After recently being Certified in WSO2 APIM 3.2 I was super interested to see how APIM 4’s architecture matched up. I figured it wouldn’t change and just add on new features for APIM and add in Micro Integrator and Streaming. I was wrong! They’ve changed the deployment model. This makes sense in many ways.
Let’s take a quick trip down memory lane.
APIM 3.2 Deployment Profiles [1]
From this segmentation you then could create Highly Available clusters as needed.
APIM 4.0 Deployment Profiles [2]
To understand the new Deployment Profiles in the APIM 4 release you’ll want to first review the new Architecture and key Components page. [3]
Now it is clear how the new Deployment Profiles fit into the Architecture landscape. Also it is clear to see that API Gateway, Streaming Integrator, and Micro Integrator all live in the Data Plane.
As you can see the Deployment Profile simplification has really reduced the number of required server types in play. Now you can focus your CPU allocations to horizontal scaling where it makes the most sense.
If you really want to seperate out the Key Manager that is still possible as seen at [4]. If you think you need to do this I suggest having a conversation with a WSO2 Architect to review your Current Deployment Architecture first.