Custom certificates are like ID cards issued by your own company instead of a public authority. They're mainly used inside private systems, such as microservices, where services only need to trust each other. A central service acts as the certificate authority (CA), creates these certificates, and gives them to each service. When combined with TLS, they let services prove their identity and communicate securely, without relying on external certificate providers.

Microservices are small, separate parts of a bigger application that work on their own. But if one part stops working, it can cause problems for the whole system. That's where resilience patterns come in. These are smart ways to keep things running smoothly, even when something goes wrong. For example, a retry pattern tries again if a service doesn't respond at first. A circuit breaker stops sending requests to a broken service so the system doesn't get overloaded. Timeouts stop the system from waiting too long for a reply. These patterns help keep the app steady and fast, giving users a better experience even if some parts fail.

Go is known for its simplicity and its powerful built-in concurrency model. At the heart of this concurrency is the concept of goroutines and the Go scheduler. In this post, we'll explore how the Go scheduler works, what makes goroutines so efficient, and how they are mapped to system threads using Go's N:M scheduling model.

The actor model is a conceptual model to deal with concurrent computation. It defines some general rules for how the system's components should behave and interact with each other.

MCP is an open protocol that standardizes how applications provide context to LLMs.