Turso is one of those projects that you look at and think, “How has no one done something like this before?

This text is the second part of a series of posts about the Encore.go framework :

When we think of “observability,” the first idea that probably comes to mind is “problems” or “troubleshooting” ( if you prefer the jargon).

Encore.go has been on my radar for quite some time, when its beautiful website and examples caught my attention in a news article on Hacker News.

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.