Pet Store is a web portal which can be used by the customers for ordering accessories for their Pets.
This sample is a simple webapp which consists of 5 Docker images (4 microservices and a container to serve the web portal).
- Catalog (Catalog of the accessories available in the pet store)
- Customers (Existing customers of the Pet Store)
- Orders (Orders placed at the Pet Store by Customers)
- Controller (Controller service which fetches data from the above 3 microservices and processes them to provide useful functionality)
- Portal (A simple Node JS container serving a React App with Server Side Rendering)
All 4 micro services are implemented in node.js and portal web application is a React application.
This scenario has also been implemented by using cells, and you can find more information about that in the Pet-store cells sample.
Here, we wanted to demonstrate the same scenario by using the composites. Composites are simply a group of components, and it do not have control over inter-communication between components. Further, unlike cells, composites do not have network boundary or cell gateway to control the incoming and traffic cells. Therefore, composites will not have default ingress rules or OIDC flow created as we have demonstrated in the pet-store cells, and the users will have to perform operations such as creating ingress manually to allow the traffic into the composites.
In this sample, we demonstrate the use of composites with pet-store application, and this can be packaged and deployed in three different combinations as mentioned below.
In this approach, all 5 components involved in the pet-store application is grouped together as a single composite. As this is a single composite in this, users will have to create the ingress rules to allow the external traffic into the pet-store application. You can find more information about the detailed steps here.
In this approach, both frontend and backend components have been separated into two composites and deployed. We will have to create the ingress manually to allow the external traffic into the portal application as we have performed in All-in-one Compsite. You can find more information about the detailed steps here.
In this approach, the frontend(portal) application of the pet-store is deployed as a Cell and the backend components are grouped as Composite. Since the front end application is deployed as a Cell, the ingress rules are created by default by Cellery similar to the Pet-store cells sample. You can find more information about the detailed steps here.