Managing Shared Components in Go Microservices with Fx

Managing Shared Components in Go Microservices

This article is part of the series Dependency Injection in Go using Fx

In many companies nowadays, microservices is the de facto way of handling service architecture. Some do it out of necessity as their application has reached a scale where the monolith is a bottleneck. Others, simply like being onboard the hype train. Whatever the scenario, the decision is often backed by the classical case for adopting microservices, which every junior dev studies extensively before their system design interview. What gets often neglected, however, is the problems which come with such an approach. Each of these problems usually demands a sophisticated solution, which raises system complexity. One such problem is how to reuse the shared infrastructure components in your microservices. Each of your services will probably have a distinct business logic, but it will also come with a big baggage of infrastructure code. These components usually don't change too much between your services - healthchecks, monitoring configs, logging, standard service configurations, etc. Fortunately, there is a very elegant solution for this problem for your Go services, which utilises the Fx Framework. It helps you by automatically managing your dependencies, but it can do much more than that as I'll show you in the upcoming sections. In this article, I will show you how to effectively extract your components into reusable & independent modules which can easily be shared across your Go services.
Continue Reading

Site Footer