Building a Blog with Micro - Part One

This series will cover how to build a blog service using Micro. We’ll decompose a monolithic Blog into multiple services. In part one we’ll focus on building a Post service. It will be good way to learn how to build nontrivial applications with the store and the model.

The most important takeaway from this post will likely be the the usage of the key-value store for non-trivial usecases (such as querying blog posts by slug and listing them by reverse creation order).

The Basics

Head to the Getting Started Guide if you haven’t used Micro before.

If you have let’s use that knowledge! As a reminder, we have to make sure micro server is running in an other terminal, and we are connected to it, ie

Running the micro server

micro server

Looking up our local environment

$ micro env
* local         Local running micro server
  dev        proxy.m3o.dev          Cloud hosted development environment
  platform   proxy.m3o.com          Cloud hosted production environment

We can see the local environment picked. If not, we can issue micro env set local to remedy.

Now back to the micro new command:

$ micro new posts
$ ls posts
Dockerfile	Makefile	README.md	generate.go	go.mod		handler		main.go		proto

Great! The best way to start a service is to define the proto. The generated default should be something similar to this:

In our post service, we want 3 methods:

Let’s start with the post method.

Astute readers might notice that although we have defined a Post message type, we still redefine some of the fields as top level fields for the SaveRequest message type. The main reason for this is that we don’t want our dynamic commands.

Ie. if we would embed a Post post = 1 inside SaveRequest, we would call the posts service the following way:

micro posts save --post_title=Title --post_content=Content

but we don’t want to keep repeating post, our preferred way is:

micro posts save --title=Title --content=Content

To regenerate the proto, we have to issue the make proto command in the project root.

Now, the main.go:

After that’s done, let’s adjust the handler to match our proto! This snippet is a bit longer, so cover it piece by piece:

The above piece of code uses the model package. It sets up the indexes which will enable us to query the data and also tells model to maintain these indexes.

At this point micro run . in project root should deploy our post service. Let’s verify with micro logs posts:

$ micro logs posts
Starting [service] posts
Server [grpc] Listening on [::]:53031
Registry [service] Registering node: posts-b36361ae-f2ae-48b0-add5-a8d4797508be

(The exact output might depend on the actual config format configuraton.)

Saving posts

Let’s make our service do something useful now: save a post.

After a micro update . in project root, we can start saving posts!

micro posts save --id=1 --title="Post one" --content="First saved post"
micro posts save --id=2 --title="Post two" --content="Second saved post"

Querying posts

Again, implementation starts with defining the protos:

A make proto issued in the command root should regenerate the Go proto files and we should be ready to define our new handler:

We want our query handler to enable querying by id, slug and also enable listing of posts:

As mentioned, the existing indexes can be used for querying too with the ToQuery method.

After doing a micro update . in the project root, we can now query the posts:

$ micro posts query
	"posts": [
			"id": "2",
			"title": "Post two",
			"slug": "post-two",
			"content": "Second saved post",
			"created": "1604423363"
			"id": "1",
			"title": "Post one",
			"slug": "post-one",
			"content": "First saved post",
			"created": "1604423297"

Stellar! Now only Delete remains to be implemented to have a basic post service.

Deleting posts

Since we have already defined Delete in our proto, we only have to implement the handler. It is rather simple:


This brings us to the end of the first post in the blogs tutorial series. There are many more features we will add later, like saving and querying by tags, but this post already taught us enough to digest. We will cover those aspect in later parts of this series.

The source code for this can be found here. Further versions will be in the same blog folder with different versions, ie v2-posts and once we have more services, v2-tags, v2-comments. Folders with the same prefix will be meant to be deployed together, but more on this later.