Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Use serverless cloud services for running workloads #129

Closed
srini1978 opened this issue Oct 23, 2022 · 1 comment · Fixed by #151
Closed

Use serverless cloud services for running workloads #129

srini1978 opened this issue Oct 23, 2022 · 1 comment · Fixed by #151
Assignees
Labels
proposed pattern An idea for a new pattern to submit

Comments

@srini1978
Copy link
Contributor

srini1978 commented Oct 23, 2022

Describe the pattern you'd like to propose
Serverless cloud services present an option to run workloads wherein a separate machine need not be provisioned in the cloud .

Describe specific emission impact from this pattern
Serverless architectures are meant not to provision cloud servers exclusively for a specific workload or customer, but rather to use them when they are needed and then de-allocate them after the completion of workload execution. This also serves the sustainability story very effectively as servers, storage, and network bandwidth are used to their maximum utilization levels.

References to this pattern
(https://devblogs.microsoft.com/sustainable-software/adopting-azure-serverless-architectures-to-help-reduce-co2-emissions-part-1/)

(https://dev.to/kumo/you-thought-serverless-was-green-here-is-how-to-really-make-it-sustainable-1m0p)

Additional context
Add any other context or screenshots about the proposed pattern here.

@srini1978 srini1978 added the proposed pattern An idea for a new pattern to submit label Oct 23, 2022
@markus-gsf-seidl
Copy link
Contributor

I'll convert this

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
proposed pattern An idea for a new pattern to submit
Projects
Status: Done
Development

Successfully merging a pull request may close this issue.

4 participants