Nothing new, but I keep seeing violating of this rule again and again. Let's explain why it is bad.

Automated infrastructure (Infrastructure as Code) is essential to succeed (not only) in the cloud.

Serverless blue-green deployment is a nice practice. However, it doesn't come without challenges.

Let's code some transducers and take a deeper look at how they work under the hood to see differences from pipes.

Let's find the best combination of two good architectural approaches: Package by component and Clean architecture.

Async/await syntax is a great technique how to deal with promises in modern JavaScript. Unfortunately it's not always easy to understand how it works which can lead to strange bugs. Let's investigate one of them.

Why shouldn't we test the implementation? How to decouple our tests from the code? What is the reason to add a new test? Why is mocking a code smell? In this article I will try to find answers to those questions.

Blue-Green Deployment is a very good technique that has been successfully used for managing releases of cloud applications. Now it's time to rethink it a bit for serverless systems.

Is it even possible to roll microservices back?

Talking about serverless microservices, functions are the basic building blocks of the service functionality. How to design them from the code and deployment perspektive?