I’ve written several articles on this topic now, each time trying to refine the idea and explain it from a different vantage. This short article provides an executive summary of the others.

Because the term microservice is well known in cloud-native application design, I’ve employed it in my descriptions of…


Self-deployment is a technology used by federated applications to deploy themselves upon request. In a previous article, we defined a federated application as one whose components are loaded from multiple network locations and repositories at runtime. As we’ll see, just how they’re loaded has important implications. Strictly speaking, the components…


What are federated microservices?

Federated microservices are the independently deployable components of a federated application. In a federated application, components are loaded from multiple network locations and repositories at runtime. They are not developed by a single team or built from a single codebase. …


When evaluating microservices as a candidate architecture, the most important factor to consider is that the end result is a distributed application. Microservices are the components of distributed applications — and distribution is what enables their chief virtue, deployment independence. Unfortunately, relative to the traditional alternative, pejoratively called “monoliths”, distributed…


For the latest on this topic, see:

While microservices speed time-to-market through focused, autonomous teams, shorter development cycles and deployment independence; they are considerably more complex to build and maintain than traditional monoliths. So much so, that many projects underdeliver or fail outright.

Module federation offers a solution to this…


This is the first installment in (what I intend to become) a series of articles on Module Federation design patterns. As MF is a recent technology, and not well understood, these patterns may help to increase clarity and spur innovation.

Currently, MF is Javascript-based and, therefore, some patterns can only…


Excellent work.

You might consider module federation, and stream remote modules at runtime, as they are needed, plus any required dependencies.

Framework for federated, cloud-native apps.

github.com/module-federation/microlib

Any plans to support a standalone WebAssembly runtime, like wasmtime or wasmer?

Same question for deno?


If everything is not done for the sake of something else, surely that which is not is the good and the chief good. Will not the knowledge of it then, like an archer with a mark to aim at, help us to hit upon what is right? -Aristotle

In one of his presentations, “Uncle Bob” throws into stark relief the exaggerated importance placed on the database in past years. “The database is just an I/O device,” he says. It’s incidental, not essential — it’s a detail, not architecture and not the point of software. Wait long enough and…


Zero Marginal Cost

Modern, distributed applications are characterized by decentralized control, zero trust, open source and arguably an egalitarian spirit. They create significant value with little overhead, leading to what economist Jeremy Rifkin calls, The Zero Marginal Cost Society. According to Rifkin, software in general, and IoT in particular, is key to new…

Tyson Midboe

After a decade of building clouds for large enterprises, now working to resolve issues with with cloud-native application architecture.

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store