Decoupling play store from container app
The objective of this space is to lay down a clear plan for decoupling the play store from the container application.
- Offload the maintenance overhead
- Avoid collision
- Create more modular components
The whole idea is revolving around the micro frontend. The microfrontend is a type of architecture where a web application is divided into different modules or individual functions, implemented autonomously, allowing frontend teams the same level of flexibility and speed that microservices provide to backend teams. The main application will be served as is however the plays will be hosted separately and when a play is being requested by the container app, it will be served through module federation (or any other mechanism for microfront end) An important point to note here is, we will not be creating an individual app for each play, rather a group of play would be identified automatically and provide an identity. The same identity needs to be informed to the container app to create an appropriate route table
- Each play will be having its own package.json
- A play will be assigned to a group automatically when merged
- These groups need to be built separately
- All package.json files will be merged at the group level
- Route table in the container app needs to be updated accordingly
#Backward compatibility The major housekeeping job involved here is to translate existing plays to this new proposal. However, I guess there is no other option than bite the bullet
TODO...