The document discusses Mulesoft API versioning, detailing how to configure applications to support multiple deployed API versions simultaneously. It emphasizes best practices such as using semantic versioning, placing major versions in the URI, and managing autodiscovery IDs for differing major versions. Additionally, it includes insights on deploying and upgrading applications within this versioning framework.

1. A MuleSoft Guru
API Versioning

2. Contents
2
API Versioning
Configure application to enable multiple API
versions deployed at the same time
Demo
Best practices and possible cases
Summary of what we’ve learned
Summary
1
2
3

3. Semantic versioning
3
MAJOR
Backward incompatible
changes
MINOR
New functionality
backward compatible
PATCH
Bug fixes that are
backward compatible

4. Where to place API version in the URI?
4
Base path Application Name

5. DEMO
Create new application
Configure CloudHub deployment
Deploy application
Upgrade application to version v2

6. MAJOR version
Use only major version in
the URI. Skip minor and
patch parts.
API version in
HTTP Listener
Usually one major version
running
API version in
application name
Flexibility in development
and management.
Multiple versions running
concurently
Autodiscovery ID
Two different major
versions of the same API
do not share the same
autodiscovery ID
6
API Versioning
summary

7. Does anyone have any questions?
https://www.linkedin.com/in/prof-it-patryk-bandurski/
https://ambassdaropatryk.com
7
Thanks!