by Sam Newman O'Reilly Publication
\nMicroservices are an approach to distributed systems that promote the use of finely grained servicies with their own lifecycles, which collaborate together.
\nMicroservices are small, autonomous servicies that work together.
\nCohesion - the drive to have related code grouped together.\nHow small? Small enough and no smaller.\nThe smaller the service, the more you maximize the benefits and downsides of microservice architectures.
\nIt might be deployed as an isolated service on a platform as a service (PAAS), or it might be its own operating system process. We try to avoid packing multiple services onto the same machine.\nTIGHT COUPLING -> Depends on each other!
\nWith a system composed of multiple, collaborating services, we can decide to use different technologies inside each one. Pick the right tool for each job.\nOne example I liked was a social applicaiton:
\nWe can just scale those services that need scaling, allowing is to run other parts of the system on smaller, less powerful hardware.
\nWith microservices, we can make a cgange to a single service and deploy it independently of the rest of the system. Code is deployed faster. If a problem occur, it can be isolated quickly to an individual service, making fast rollback easy to achive. New functionality out to customers faster.
\nThis has to do with teams.
\nThe reuse of functionality. With microservices, we allow for our functionality to be consumed in different ways for different purposes.
\nSmall applications are faster to re-write.
\nSOA is a design approach we multiple services colaborate to proide some end set of capabilities (its somehow similar to Microservice architecture). It is an approach that aims to promote the reusability of sotware; two or more end-user applications, for example, could both use the sane services.\nSOA doesn't touch all points which microservices do, like how big is to big.
\nArchitects have a joined-up technical vision. Somehow this term has been adopted in the Computer Science world. Sotware Architect.
\nZones? These are our service boundaries, or perhaps coarse-grained group of services. Architects worry less about what happens inside the zone than what happens between zones. \"Be worried about that happens between the boxes, and be liberal in what happens inside.
\n\"Rules are for the obedience of fools and the guidance of wise men\" - maybe Doublas Bader.\nStrategic Goals -> Principles -> Practices
\nIn this chapter the author goes on and on about standards for architects to follow by monitoring, setting interfaces, thinking about safety, implementing Governance, creating templates and more points in order to stablish a framework under which development can be done. Is more about team, but it follows the ideas above.
","frontmatter":{"date":"February 01, 2021","slug":"/blog/2021-04-01-building-microservicies-by-sam-newman","title":"Building Microservices by Sam Newman"}}},"pageContext":{"slug":"/blog/2021-04-01-building-microservicies-by-sam-newman"}},"staticQueryHashes":[]}