When I was interviewed for my role at MuleSoft a few months ago, I was asked if it was possible to have more than one System API layer. I froze — and it’s possible this question has crossed your mind as well.
After the interview, I sketched out some use cases to figure out the answer to this question. It did not take long for me to understand that API-led connectivity is not strictly restricted to three layers — System API,
Integration is critical for all businesses, and the right Integration Platform-as-a-Service (iPaaS) is a key piece for any organization looking to accelerate digital efforts. However, truly unlocking your data and systems is about more than just connecting systems and applications. To build an agile and future-proof business, you need an integration strategy and partner that recognizes that iPaaS alone isn’t the end solution.
Application networks and APIs are a key enabler of the composable enterprise, creating a more agile organization and allowing for rapid responses to changes in market conditions, technology disruption, and business demands.
Adopting an API-led approach in your composable enterprise allows each newly developed API to add incremental value to your overall application network and market place. It allows new capabilities and architectures to emerge over time,
This blog post is based on the internal work of Thomas Baumgart, former MuleSoft Client Architect, and is now being published by MuleSoft.
In previous blog posts, we’ve discussed business agility, the various types of architectures, and an API-led approach with Anypoint Platform. In this blog post, we’ll cover the differences between MuleSoft’s unique API-led approach and an SOA-based architecture.
Many organizations undergoing digital transformation are under pressure to connect their applications, data, and devices — most often the path to success is moving to an API-led integration strategy.
SE2 is a technology vendor providing insurance software-as-a-service to its customers. SE2’s main product is the SE2 Aurum® Platform. To ease the buying process, SE2 Aurum® needs to integrate with many disparate systems. Below, Ambrish Patel and Indra Bhattacharya, Enterprise Architects at SE2, describe how SE2 transformed the life insurance new business and underwriting support process using MuleSoft to switch to an API-led integration approach.
MuleSoft is continuously striving to increase the clock speed of digital transformation for our customers, and today we’re pleased to partner with leading robotic process automation (RPA) companies to make it even easier to automate repetitive tasks and unlock data from legacy UIs.
Managing complexity is at the heart of supply chain strategy. Whether it’s in logistics, planning, procurement, or warehousing, supply chains provide firms with a competitive advantage by adding intricate, automated, or resource-heavy capabilities that can’t be easily replicated.
In light of the digital transformation imperative, IT has taken center stage as a key enabling function supporting the survival and growth of the modern energy and utilities provider. New technologies and tools support anytime, anywhere access of data, real-time processing, and increasingly rich analytics functionality. As executives and line-of-business owners increase the pressure on IT teams to deliver these new capabilities to support strategic business objectives, demands on IT have exceeded IT delivery capacity.
In my previous blog posts, I outlined a number of concepts and challenges faced across governments building digital ecosystems. With those building blocks, how can we build a secure application network for governments to support the concept of citizen journeys?
