This PR is still part of the extra-components version of the generator.
It will allow the user to run the generator using a flag --> yo systemic --extra-components.
If the user decides to use the flag then he is going to get the show-case version of the resulting microservice as describe in #48 .
If he decides not to use it, running the generator with no params --> yo systemic, then he will get as a result the basic no-business-logic version of the microservice.
With this approach we get rid of the Would you like to have a showcase including extra components? useless question.
Notes
This would be the final PR made to the v2.3.x branch branch.
With this in place we have finally reach a point in which we have:
The default generator (yo systemic) that:
highlights the un-opinionated approach of systemic about how to create microservices. We give the users a base and they define which type of business logic they want to implement (rest + DB / bus + DB / bus + blob / rest + third integration / etc.)
The generator with the flag (yo systemic --extra-components) that:
lets the user understand how to get the most out of a systemic based microservice.
fosters the implementation of an Hexagon Architecture for the microservice.
gives an hint of how to manage multiple business logic workflows in the same microservice.
gives an hint of how to manage versioning of components.
gives an hint of how to manage integration testing.
gives an hint of how to manage the infrastructure for a given microservice with docker-compose.
gives an hint of how big the systemic ecosystem is when it comes to already available npm systemic components (systemic-rabbitmq, systemic-mongodb).
But still we:
do not pollute the systemic-generator code and have to maintain 2 version of it (the basic yo systemic and the advanced yo systemic:advanced)
do not have to bother the user with the useless and always NO answered question Would you like to have a showcase including extra components?
We need now to finally decide if we are going to merge the v2.3.x branch into master or not.
feliun
commented
4 years ago
Description
This PR is still part of the extra-components version of the generator. It will allow the user to run the generator using a flag -->
yo systemic --extra-components.yo systemic, then he will get as a result the basic no-business-logic version of the microservice.With this approach we get rid of the
Would you like to have a showcase including extra components?useless question.Notes
This would be the final PR made to the v2.3.x branch branch. With this in place we have finally reach a point in which we have:
yo systemic) that:yo systemic --extra-components) that:But still we:
yo systemicand the advancedyo systemic:advanced)Would you like to have a showcase including extra components?We need now to finally decide if we are going to merge the v2.3.x branch into master or not.