3 years ago

Category: nginx, container

by Despite being a more complex solution than the more traditional Monolith, in Apiumhub, we believe that microservices are a good solution to many extremely common problems in software development, such as difficult and slow deploy process, large codebase that often lacks cohesiveness, difficulty for different teams to work simultaneously in somewhat related features due to conflicts, etc.Nevertheless, Microservices are used almost exclusively on the backend.

And this can be achieve using one of the following approaches: In this approach, all micro applications are put together in the Container application during the build process, and the result of this operation is then deployed to production. In this case, the Container application acts as a Monolith, and the micro applications are just dependencies that are used within. The main problem that arises with this method, is that whenever a new version of a particular micro frontend is pushed, it is necessary to go to the main project (Container), bump the version of the micro service, and push that change.