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.
Author, Laurell K. Hamilton, wrote “Questions are great, but only if you have the answers.” Many of you have questions about the Anypoint Platform and our product team has the answers! Here is our second installment of our Anypoint Quarterly FAQ, where we answer the most frequently asked questions.
This quarter, we will focus on questions regarding the upcoming releases: Service Mesh, Access Management 2.0,
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,
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.
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.
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.
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.
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.
