4 ms·

Honestly I think a lot of the frustration is because Lambda is not a fully developed platform yet. I decided to use it for a new product we're building at Croni

Honestly I think a lot of the frustration is because Lambda is not a fully developed platform yet. I decided to use it for a new product we're building at Cronitor and it's not a travesty but I wouldn't have used Lambda if I had it to do over again. They give you decent primitives: immutable versions, aliases, easy logging. But everything else you have to build yourself: You have to figure out a development loop, deploys, configuration management. There is nothing built-in to help coordinate lambda deploys across regions. I expect that you'll see this built out more this year.

spdustin 11y ago
> You have to figure out a development loop, deploys, configuration management. There is nothing built-in to help coordinate lambda deploys across regions. https://github.com/serverless/serverless https://github.com/serverless/serverless solves (upon my initial read-through) every one of your requirements, including multi-region deploys.
- encoderer 11y ago
  That may be true, but when you start using something like Lambda, you don't immediately jump to "what 3rd party framework can I use to manage this". It's not clear what the weakness are until you experience it. In the end, we solve it with a few hundred lines of fabric and bash scripts but neither of those solutions make up for the blown opportunity of a better and more powerful UX. (Lambda PMs have been on here before and have said they're working on it.)