Using the catalog server

[leofolive]

Greetings, I'm interested in gaining a deeper understanding of the catalog server's role and necessity.

• Is it possible to achieve the same functionality by creating a utility within the existing package, thereby bypassing the need for an API?
• Additionally, could you please clarify the primary advantage of having an API for controlling path assembly?
• If the catalog is mandatory for a production application, is it necessary to deploy it? What is the impact of having this service offline? Furthermore, if it is mandatory to have the API in production, would it be a good practice to have API versioning to ensure that future additions of routes and version changes in the path don't break in production?

I'm using this project as a valuable learning opportunity to study its proposal and architecture, particularly with a focus on code splitting. Thank you for your assistance.

[leofolive]

@jbroma