Hot answers tagged

6

In a SOA application, instead of a monolith component solving some problem, you have multiple services - each dealing with its own business concern - that now must communicate and collaborate to solve the same problem together. That means they need to know about each other and what each one is doing. That's a dependency, plain and simple. Services are self ...


3

There are differing opinions on how bounded contexts should relate to microservices, some of these opinions are largely predicated on how a microservice is defined. Those who say there shouldn't be a one to one correspondence are generally conceiving of a microservice as physical service, a process like a ASP.NET application. They argue that many services ...


2

One way (whether this fits your environment is up to you) is decoupling the BillingService by giving it its own data storage: Set up a system where the various reservation services propagate the data which is necessary for the billing service Set the billing service as a receiver for these data updates Store the data in the billing service itself Pros The ...


1

Think of the SOLID Interface segregation principle (not exactly the situation here, but kind of close): you want to limit what the UI can access, especially if you are dealing with something that will be exposed over the internet. You also want the API used by the front end to return specific information pertinent and arranged in a way that is useful to the ...


Only top voted, non community-wiki answers of a minimum length are eligible