Hey, we’re starting a newsletter! Micro provides an opinionated view on how to build cloud-native systems but we want to provide opinions beyond the micro ecosystem too.

Application configuration has remained largely static for most of our lifetime, using flags, environment variables and files. Any change has usually required restarting the application or significant complexity in code to signal and reload the config.

The open source development of micro can now be sponsored via Patreon. Before we go into the details, I want to first mention what micro is and it’s funding journey.

As technology evolves so do our programming models. We’ve gone from monoliths to microservices and more recently started to push this separation even further towards functions.

Today I’m excited to announce the Micro Explorer, a single place to find projects within the micro ecosystem.

2016 has been a heck of a year for Micro. In this post we’ll recap on the past year and where we’re going but to begin with let’s talk about Micro’s origin.

As a change of pace, this post will mostly be a high level discussion on the non-technical aspects of adopting microservices within a company.

Last night I spoke about Micro at the Go meetup in London. Thanks to everyone that came to the meetup, the organisers and all those that asked questions.

It’s been a little while since the last blog post but we’ve been hard at work on Micro and it’s definitely starting to pay off. Let’s dive into it all now!

Today I want to talk to you about bots.

We’ve had a lot of questions about the micro architecture and design patterns for microservices over the past few months. So today we’ll try cover both.

In this post we’re going to discuss using Micro on NATS. It includes discussion around service discovery, synchronous and asynchronous communication for microservices.

This is a high level guide to writing microservices with go-micro.

By now you may have heard of this new phenomenon, microservices. If you’re not yet familiar and interested in learning more, checkout our introductory post here.