3 ms·
Reading through the comments one thing is clear: almost no one here seems to understand _why_ you use serverless implementations. If your architecture follows
by ChicagoDave 5y ago
Reading through the comments one thing is clear: almost no one here seems to understand _why_ you use serverless implementations.
If your architecture follows domain driven design principles, you can build very large, complex, scalable, and maintainable systems.
- akos-kri 5y agoHey, author of the post here! Thanks for your comment. Yes, you hit the nail on the head :) 99% of our code actually lives in domain packages that are infrastructure agnostic. Our lambda handlers are very lightweight adapters that take the input and transform it to a domain input and transform the output back. That said, our serverless architecture does leak a bit into our domain thinking. E.g. certain things are built async since it's just so easy to hook up a lambda to listen to an EventBridge event.
- Veuxdo 5y agoI use them because, as a programmer, I don't care about operating system upgrades, disks becoming full, viruses scanning etc.
- spelunker 5y agoThis reason alone makes doing serverless worth it, IMO.