Docker compose supports extending compose files, which is very useful for overriding specific parts of your configuration. This is very useful at least for development environments and may be useful in small deployments too. The idea is having a base shared compose file you can override for different teams or environments. You can combine that … Read more
You trouble is how model your microservices. In term of microservices the second approach is most appropriate, which expose its logic through API. Always when you model your microservices keep in mind the follow facts. Loose Coupling: When services are loosely coupled, a change to one service should not require a change to another. The … Read more
The ‘problem’ with a multi-module parent pom is that, without complicated profiles, it locks the modules in the same release cycle (assuming you’re using the Release Plugin, which you should be). The way I work with Maven is to have a parent pom that declares: common dependencies (logging APIs, JUnit, etc). common plugins. all dependencies … Read more
In my case I had an erroneous reference in Dependencies > Packages to Microsoft.VisualStudio.Azure.Containers.Tools.Targets Removing the reference fixed the error.
I got it working. Basically the way to do it is to create two separate projects. Let’s say – one is a createMicroservice and another is just an HTTP app (but could easily be another microservice). I used a “normal” app just so I can call it easily for testing. Here is the main.ts file … Read more
each microservice need its own database A separate DB per microservice is not a prerequisite (nor a requirement, really). You can have as many microservices as you want working on top of the same database, but use different schemas for example. The bounded context of a microservice should be the boundary. Lets say we have … Read more
The evils of too much coupling between services are far worse than the problems caused by code duplication The author is very unspecific when he uses the generic word “coupling”. I would agree with certain types of coupling being a strict no-no (like sharing databases or using internal interfaces). However the use of common libraries … Read more
This blog post lists some reasons why you should not run production databases in containers. It also references another blog post describing problems with updating docker and unstable storage drivers. The main points here for me boil down to this: Dodgy storage drivers. This may be less of a problem when you write your database … Read more
A standard that I’ve followed in the past is to use web services when the key requirement is speed (and data loss isn’t critical) and messaging when the key requirement is reliability. Like you’ve said, if the receiving system is down, a message will sit on a queue until the system comes back up to … Read more
The Microservices architectural style tries to allow organizations to have small teams own services independent in development and at runtime. See this read. And the hardest part is to define the service boundaries in a useful way. When you discover that the way you split up your application results in requirements impacting multiple services frequently … Read more