Have a safe microservice journey!
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.
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.
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.
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.
Don’t compromise on microservices prerequisites, both technically or organizationally. It’ll cost you a pretty Franklin banknote.
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.
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.
