Tomas Tulka's Blog

Defining service boundaries is hard. Let's bring some colors and make it fun!

There are situations where events and commands seem to be a good solution for a problem. Where to use events and where are commands the best fit?

Multitenancy was and still is a very popular and successful architectural pattern of the last decades. But, that is likely to change with the advent of cloud computing.

Binary data shouldn't be a part of the codebase. This is pretty well-known practice. But how to proceed when we do need binaries in our codebase, for instance as test data?

Continuous delivery (CD) brings a lot of ideas essential for a modern software product deployment. In this article we discuss how to follow CD principles by building CD pipelines with an example in AWS.

Automated infrastructure (Infrastructure as Code) is essential to succeed (not only) in the cloud. AWS provides its own service for managing resource stacks: AWS CloudFormation. What are the options to manage dependencies between stacks, how to use them and which pros & cons they have?

I already blogged about the serverless blue-green development some time ago. I used it in practice a lot with very promising results. But there are challenges as well.

After some time of developing serverless systems (especially on AWS) I take a look back and try to summarize what I have learned so far.

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

Thinking about a deployment strategy for a microservices-based system it's natural to consider a rollback. Before looking for a technical solution, let's discuss this idea conceptually. Is it even possible to roll microservices back?