Microservices

This reading is about microservices and well I’m going to talk about them. Here are some characteristics of microservices:

·        -  Componentization via Services: One main reason for using services as components is that services are independently deployable. If you have an application that consists of multiple libraries in a single process, a change to any single component implies to redeploy the entire application But if that application is decomposed into multiple services, you can expect many single service changes to only require that service to be redeployed.

·         - Organized around Business Capabilities: splitting up into services organized around business capability. Such services take a broad-stack implementation of software for that business area, including user-interface, persistant storage, and any external collaborations

·     -     Products not Projects: A development team takes full responsibility for the software in production.

·    -      Decentralized Governance: Rather than use a set of defined standards written down somewhere on paper they prefer the idea of producing useful tools that other developers can use to solve similar problems to the ones they are facing. These tools are usually harvested from implementations and shared with a wider group, sometimes, but not exclusively using an internal open source model

As you may have inferred microservices are great, however we do not really know the future but we know that many industries and companies are using it right know such as Netlfix, Amazon, The Guardian, and others. In my opinion this software architecture will be one of big influence in the future since the strategy it points out turns to be good for software development, however it restructures how software has been developed for the past years and people will need to learn about it.

This was a great reading for a useful tool.