Microservices



Microservices

This week the article to discuss is "Microservices" which was witted by  James Lewis and Martin Fowler.

So, first of all, the term Microservice Architecture describes a way of designing software in order that applications have functions, as suites of independently small deployable services. As each one of those is running its own processes but should communicate with the others is usual the usage of an HTTP resource API.

An interesting thing about Microservices is that this services are built around business capabilities and are independently deployable by automated deployment machinery.

Something mentioned in the article that actually I actually liked is that is a bare minimum of centralized management of the services, so they could be written in different programming languages and use different data storage technologies, allowing more flexibility, of course the fact that you can do this, does not mean that you should but it is possible if needed.

Complementing the idea, the authors explain what is a microservice style and how it works comparing with the monolithic style, basically a monolithic application is built as a single unit. This applications are usually built in three parts: a client-side user interface (like HTML pages), a database, and a server-side application. 

The principal problem whit this is that any changes to the system involve the building and deploying of a new version in the server-side. In other words, a “monolithic” application describes a single-tired app, in which the user interface and data access code are combined into a single program from a unique use platform.

Some of the shared characteristics of a Microservice Architecture, in the majority of the cases.

  • -          Componentization via Services
  • -          Organized around Business Capabilities
  • -          Products not Projects
  • -          Smart endpoints and dumb pipes
  • -          Decentralized Governance
  • -          Decentralized Data Management
  • -          Infrastructure Automation
  • -          Design for failure
  • -          Evolutionary Design

Comentarios

Publicar un comentario

Entradas populares de este blog

Is Design Dead?

Is Design Dead? I am going to write about the article “is Design Dead?” By Martin Fowler, it was a interesting article and was written in a unfamiliar way considering the title. He starts talking about the extreme programming and how it is one of the causes of the poor pre design that nowadays is (barely) used for big or small development. Software development needs like almost everything a design which defines not only how it will work, but how to make the specific modules and what job they are going to perform to accomplish a global goal. And well he basically explains the differences between planned design an evolutionary design, that is the reason why I think the title is funny, two kinds of design but he says it is dead, basically what happens is that, the extreme programming and the constant use of the technique pushes the developers to use the evolutionary design. Why? Easy, the extreme programming is a practice thas searchs the simplicity in the creation of...
Leer más

Software Architecture

Software Architecture This week I read the chapter 14 of the book "Code Craft: The Practice of Writing Excellent Code" titled " SOFTWARE ARCHITECTURE Laying the Foundations of Software Design" the first thing we should do is define what is software architecture, as we use the word architecture sounds logical that a building comes to our mind, but talking about software we can take the idea of a structure, so the author told us we can join the concepts to create in our brain the idea of high level design but of course the reason of the “similarity” in the concepts comes because the software architecture is used to create a propitious place to make code, at the end this can be used as a guide for the development. Some benefits of the software architecture are that this helps to validate requirements and conditions of a project so it can be used in a more free way for the different areas like design and development and can help to “talk the same language”,...
Leer más

Understanding the SOLID Principles

This week the blog will talk about the article "Understanding the SOLID Principles" written by Edward Guiness, this is a brief summary that presents the definition of the SOLID Principles. The general objective of the SOLID principles, and so the author in the article, is to implement best practices in the creation of objects and classes in specific cases depending on the situation that is presented. And with you, the 5 principles *drumroll*: • Single Responsibility Principle • Open/Closed Principle • Liskov Substitution Principle • Interface Segregation Principle • Dependency Inversion Principle The first of this is the Single Responsibility Principle, it says that a class, should have just exactly one responsibility, just one reason or an only class of reason to exist. This responsibility should be implemented to the class, so for this reason a class just has one reason to be modified. Why implement this? Easy, in a big project you will have lots of classes ...
Leer más