Skip to main content

Introduction to MuleSoft

Mule ESB is a lightweight and highly scalable Java-based enterprise service bus (ESB) and integration platform provided by MuleSoft. Mule ESB allows the developer to connect applications easily and quickly. Regardless of various technologies used by applications, Mule ESB enables easy integration of applications, enabling them to exchange data. Mule ESB has the following two editions:

  • Community Edition.
  • Enterprise Edition.

What is API-led connectivity?

API-led connectivity is a methodical way to connect data to applications through reusable and purposeful APIs within an organisation’s ecosystem. These APIs are developed to play a specific role: unlocking data from systems, composing data into processes, or delivering an experience. 



What are the 3 APIs that enable API-led connectivity? 

API-led connectivity provides an approach for connecting and exposing building blocks in an ecosystem. Their scope can vary: within a specific domain, within a line of business (LoB), across an organisation spanning multiple LoBs or geographies, and into the external ecosystem. There is a natural tiering as well that moves from the system of records to the system of engagements.  

  • System APIs 
  • Process APIs 
  • Experience APIs 
System APIs usually access the core systems of record and provide a means of insulating the user from the complexity or any changes to the underlying systems. They create the nouns of your business vocabulary into reusable building blocks. Once built, many users can access data without any need to learn the underlying systems and can reuse these APIs in multiple projects.

Process APIs interact with and shape data within a single system or across systems (breaking down data silos). They often represent the verbs of your business vocabulary. They help implement an organisation’s processes without having to worry about the source systems where data originates or the target channels through which that data is delivered. They lend themselves very well to automation capabilities and Bots.

Experience APIs are catered toward delivering a delightful end-consumer experience. They get their power by maniacally focusing on the consumer and reusing the building blocks already created (typically in the form of System or Process APIs). Often built by a different persona, they can speed up delivery by working from the API specs built as a part of the design-first approach. 


Anypoint Platform components

  • API Designer is a web tool that a developer can use to design and document an API, and then share that design with team members.
  • API Manager is a component to manage APIs and secure them via an API gateway by creating policies around API calls and throttling.
  • Anypoint Studio is a desktop-integrated development environment (IDE) for building your APIs.
  • Anypoint Connectors are a set of built-in connectors that a developer can use to integrate applications with thousands of third-party REST and SOAP.
  • Anypoint Analytics is a tool to track API metrics, such as performance and usage. It can be also used to create custom charts and dashboards to visualize API performance.
  • Anypoint Runtime Manager is the interface to Anypoint Platform which provides a unified view to the developer of all of your apps, servers and APIs. •Anypoint Exchange is a hub used for storage and accessing APIs, templates, connectors, documentation and other resources.•Anypoint Monitoring is a dashboard to monitor applications health. •Anypoint Visualizer is a graphical tool which displays APIs and their dependencies.




Anypoint Studio

  • An eclipse based “drag and drop” integration development environment (IDE).
  • Used for designing, developing and testing Mule applications.
  • Contains a visual editor and has an embedded unit testing framework.

Next > CouldHub

Comments

Popular posts from this blog

Microservices design patterns

Microservices design pattern Next :  saga-design-pattern-microservices

Integration Design Patterns

Understanding Integration Design Patterns: Integration design patterns serve as reusable templates for solving common integration problems encountered in software development. They encapsulate best practices and proven solutions, empowering developers to architect complex systems with confidence. These patterns abstract away the complexities of integration, promoting modularity, flexibility, and interoperability across components. Most Common Integration Design Patterns: Point-to-Point Integration: Point-to-Point Integration involves establishing direct connections between individual components. While simple to implement, this pattern can lead to tight coupling and scalability issues as the number of connections grows. Visualizing this pattern, imagine a network of interconnected nodes, each communicating directly with specific endpoints. Publish-Subscribe (Pub/Sub) Integration: Pub/Sub Integration decouples producers of data (publishers) from consumers (subscribers) through a central ...