Platform APIs are a set of building blocks for platform teams to deliver self-service infrastructure to engineers within their orgs. They are a way of delivering the required dependencies for applications without the need for direct interaction with cloud infrastructure, using APIs, SDKs, CLI and Web UI.
Micro is an API first development platform. It’s a single solution for building API first products from source to running and beyond. Micro abstracts away the complexity of cloud infrastructure and provides simpler building blocks to build on. It embraces the microservices architecture and enables developing a single API as many separate services.
Micro Web was a dashboard built for querying Micro services in a browser. In v3 we largely sidelined it to focus
on a headless server driven by a CLI and consumed via APIs. Today though we’re bringing it back in an all new way.
Micro Web is Reborn as a pure JS experience.
One of the things I love the most about Micro is dynamic CLI commands. This is a feature that showed up in version 3.0.
Micro started out with a fixed set of commands like most command line tools. The API however knows how to map HTTP requests
to service dynamically. We wondered, what if you could do the same for the CLI. It turns out, you can. Here’s an example.
Over the years I’ve become pretty frustrated by the state of tech and engineering in general.
One of the biggest issues we face in the industry is the lack of reusability in software.
GitHub made a major revolutionary change for developers, enabling all of us to reuse libraries,
and code through reuse rather than writing everything from scratch. Yet it never felt like that
made it any further than that.
If you’re following our Building a Blog with Micro series you’ll already know a lot
about building a blog as Micro services. In this post we’re going to cover a little on actually writing your blog via the terminal. We’ve already
built out the services needed so you should be able to access them in micro/services/blog.
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.
This is the official announcement for the release of Micro 3.0 better known as M3O - a platform for cloud native development.
Our 3.0 release is a major refactor and consolidation of the existing tooling into something that addresses the entire workflow
of build, run, manage and consume all from the developers perspective.
Today we’re announcing M3O - a cloud native platform for Micro services development. A vastly simpler method of building distributed systems in the Cloud and beyond without having to manage the infrastructure. M3O (pronounced “em-3-oh” and derived from the word M[icr]o) is the culmination of many years of experience doing distributed systems development and today we want to shed more light on what we’re working on.
In this post we will have a look at how to run and manage microservices locally with micro server and the Micro CLI in general.
The Micro CLI consists of both the server command and other client commands that enable us to interact with the server.
micro server can run microservices in different environments - binaries locally for speed and simplicity, or containers in a more production ready environment.
In 2015, go-micro, a Go microservices framework was announced. Today we introduce the micro server, which builds on top of go-micro, and enables you to run and manage microservices with ease, both locally and across different environments.