So, is a modern microservices architecture the ultimate answer to everything?

This is the third blog in a series explaining how MuleSoft’s Anypoint Platform can provide agile connectivity across monolith, SOA, and microservices architectures.

In my last blog, I reviewed the different types of architectures that have evolved over the last decade and how that has now led to the commonly used microservices architecture approach. This post will discuss whether this is the ultimate answer to architecture development,

EDI with an API-led approach

retail API-led connectivity

When EDI first came into use, supply chains were simpler, with a limited number of suppliers. Now, thanks to globalization and specialized manufacturing, there might be hundreds of suppliers in a supply chain. And, as prices change, businesses move overseas, and market conditions evolve, these suppliers change as well. 

K8s: 8 questions about Kubernetes

data blocks

This is the first post in a series that intends to provide context and practical information about emerging enterprise technologies. First up is Kubernetes, the container orchestration platform that is sweeping the cloud-native world.

Have a safe microservice journey!

mountains road

An architecture needs to bend, not break, as new innovations, best practices, and needs emerge. In this post, I’ll explore the broader landscape we are traveling to support that agility.

Getting to know Anypoint Visualizer

Anypoint Visualizer architecture

Anypoint Visualizer is a graphical visualization that provides a high-level view of your application network. It automatically organizes APIs, Mule applications, and third-party systems into a comprehensive view of how they are connected. The data displayed is dynamically updated based on real-time traffic and does not require any prior configuration.

Microservices on rails

railroad tracks

In the intro to this blog series, I promised to reconcile the apparent incongruence of strategic business objectives (move fast) with traditional IT must have paradigms (be safe). In the last post, we chugged away at the surrounding ecosystem that’s needed to support the velocity promised by the former. In this post, I pause at the pre-production station to discuss some of those system safety properties that we can’t leave behind.

API interaction types in a microservice architecture: queries, commands, and events

Query Command Event

One of the debates that’s been smoldering since the microservices movement began is how microservices should communicate with one another.

The many flavors of API coordination

wheel gear cogs

Software architects can often conflate the different types of API call coordination. To help address this pitfall, see the classification system I use.

The locomotive: technological capabilities for microservices

bullet trains

Similar to steam engines leveraging prior innovation to get to bullet trains, companies just getting started with microservices can take shortcuts confidently because of microservices pioneers.

The third rail: putting microservices in context

hundred dollar bill

Don’t compromise on microservices prerequisites, both technically or organizationally. It’ll cost you a pretty Franklin banknote.