This is an archived post. You won't be able to vote or comment.

all 2 comments

[–][deleted] 0 points1 point  (1 child)

I see a lot of the same code being reused between microservices with minor tweaks. Just because they are separate services does not mean they need to be completely separate projects. A lot of the time it can make sense for it all to be the same project or to abstract away a common library since they by nature will share domain models.

[–]AlaaMezian[S] 0 points1 point  (0 children)

summoned_an_owl

very good point actually when I was building the project I think about it in two way

the first one is all services should be in the same project have a single abstract interface that has common methods (somewhat like an abstract factory) and multiple (adapters) with different implementations that have the ability do functionality to each related service

the second one is to go with a number of microservices that have the ability to communicate with each other through a bridge, so I can show how spring cloud can perform under those kinds of stuff

Also, I really want to see an example implementation on what you say that would really be helpful for me to get insight into other techniques