[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"doc-detail-188012-en":3,"doc-seo-188012-105":30,"detail-sidebar-cat-1-en-105":92},{"code":4,"msg":5,"data":6},0,"success",{"doc_id":7,"user_id":8,"nickname":9,"user_avatar":10,"doc_module":11,"category_id":12,"category_name":13,"doc_title":14,"doc_description":15,"doc_content":16,"file_id":17,"file_url":18,"file_type":19,"file_size":20,"view_count":11,"is_deleted":4,"is_public":11,"is_downloadable":11,"audit_status":11,"page_count":21,"language":22,"language_code":23,"site_id":24,"html_lang":23,"table_of_contents":25,"faqs":26,"seo_title":27,"seo_description":15,"update_tm":28,"read_time":29},188012,962084925502,"Emma Mercer","https://ap-avatar.wpscdn.com/davatar_6f874abed73319feea01a86fa6f0fab8",1,158,"General","OaaS Abstraction and Cloud-Developer Coordination","This document explores a novel approach to Function-as-a-Service (FaaS) development and deployment, focusing on an OaaS (Object-as-a-Service) abstraction that integrates non-functional requirements directly into the application development lifecycle. The proposed system aims to streamline the coordination between cloud developers and infrastructure providers by offering an app-friendly interface for defining and managing non-functional requirements such as throughput, availability, locality, persistence, runtime configurations, budget constraints, consistency models, jurisdiction, and data encryption. The OaaS abstraction is presented as a unified framework that bridges the gap between logical, data, and non-functional aspects of an application. The deployment phase leverages a DaaS Provider (Oparaca) built on cloud infrastructure, featuring components like a Runtime Manager, QoS Enforcer, Monitor, and Class Runtime. This architecture facilitates non-functional requirement-driven cloud-developer coordination, leading to more efficient and robust FaaS applications. The document also touches upon resource optimization within Class Runtimes, involving modules for object management, code execution, data management, a class runtime manager, a container orchestrator, and monitoring capabilities, all orchestrated by a Package Manager and a Hash-Aware Load Balancer. This comprehensive system design supports the development and deployment of scalable, reliable, and cost-effective cloud-native applications by abstracting complexity and emphasizing clear interfaces for developer interaction with cloud services and their associated non-functional guarantees.","| Application = | \u003Cbr>Logic\u003Cbr>\u003Cbr>Data\u003Cbr>\u003Cbr>Non-functional Requirements\u003Cbr>|\n| --- | --- |\n\n| Name | Value Type | Unit | De􀀂nition |\n| --- | --- | --- | --- |\n\n\n| QoS Requirements |  |  |  |\n| --- | --- | --- | --- |\n| Throughput | Integer | Rps | Minimum number of invocations guaranteed to be executed per second |\n| Availability | Real | Percent | The percentage of time an object/function must be available for service. |\n| Locality | {Local, None} | N/A | How function invocations are dispatched with respect to object state location. |\n\n\n| Deployment Constraints |  |  |  |\n| --- | --- | --- | --- |\n| Persistent | Yes/No | N/A | Should the data associated with the object persistent |\n| Runtime Req. | Dict | N/A | Speci􀀂c object runtime con􀀂guration. (e.g., choice of FaaS engine) |\n| Budget | Integer | Credit | Object deployment and operation budget. All costs must not exceed this value. |\n| Consistency | Enumerate | N/A | Object consistency model: eventual, sequential, linearization, or none. |\n| Jurisdiction | Enumerate | N/A | Candidate places to deploy an object |\n| Data Encryption | Enumerate | N/A | Specify or disable the encryption algorithm for the stored data |\n\n|  |  |  |  Knative |  |  |  |  |  | |  OpenFaaS |  |  |  |  |  |  |\n| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |\n|  |  |  |  Fission |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n|  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |  |\n\n|  | |  | Knative\u003Cbr>Oparaca (Local)\u003Cbr>Oparaca (Local + Warm) Ideal |  |\n| --- | --- | --- | --- | --- |\n|  |  | |  |  |\n|  |  |  | | |","cbCaigp7CXhDXfKy","https://ap.wps.com/l/cbCaigp7CXhDXfKy","pdf",907284,19,"English","en",105,"# Oparaca\n## Knative","[{\"question\":\"What are the key components of the OaaS abstraction?\",\"answer\":\"The OaaS abstraction encompasses Logic, Data, and Non-functional Requirements, providing a unified framework for application development.\"},{\"question\":\"What are some of the non-functional requirements that can be managed?\",\"answer\":\"The document lists several non-functional requirements including Throughput, Availability, Locality, Persistence, Runtime Requirements, Budget, Consistency, Jurisdiction, and Data Encryption.\"},{\"question\":\"What is the role of the DaaS Provider (Oparaca)?\",\"answer\":\"The DaaS Provider (Oparaca) is responsible for the deployment phase, managing the runtime, enforcing QoS, and monitoring applications on the cloud infrastructure.\"}]","OaaS Abstraction and Cloud-Developer Coordination | PDF",1788386806,7,{"code":4,"msg":31,"data":32},"ok",{"site_id":24,"language":23,"slug":33,"title":14,"keywords":34,"description":15,"schema_data":35,"social_meta":87,"head_meta":89,"extra_data":91,"updated_unix":28},"oaas-abstraction-and-cloud-developer-coordination","",{"@graph":36,"@context":86},[37,54,69],{"@type":38,"itemListElement":39},"BreadcrumbList",[40,44,48,51],{"item":41,"name":42,"@type":43,"position":11},"https://docshare.wps.com","Home","ListItem",{"item":45,"name":46,"@type":43,"position":47},"https://docshare.wps.com/template/","Template",2,{"item":49,"name":13,"@type":43,"position":50},"https://docshare.wps.com/template/general/",3,{"item":52,"name":14,"@type":43,"position":53},"https://docshare.wps.com/template/oaas-abstraction-and-cloud-developer-coordination/188012/",4,{"url":52,"name":14,"@type":55,"author":56,"headline":14,"publisher":58,"fileFormat":61,"inLanguage":23,"description":15,"dateModified":62,"datePublished":63,"encodingFormat":61,"isAccessibleForFree":64,"interactionStatistic":65},"DigitalDocument",{"name":9,"@type":57},"Person",{"url":41,"name":59,"@type":60},"DocShare","Organization","application/pdf","2026-09-06","2026-09-02",true,{"@type":66,"interactionType":67,"userInteractionCount":47},"InteractionCounter",{"@type":68},"ViewAction",{"@type":70,"mainEntity":71},"FAQPage",[72,78,82],{"name":73,"@type":74,"acceptedAnswer":75},"What are the key components of the OaaS abstraction?","Question",{"text":76,"@type":77},"The OaaS abstraction encompasses Logic, Data, and Non-functional Requirements, providing a unified framework for application development.","Answer",{"name":79,"@type":74,"acceptedAnswer":80},"What are some of the non-functional requirements that can be managed?",{"text":81,"@type":77},"The document lists several non-functional requirements including Throughput, Availability, Locality, Persistence, Runtime Requirements, Budget, Consistency, Jurisdiction, and Data Encryption.",{"name":83,"@type":74,"acceptedAnswer":84},"What is the role of the DaaS Provider (Oparaca)?",{"text":85,"@type":77},"The DaaS Provider (Oparaca) is responsible for the deployment phase, managing the runtime, enforcing QoS, and monitoring applications on the cloud infrastructure.","https://schema.org",{"og:url":52,"og:type":88,"og:title":14,"og:site_name":59,"og:description":15},"article",{"robots":90,"canonical":52},"index,follow",{"doc_id":7,"site_id":24},{"code":4,"msg":5,"data":93},[94,99,104,109,114,119,124,129,134],{"id":95,"doc_module":11,"doc_module_name":46,"category_name":96,"show_sort_weight":97,"slug":98},11,"Presentations",90,"presentations",{"id":100,"doc_module":11,"doc_module_name":46,"category_name":101,"show_sort_weight":102,"slug":103},12,"Resumes",80,"resumes",{"id":105,"doc_module":11,"doc_module_name":46,"category_name":106,"show_sort_weight":107,"slug":108},14,"Invoices",70,"invoices",{"id":110,"doc_module":11,"doc_module_name":46,"category_name":111,"show_sort_weight":112,"slug":113},15,"Posters",60,"posters",{"id":115,"doc_module":11,"doc_module_name":46,"category_name":116,"show_sort_weight":117,"slug":118},16,"Social Media",50,"social-media",{"id":120,"doc_module":11,"doc_module_name":46,"category_name":121,"show_sort_weight":122,"slug":123},17,"Forms",40,"forms",{"id":125,"doc_module":11,"doc_module_name":46,"category_name":126,"show_sort_weight":127,"slug":128},18,"Letters",30,"letters",{"id":130,"doc_module":11,"doc_module_name":46,"category_name":131,"show_sort_weight":132,"slug":133},21,"Paper Templates",5,"papers-templates",{"id":12,"doc_module":11,"doc_module_name":46,"category_name":13,"show_sort_weight":4,"slug":135},"general-158"]