Explore the Application Network
After completing this unit, you’ll be able to:
- Explain the challenges with integration.
- Explain what an application network is.
- Explain how API-led connectivity is built into an application network.
- Identify the best practices of implementing API-led connectivity with a multi-layered API architecture.
Why Is Integration So Challenging?
The Fourth Industrial Revolution is upon us. Connectivity across people, applications, data, and the Internet of Things (IoT) is the cornerstone. As connected consumers, we are bombarded daily with new technologies that change the way we live.
As such, we’ve grown to expect powerful systems and functions. We expect them to work together seamlessly. And we expect businesses to deliver these functionalities faster than ever.
In order for our organizations to lead in the new digital economy, we must become Integration Trailblazers. Often deep within the ranks of an organization, an Integration Trailblazer is a strong advocate and evangelist for API-led connectivity; someone who understands the potential of APIs to revolutionize internal business processes as well as customer experiences.
This is especially true now, given the way businesses are presented with a huge number of tools to meet their customer's expectations. Let’s look at marketing as an example. Here are some of the companies that specialize in search engine optimization (SEO).
Keep in mind that these companies are hyperspecialized. They offer services that focus solely on one domain: SEO. This is actually three levels down from marketing technology as a whole—first there’s marketing technology, next there’s content and experience, and finally you arrive at SEO. If we take a step back to the top level, we find that there are over 8,000 total companies specializing in marketing technologies as a whole as of 2020.
That’s a lot of technology just for marketing! There are thousands more of these hyperspecialized offerings in Sales, Service, IoT, and so on. All these choices can create pain for established companies that have to rethink how they offer their services to customers. Here’s why.
- Companies want to plug new technologies into their businesses as quickly as possible.
- To get a 360-degree view of their customers and improve their experiences, new technologies must be easily integrated with existing systems.
But, to integrate quickly, developers often set up point-to-point connections, where each system is connected to every other system, using plenty of custom code.
Absent of an internal champion for API-led connectivity, little thought is given to the overall architecture of these integrations. Soon the next technology is brought in, more point-to-point integrations are built, and more complexity is added.
Add Unnecessary Complexity, Lose Agility
For many companies, this pattern can go on for years, maybe even decades, until there is a giant tangled mess at the core of the business. Point-to-point connections involve a lot of custom code and create tightly coupled systems. Tightly coupled systems come with dependencies, and minor changes to the integrations require complete rewrites of code.
Over time, the system becomes harder and harder to maintain and improve. As a result, the business loses the agility it needs to respond to sudden changes in their industry and the world—everything from disruptive startups to global pandemics—and constantly changing customer expectations.
By breaking up the tangled mess of integrations, businesses can once again be agile. They can incorporate new hyperspecialized technologies and quickly make changes to existing business processes and customer experiences. This is where MuleSoft comes in.
API-Led Connectivity to the Rescue
API-led connectivity is a methodical way of connecting applications, data, and devices through APIs. When the entire organization embraces a culture of API-led connectivity, developers and system architects are empowered to deliver applications and projects that avoid tightly coupled point-to-point integrations, in favor of:
- Clear contracts between systems
- Visibility and security
- Availability and resiliency
They are building the foundation of an application network—a seamless framework of applications, data, and devices. Businesses with application networks rely on a plug-and-play repositories of internally and externally-provided assets that they can use in an agile way.
There are a lot of terms to keep track of! Here’s a handy table to help you keep some major concepts straight and top of mind.
||A methodical way to connect applications, data, and devices through reusable and purposeful APIs; the opposite of point-to-point integration.
||A network of applications, data, and devices connected by reusable APIs, each built with the principles of API-led connectivity.
||MuleSoft's platform that provides many tools to design, build, deploy, and operate an application network.
||A person within the ranks of the company who champions the idea of API-led connectivity as an opportunity to revolutionize how business is done (and lead in the new, digital economy).
So, what does this all really mean?
As companies start to rethink their own IT in terms of API-led application networks, MuleSoft recommends building and organizing APIs into three broad categories.
- System APIs
- Process APIs
- Experience APIs
Think of these three layers of APIs as an example architecture to implement API-led connectivity, where each layer serves a specific purpose.
System APIs handle the minutiae of connecting to systems (think databases) such that users are insulated from any changes.
Process APIs shape data across System APIs, with the intent of modeling business needs and processes, to break down technology silos and make data more consumable.
Experience APIs reconfigure this data so that it is most easily consumed by its intended audience through apps and devices. APIs at this level are created with reusability in mind, without a dependence on the source systems from which that data originates.
The MuleSoft Anypoint Platform provides a suite of tools to create these different kinds of APIs designed to either unlock data from systems, compose data into processes, or deliver an experience. Rather than being tightly coupled, they are loosely coupled components that can be reused to connect different systems. Much the same way Ford now outsources 99 percent of the parts that go into its cars and trucks, be sure to reconsider whether it makes more sense to outsource certain internal capabilities to 3rd party offerings via the API economy.