Recently I’ve spent some time working on a .NET microservice ecosystem. After working on this for a few weeks, it struck me how time-consuming and frustrating it was to work with the configuration across these services. It got me thinking about the past projects I’ve worked on and how I’ve never really seen configuration managed well; it’s always an afterthought. Often a .env file is added when an engineer realises they need to manage configuration values.

Last year I wrote a blog post on the journey to micro frontends we took when I worked at Peak. It was supposed to be a series, priorities changed, and the solution never evolved into what it was supposed to be. I want to revisit this and discuss why I believe it didn’t work and why I wouldn’t recommend it moving forward.