Back to building monolith applications?

Most experienced engineers would likely recommend implementing microservices, APIs, and serverless architectures in the current technology landscape. And not dare to talk about building a monolith solution. But this is what one Amazon Prime Video team did because of too high infrastructure costs and scaling bottlenecks. By ditching serverless, microservices, and AWS Lambda, they saved 90% of their infrastructure costs and solved their performance issues. Read the full story here.

Implementing the latest infrastructure and development concepts for the sake of it does not necessarily bring the best solutions. It’s like pushing database normalization to the extreme, to the detriment of performance. Denormalization is often necessary.

Every case is different when building an [new] IT solution and comes with other requirements. Different IT architectures will have various pros and cons, and no solutions will be perfect. You must challenge your team to think out of the box, assessing “modern” ways of doing things while not excluding traditional ones.You must also recognize the existing IT landscape and technical debt because it’s not like you can erase everything and start from scratch. If necessary, build a minimum viable product to prove your proposed architecture is scalable and delivers the required performance.