# User-Defined Cloud

* Cloud computing evolves --> services, instance types 
* Life cycle 
  * Provider identifies a new type of application / hardware
  * Provider develops / adapts SW/HW infrastructure
  * Provider launches a new service or extends an existing one 
* E.x. health industry 
  * Secure storage and processing 
  * But today:
    * No on-demand accelerator: pay extra with VMs 
    * No secure accelerator: use secure CPU and run slower 
    * No fine-grained tuning of systems feature: build your own 
      * Combine a set of services 
* No right service for niche applications 
  * Users have to build a local cluster or use a third-party services 
* Cloud providers "define" the cloud to accommodate the user needs they deem popular 
* Users know what is needed to run their workloads and should be allowed to get what they need 
* Idea: 
  * user-define computing resources and features for their own workload
  * cloud provider supply software and hardware infrastructures under the hood  

![User-define cloud ](/files/awqBn1xIBobZXe3exa5Y)

![What users can define ](/files/eVI174jNjyiH8qVNbZb5)

* Fine-grained hardware and software building blocks put together on demand like Lego pieces 

![](/files/ClEtumqbXtHXV3u2SPIk)

* Find the right combination of HW / SW

Benefits:

* Users 
  * Customize public cloud for exactly what they need 
  * No need to wait for providers to prepare new features 
    * Fast time to market, better performance 
  * No need to manage SW/HW infra
  * Pay as we go 
    * Low cost 
* Providers 
  * Build one set of configurable SW/HW infra 
    * Cheaper to develop and maintain 
  * Attract niche users 
  * Charge a higher unit resource price 
    * More profit 


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sliu583.gitbook.io/blog/networking/index/reading-list/user-defined-cloud.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.