Adopting an event-driven architecture (EDA) to increase scalability and reduce coupling between components/services is relatively common in complex environments.

This post is part of a tradition I started 10 years ago! Every now and then, I make a list of the apps and services I use on a daily basis and share them in these posts.

I’ll start this post with a bit of history. Back in the early 2010s, the buzz was the concepts of APIs and API-first.

Let’s start at the beginning. What is resilience? I like the definition in this post:

When we think about communication between services/microservices, the first option that comes to mind is good old JSON.

Thanks to the Google Developer Experts program, I had the opportunity to participate in Google I/O in Mountain View, California, in May this year.

First things first: what is make? Present in all Linux distributions and Unix derivatives such as macOS, the tool’s manual describes it as:

This text is the last part of a series of posts I wrote about one of the technologies that have had the most impact on me in recent years: WebAssembly.

Recently, in a code review, the great Cassio Botaro gave me a handy tip: refactor some tests to use the test helpers feature from the testing package.

In the previous post, we saw that there are different types of load tests and what their objectives and characteristics are.