This post is by one of our MuleSoft champions, Antonio Abad.
Let’s start with a simple definition of both concepts:
“An ESB is basically the integration of the new and the old, providing a central place for the services, applications, and IT resources in general that you want to connect.”
“A microservice architecture (vs. the legacy monolithic architecture) is an approach to developing a software application as a series of small services,
Download our Best Practices for Microservices whitepaper to gain a deeper perspective about our approach to microservices written in this post.
If IT today has a watchword, that word is “speed.” At the same time, IT is expected to protect the organization’s crown jewels (company finances and private customer records) and to keep services available and responsive. The message: Go faster, but don’t break anything important. Even Facebook has modified its motto on this front from “Move fast and break things” to “Move fast with stable infrastructure.”
In response to these pressures,
Featured guest post on MuleSoft Blogs from Abraham Santiago, Principal Integration Consultant of WhiteSky Labs.
API middleware integration industry is definitely not short of Architectural principles, from top-down strategic initiatives like digital transformation and legacy modernization to developer-centric ones like event-driven architecture, microservices, and DevOps. But beyond that and onto the fun and games of actual delivery of services to enterprise customers,
Govind Mulinti, a senior architect at Whishworks, is the guest author of this blog post.
Microservices has been a buzz word for past few years. It talks about a technique of designing integrations and APIs as independently deployable services. There are certain characteristics around organizations around business capabilities, automated deployments, intelligent endpoints and distributed control of data.
Before we start on microservice style,