Mule microservices distributed transaction tracing

With the advent of microservices, the functionalities that used to be bundled together in a single web/mule application are now running on different containers across VMs and at times across datacenters. This presents a huge challenge to trace transactions as they traverse across the container/VM boundaries.   

Is this the end of microservices?

February 28 2020

0 comments

It was inevitable! With such euphoria greeting the concept of microservice architecture in 2014, it was only a matter of time before the trough of disillusionment swallowed the hype. What started with blogs like “What are microservices?” and “Reducing technical debt with microservices,” peaked with articles like  “Can microservices save U.S. Retailers?” and “Why microservices are the foundation to a digital future,” has now come crashing down with pieces like “Goodbye microservices” and “Monoliths are the future.” Where did it all go wrong?

What is a service mesh and do you need one?

Studies show that 91% of enterprises are using or have plans to use microservices. The reasons are well documented — monolithic architectures are hard to develop and maintain, while microservices allow for greater agility with smaller, targeted services. 

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.

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.

Getting on track with microservices

API-led connectivity

As enterprise IT seeks greater speed and agility through the adoption of a microservice architecture, they find this new paradigm can collide with long-established operating models.

How microservices enable organizational agility

LAYERED APIs OVER FINE-GRAINED SOA

The big don’t eat the small, the fast eat the slow. In today’s hyper-competitive digital economy, organizations succeed or fail based on their agility: the velocity at which they can deliver the new products, services, and features that meet the changing needs of their market.

Fundamental principles of microservice design

design principles microservices

Microservice capabilities are expressed formally with business-oriented APIs. They encapsulate a core business capability and as such are assets to the business. The implementation of the service, which may involve integrations with systems of record, is completely hidden as the interface is defined purely in business terms.

The application network and the service-mesh

Many customers I meet are either evaluating or beginning their implementation of microservice architectures. Some of these customers are coming off big-bang projects that have failed to replace large legacy assets.