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.
One of the debates that’s been smoldering since the microservices movement began is how microservices should communicate with one another.
Software architects can often conflate the different types of API call coordination. To help address this pitfall, see the classification system I use.
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.
Check out the five most popular blog posts in February 2019!
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.
No company, no matter its size or industry, is safe from disruption. It’s easier than ever for new entrants to enter a market and turn entire industries upside down. Unless organizations can nimbly innovate at the speed of their competition, they will be left behind, and large organizations with calcified processes and structures will be hit the hardest.
The orchestration of system-to-system file transfers by enterprises with external trading partners (commonly known as B2B file transfer) has been around for decades; as far back as the beginning of standard network protocols.
