Skip to content

Instantly share code, notes, and snippets.

@tristanls

tristanls/serverless_contexts.md

Created August 29, 2017 15:48
Show Gist options
  • Star 0 You must be signed in to star a gist
  • Fork 0 You must be signed in to fork a gist
  • Save tristanls/a4d4cfbc47a143cb1675e62830eff3b4 to your computer and use it in GitHub Desktop.
Save tristanls/a4d4cfbc47a143cb1675e62830eff3b4 to your computer and use it in GitHub Desktop.
Download ZIP
Contexts where Serveless was useful or not.
Raw
serverless_contexts.md

Contexts where Serverless turned out useful:

  • When setting up a service control plane (for example commands such as CreateTenant, or DeleteTenant) Serverless is useful as the commands aren't executed often, and the latency is not really a constraint.
  • Processing events from an event stream up to a certain throughput when cost starts to dominate and running dedicated servers (which possibly is "roll your own serverless") becomes a more economical choice.

Contexts where Serverless didn't work well:

  • When setting up a service data plane (for example, proxying a request with minimal latency), Serverless doesn't work well due to unpredictable startup times, as well as lack of ability to stream data through a serverless function (functions typically require whole events in order to start processing).
  • Processing events from an event stream beyond a certain throughput where cost starts to dominate and running dedicated servers (which possibly is "roll your own serverless") becomes a more economical choice.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment