Of course - when starting from scratch - the simplest way of deploying Microcks is to use our Helm Chart or Operator that will handle the setup of all required dependencies for you. Deployment OptionsĪt this point, you should have a better vision on Microcks architecture and should be wondering: should I deploy this as a monolith? Not at all, we provide different deployment options to better suit your environment. This architecture can also be deployed using Docker Compose using the docker-compose-async-addon file as described in enabling asynchronous features. When deploying on Kubernetes you will have to use our Helm Chart or Operator installation methods for that. □įor sake of simplicity we do not represent here the Zookeeper ensemble that may be associated with Kafka. We represented Kafka ones ( X broker) as well as brokers ( Y and Z) from other protocols with respect to our roadmap. The schema below represents this full-featured architecture with connection to outer brokers. An Apache Kafka broker that holds our private topic for changes and the public topics that will be used to publish mock messages by the microcks-async-minion.It retrieves these definitions from Microcks webapp at startup and then listens to a Kafka topic for changes on these definitions, The Microcks Async Minion ( microcks-async-minion) is a component responsible for publishing mock messages corresponding to AsyncAPI definitions as well as testing asynchronous endpoints.If you want to enable asynchronous API features, 2 additional components will be required: You can deploy this simple architecture whatever installation method you pick: from Docker Compose to fully featured Operator. You’ll see that users access the main webapp either from their browser to see the console or from the CLI or any other application using the API endpoints.įor sake of simplicity we do not represent here the PostgreSQL (or other database) that may be associated with Keycloak. The schema below illustrates this architecture and the relations between components. A Keycloak instance that holds the authentication mechanisms and identity provider integration.A Microcks Postman runtime ( microcks-postman-runtime) that allows the execution of Postman Collection tests and calls back Microcks for storing results,.Its associated MongoDB database for holding your data such as the repository of APIs | Services and Tests,.The Microcks main web application (also called webapp) that holds the UI resources as well as API endpoints,.In its simplest form, Microcks architecture is made of 4 components which are: This page will go through these topics, showing the different choices and options you may have depending on your target environment. Now that you have looked at the different installation methods of Microcks, you may want to have a high-level view of its architecture and deployment options.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |