Hi, nice post! You don't really "need to learn distributed message delivery methods and the behavior of distributed transactions", unless you're into microservices.
Although this architectural pattern is common and fits well in serverless computing, it's not a must. If you have a monolithic function, for example, distributed transaction isn't needed.
Using features like Lambda Layers, it's even possible to avoid distributed msgs or transactions while still enjoying some benefits similar to what microservices deliver.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi, nice post! You don't really "need to learn distributed message delivery methods and the behavior of distributed transactions", unless you're into microservices.
Although this architectural pattern is common and fits well in serverless computing, it's not a must. If you have a monolithic function, for example, distributed transaction isn't needed.
Using features like Lambda Layers, it's even possible to avoid distributed msgs or transactions while still enjoying some benefits similar to what microservices deliver.