In this chapter, we will use Anypoint Platform configured in Chapter 1

The Anypoint control plane is a collection of products, tools, and services that together function as the central hub for managing and governing MuleSoft application runtime deployments and APIs. This control plane is architected as a set of microservices, allowing this central hub to be scalable, highly available, and fault tolerant. Furthermore, the services were built with an API-first design. This means development teams and operations teams have APIs at their disposal that can be used to interact with Anypoint Platform. In fact, there are three ways to interact with the services and components in the Anypoint control plane:

• Standard web frontend
• Anypoint Platform APIs
• The Anypoint Platform Command-Line Interface (CLI)

These services can be incorporated into your CI/CD pipeline and provide insight into its processes and performance via alerts and audit logs. In this book, we will primarily use the user interface web frontend of...

The runtime plane, as described earlier, is where your programs run. This is where the HTTP connectors you add to flows will listen to the port you told it to listen to. It’s where the Dataweave transformation logic sits waiting for a payload to reshape. It is also the domain of Anypoint Object Store V2 and Anypoint MQ. In order to run these components, we must have compute, memory, storage, and network resources. In short, the runtime plane is the server or collection of servers used to run your applications.

Note

Anypoint Object Store V2 and Anypoint MQ settings are configured from the control plane.

The platform architect must consider several things when designing the runtime plane architecture. Let’s first look at the runtime deployment options.

Runtime deployment options

MuleSoft provides four options for where to execute the MuleSoft runtime engine:

• CloudHub – MuleSoft-managed infrastructure running in a...

As we have already seen, Anypoint Platform provides the components to design, deploy, and manage the APIs we build. The platform also provides the components, and in many cases the infrastructure, to run or execute these applications. Let’s take a quick look at the different components that support each of these phases in the lifecycle of API development.

Management capability

Earlier, we identified the Anypoint Management Center, and specifically Access Management, as the core service for user management and platform organization. The Management Center is also where we can find the core services focused on the operations and administration of the platform as well as any running API applications.

The screen in Figure 2.6 shows the options in the Management Center.

Figure 2.6 – Anypoint Management Center

The management capabilities in Figure 2.6 are detailed as follows:

• Access Management: This was described...

In this chapter, we looked in some detail at the control and runtime planes that make up Anypoint Platform. We considered some of the architectural decisions that need to be made and the business requirements that inform those decisions.

We looked at where the control plane and runtime plane can be hosted, and discovered two different ways to control access to the platform. We also considered the relationship between the control plane options and the influence those options have on the runtime plane.

We then took a quick look at the core services for designing, managing, and cataloging APIs within Anypoint Platform.

In the next chapter, we will look at Catalyst and the MuleSoft KnowledgeHub and see how we can leverage the Catalyst approach to increase the efficiency of our API projects.

1. What are the four hosting options available in the runtime plane?
2. Can you name the two capabilities that are unavailable when using Runtime Fabric for hosting the runtime plane?
3. What is Anypoint Exchange used for?
4. What are some of the considerations to keep in mind when determining where to host the control and runtime planes?
5. Describe the best practices for organizing resources in Anypoint Platform.

MuleSoft business group documentation: https://docs.mulesoft.com/access-management/business-groups

1. CloudHub, CloudHub 2.0, RTF, and standalone servers are the current options for hosting the MuleSoft runtime plane.
2. Object Store v2 and Anypoint DataGraph are not available when using RTF.
3. Anypoint Exchange serves as a catalog of reusable assets comprising APIs, Connectors, Accelerators, Dataweave, RAML fragments, and more.
4. Data regulations, proximity to data, and cloud readiness.
5. Create child business groups and share resources with those groups. Create an environment for each testing phase included in your project and/or corresponding to your testing methodology.