Blog

The latest on M3O, the cloud, APIs and more

Launching M3O Carbon


Today we’re announcing M3O Carbon, a way to purchase carbon offsets programmatically.

»

Launching M3O Space


Today we’re announcing M3O Space aka infinite cloud storage.

»

Launching M3O Apps


Today we’re announcing M3O Apps. A quick way to deploy any app for free.

»

Open sourcing the M3O Cloud Next Dashboard


Today we’re open sourcing our M3O Cloud Next Dashboard.

»

Why developers need an AWS alternative


»

M3O - An open source AWS alternative

M3O is an open source public cloud platform.
We are building an AWS alternative for the next generation of developers.

»

Side step the fuel shortage with APIs

With the latest fuel shortages gripping the UK perhaps you’ve decided to invest in an electric vehicle (EV) or maybe you already own an EV and are currently feeling very smug indeed. Whatever your position you will probably find that locating a public charging point is still not the easiest thing to do as the current charging infrastructure lags far behind that of its petrol powered equivalent.

»

Leveraging Micro APIs through Nocode


Over the last few years the “Nocode” movement has gathered huge momentum; today, there is a plethora of tools that will empower non-developers to turn their ideas in to real businesses.

»

Micro APIs - Programmable building blocks for everyday use


Today we’re excited to announce our new Micro API cloud platform, now in beta. Simple, fast and affordable APIs for everyday use. Signup for free (no credit card needed) and get $5 of free credit to get started.

»

Why and how we built Distributed with Next.js and Micro


Distributed is a live social chat app built as a Jamstack demo using Next.js and Micro. We built it to demonstrate the value proposition of M3O - a cloud platform for API development. This post explains what went into building Distributed in just a few weeks and how M3O helped rapidly build our MVP.

»

Your new API backend for the jamstack


Last month we talked about a new architecture pattern, Netlify for the frontend, Micro for the backend. As the frontend has evolved towards being dominated by the Jamstack, we believe the backend also requires a fundamental shift in it’s design and consumption model.

»

Why Companies Adopt Microservices and How They Succeed


This is a cross post from the open source Micro.mu blog. A wildly popular article on why companies adopt microservices and how they succeed written in 2016. Given its relevance we thought it was the right time to post it here. Hope you enjoy!

»

Turn any blog or RSS feed into an API


Last time we talked to you about how we believe Micro is Netlify for the backend. We got a very strong positive reaction to that, filling a pain point it looks like many people had. In that post we used headless cms aka blog posts as an example of the API you’d build on the backend to be consumed by a frontend. Today we’re going to take it a step further. We’re going to turn any blog or RSS feed into an API.

»

Building a blog with Micro in Go

This is a cross post from micro.mu/blog on how to build a blog with Micro. We’ve been getting a lot of feedback on our series related to Netlify for the backend and what’s clear, people want to see more code. So here it is. Hope you enjoy!

»

Netlify for the frontend, Micro for the backend


Today Netlify has emerged as the modern platform for rapidly building web applications without having to worry about anything beyond your code. We at Micro are users of Netlify and have bought into this phenomenal experience. What’s more Netlify has demonstrated to us a breakdown in the classic web architecture stack which previously combined web and api concerns in a single place. As we moved through a tiered architecture frontend had not been given anything more than hints on how to consume dynamic content from the backend. Today we’re all calling this the Jamstack.

»