We found a structure that works for our service.(eg clean architecture). That means we have a domain layer, a data access and application layer and of course our presentation layer which can be a rest endpoints layer. Now we want all our services to respect this structure and also we don't want to manually copy… Continue reading Maven Archetypes
Tag: Maven
Maven BOM
BOM stands for Bill of Materials. Basically we can use it to store in one place all the dependencies with their versions. It's useful in the case microservices are used to make sure same versions are used everywhere. Of course this is not necessarily a requirement for microservices, as you have the choice to build… Continue reading Maven BOM
Microservice versioning
Why do we need to version our microservices? Microservices are basically APIs. These are consumed by the clients. We should be able to evolve them without any impact to the clients. We should not force the clients to use the new changes in services and more importantly this should not break the clients. There must… Continue reading Microservice versioning
Build once vs build many
After we have written the code and compile it, the next step is to build and deploy it somewhere. We can go two ways here: build many times the code, deploy it many times build once the code, deploy it many times Build many This is the way many of you are familiar with, as… Continue reading Build once vs build many
Learn. Write. Repeat. 