7/29/2023 0 Comments Bounded context in microservicesTraditional approaches to concurrency are based on synchronizing shared mutable state which is difficult to get right, as it often involves locking and coordination. What is an Actor?Īctors is another decomposition model that allows dividing a system into smaller isolated tasks or actors that can run concurrently. The idea of slicing up your system into manageable chunks is the key here. Bounded context in DDD terminology focuses on the logical separation whereas Microservice focuses on the physical separation. This decomposition can be at the logical level (business capabilities - the reason for something to exist), component level (dlls, jars, source code repos), process level (web app, http endpoints) or the physical level (machines, hosts). Philip Kruchten’s 4+1 Architecture View Model describes software architecture based on multiple concurrent views.ĭefining services involves breaking an overall system into smaller isolated sub systems so that adding features to the overall system requires touching as few sub systems as possible. Doing CRUD through REST over HTTP does not change that. A service that only has data is a database not a service.Making it remotely callable through RPC/SOAP still does not make it a service. A service that has only a function is a function not a service, like calculation, validation (not be confused with DDD’s Domain Services which is a more granular concept).Anything with the word Service appended to it does not automatically qualify as a service. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |