You have defined different Spring Boot profiles for your Java Domain Service service and want to activate one of them when deploying the service through an application composition project in order to apply a specific bunch of configurations.
You have developed a microservice and have a ready to use helm chart and image available.
In this course, you will learn everything important around application composition within . You will also practice how to compose an application.
If a Service is deployed through an Application, changes made in the design or the implementation of the Service will not automatically be reflected in the deployed Application. Instead, the Application needs to be explicitly adapted to use a newer version of the Service component in order to apply the changes.
You want to consume an Event from a Service that has already been published so that you can implement logic that is executed when the Event is triggered.
Your web browser is designed to by default disable Cross Origin Resource Sharing (CORS) which allows sharing data across different origins ; i.e. the combination of scheme, domain and port. There are some situations where you will need to enable CORS and this can be done across a whole project (Deployment target), for a certain service or for a component in your composed application.
To debug your Java Solution, you can debug them in a number of ways. JUnit is one of them, and using the docker images for the events locally is another method. For more info, please see here.
You want to deploy your built frontend through an application in the Workbench and provide a route for it so that it is ready to use.
You have implemented changes in your Service and want to release them so that the new version could be used in an Application.
For your asychronous communications within and between services, you want to establish well defined "contracts" of the event payload data for everyone to use by means of using the new schema registry supported feature in .