We don’t even need a moment to gather which operating system is the most used one. Android development is a booming business because of the number of users it has. It is open source and its development can be ported across devices with relative ease. Plus, it has good backwards compatibility across versions. And, precisely due to this diversity, the need for testing on many devices is paramount.

Have you heard of the misconception that agile is about velocity: i.e. delivering more, at a faster rate? Although this statement is true, it is ultimately meaningless if you don’t deliver value and the customer is not satisfied.

Whether you're breaking up a monolith or building a green-field application, you may consider using a microservice architecture. Like all app architectures, this model brings opportunities and challenges that a developer must be aware of in order to make the most of this app design. One such challenge is ensuring communication between your microservices.

In today’s post, we’ll dive into how we, at AppSignal, solved a daunting engineering challenge. Giving you a look into the kitchen, this post will show you how we tested a new database in production without having to worry about errors/downtime. Alright, let’s get cooking!