Vaughn and John discuss API portfolios and monetization, covering topics such as API First, REST, GraphQL, gRPC, and using APIs with DDD. They explore the concept of ESBs, messaging in API development, and API design patterns. The conversation also delves into converting data sources into service-compatible formats, API marketplaces, and upcoming discussions on internal API and DDD.
MuleSoft's API-led and API-first approach revolutionized the integration framework by allowing organizations to choose the appropriate backend technology and shifting the focus from ESBs to a more versatile integration framework.
The increasing trend of external monetization and productization of APIs has given rise to new API management vendors, with sectors like financial services and healthcare exploring API monetization, while energy sectors are capitalizing on location-based data.
Deep dives
ESBs and their Origin as Enterprise Service Buses
ESBs originated as an architectural pattern documented in the mid-2000s. They aimed to centralize the handling of SOAP APIs, providing mediation, routing, security, authentication, and reliable delivery. Initially, messaging brokers like JMS were used, and different implementations of ESBs emerged. However, ESBs faced challenges such as canonical data models being complicated and requiring consensus across different domains. They also posed scalability issues as central IT teams managed the bus, leading to bottlenecks in adding new services. These factors led to organizations operating in silos, rendering the ESB pattern less effective.
Evolution of ESBs and the Rise of MuleSoft
MuleSoft, an integration and transformation framework, gained popularity by rethinking the value of ESBs. They emphasized embedded transformation and integration in Java and Spring Apps, rather than relying on a monolithic ESB. MuleSoft introduced the concept of API-led and API-first implementations, where APIs were composed and designed from a contract-first perspective. This approach allowed organizations to choose the appropriate backend technology. MuleSoft's success stemmed from their ability to support both domain-centric and transformation-focused microservices. They shifted the focus from ESBs to a more versatile integration framework.
Challenges and Decline of ESBs
ESBs faced backlash due to two major challenges. First, canonical data models became complex, making it difficult to achieve consensus across different domains. Second, centralized IT teams managing the ESBs led to friction and bottlenecks. ESB vendors struggled to meet the evolving requirements of different organizations. This resulted in organizations deploying services in silos, undermining the purpose of the ESB pattern. The concept of 'dumb pipes, smart endpoints' was overshadowed by the complexity and complications of ESBs.
Current Trends and Future of API Management
As organizations mature with internal APIs, they are starting to focus on external monetization and productization of APIs. This trend has given rise to new API management vendors that address the challenges of integrating, commercializing, and securing APIs. Existing verticals like financial services and healthcare are exploring API monetization, while newer sectors like energy are finding ways to capitalize on location-based data. The future of APIs could involve event-driven architectures and exploring messaging protocols beyond HTTP, although HTTP-centric approaches are expected to dominate initially.
Vaughn and John discuss API portfolios and the increasing number of APIs being made available for public consumption. From John's deep knowledge and background in APIs, the timeline of early to contemporary technologies is considered for perspective. From there, they discuss monetization of strategic APIs using his innovative HyperCurrent product. In their dialogue, API First, REST, GraphQL, gRPC, asynchronous message-based and event-driven, the future of APIs and API products, as well as using APIs while applying DDD are covered. It's an opportunity to tap the knowledge of a long-time API design and tools expert.
John D'Emic is the CTO and Co-Founder of HyperCurrent, the leading Enterprise API Monetization Platform. He is an architect, full-stack developer, and author with over 20 years of experience. Besides co-authoring both editions of Mule in Action, John has published numerous blogs, articles, and white papers.