If you’ve been following the news in recent weeks (March/April 2026), you must have read about two major “supply chain attacks” that occurred. You were probably affected in some way by the problem with the LiteLLM and Axios projects.

One of the perks of being a Google Developer Expert is the incredible opportunities it provides. A few weeks ago, I had the opportunity to meet Robert Griesemer, co-creator of Go, in person, as well as Marc Dougherty, Developer Advocate for the Go team at Google. At a happy hour after Google I/O, Marc asked me and another Go GDE from Korea for feedback on the language. My response was that I didn’t have any specific feedback about the language but that:

In November 2024, Anthropic published a blog post announcing what may be its most significant contribution to the AI ecosystem so far: the Model Context Protocol.

Turso is one of those projects that you look at and think, “How has no one done something like this before?”  I’ve been following the project since its launch, but only now have I been able to dedicate some time to testing, which I describe in this post.

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

1. Creating an API with a database
2. Creating an API with authentication (<— you are here)
3. Communication via Pub/Sub
4. Deploy

In the first part, we created a simple API that validates a user given the correct parameters. Now, let’s use this functionality to increase the project’s complexity: add a new API that requires authentication to be accessed.

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. But my excitement really increased after this post was published in December 2024. It announced that the framework would become an independent project, separated from the Encore Cloud tool. This decision can make the framework more attractive to companies and developers who want to use it in their existing environments. I have nothing against Encore Cloud, which seems to be a very interesting and robust solution, but this freedom of choice favors adoption in companies of different sizes.

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

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

The intrinsic ability of a system to adjust its functioning prior to, during, or following changes and disturbances, so that it can sustain required operations under both expected and unexpected conditions

When we think about communication between services/microservices, the first option that comes to mind is good old JSON. And this is not without reason, as the format has advantages, such as:

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.