this night I dream an architecture to build a "clone" of AWS Lambda.
The more I think about the more it seems reasonable.
Before to start coding and stuff, I would like to know if you guys are using AWS Lambda, what you like of the service and what you dislike.
What would it be your perfect Lambda ?
I'm a Technical Evangelist at Amazon Web Services.
Here are some videos from re:Invent 2015 on AWS Lambda : technology, use cases, customer stories. I hope you find them useful :)
Large burstiness would also be amazing.
Imagine running Spark where a hundred workers are allocated for 30 seconds. It makes it possible to build services like BigQuery.
I use Lambda for a lot of aws backup jobs that boto can do. For example
* RDS hourly snapshots
* EBS daily snapshots
* checking contents of s3 buckets
Works great for that type work for me as long as the job doesn't run for more then 300 seconds.
Lambda seems designed for internal trusted use for offline or background data processing, not for writing a public API endpoint.
Might fit your needs better than Lambda.
Lambda passes the data to another component on AWS to be processed.
The input sources for data range from APIs calls on Lambda, data from partners, data from legacy components, etc. So we split our data sourcing/fetching and data processing. They all flow into the same funnel (component) to be processed.
Anyone got a one or two line description of the sort of problems it would be good at solving?
- Dirt cheap (pay only what you need)
- Scales fast and large
- Just works
- Getting swift to run is very hacky
Considering to replace the game backend (scala on ec2) with Swift on Lambda (plus API gateway)
Lambdas do run in containers/instances that get reused ... unless they are idle for too long.