Microservices

Microservices

The term "Microservice Architecture" has sprung up over the last few years to describe a particular way of designing software applications as suites of independently deployable services. 
"The microservice architecture is an approach to developing a single application as a suite of small services, each running in its own process and communicating with lightweight mechanisms, often an HTTP resource API."

Enterprise Applications are built in three main parts: 
  1. A client-side user interface
  2. A database 
  3. A server-side application.
The server-side application will handle HTTP requests, execute domain logic, retrieve and update data from the database, and select and populate HTML views to be sent to the browser. 

Monolithic applications vs Microservices

Monolithic applications have some disadvantages just as:
  • "A change made to a small part of the application, requires the entire monolith to be rebuilt and deployed."
  • In a similar way scaling requires scaling of the entire application.
 





Microservice Architecture

Important things to take into account:
  • Componentization via Services: To build systems by plugging together components.
  • Microservice architectures will use libraries ("their primary way of componentizing their own software is by breaking down into services").  
  • From General to specific easier to treat separated components
  • Using services as components is a more explicit component interface
Conway's LawAny organization that designs a system (defined broadly) will produce a design whose structure is a copy of the organization's communication structure.



The microservice division focus on splitting up into services organized around business capability. 



"A common inspiration for this is Amazon's notion of "you build, you run it" where a development team takes full responsibility for the software in production."

In Overall the Microservice architecture set another paradigm most of us think is recent but no, part of what today is Microservice architecture has already being defined and used in other older approaches, still this architecture adds a new option on this vast programming area, these architecture has gained popularity in the last 10 or more years and It has being proved to be a reliable option if your problem fits on the structure of the paradigm.

References:https://martinfowler.com/articles/microservices.html

Comentarios

Publicar un comentario

Entradas más populares de este blog

Hidden Figures

Hidden Figures For me was unexpected to watch this movie on class, it surprised me a lot the way that address several topics that happened on the USA around 1960: the racism , the cold war, the launch of the Apollo 11 and of course the arriving of men on the Moon. I decided to divide this blog in three sections, to tell from my point of view this topic and how it's related with the movie. It's not a mystery the United States have always suffered of racism, an evil they have never being able to eradicate. The situation today is really different from the one lived on 1960, hidden figures portrait it in a close look on how those years were. Imagine being a woman and black in the late 1960, just 12 years have passed since women can vote, sexism is still predominant. Here is where Katherine Johnson, Dorothy Vaughan and Mary Jackson going against all adversities achieve individual success contributing directly on the success of the USA and of humanity itself. The cold war was
Leer más

The 4+1 View Model

The 4+1 View Model Developed on 1995 by Philippe Krunchten. This model break down the whole into sets of related parts. Is composed of the Logical View, the Process view, the Physical view, the Development view and the Use Case View. Logical view: Shows the parts that comprise the system it describes the system object model. And it has the following UML's: Class diagrams, state diagrams, object diagrams, sequence diagrams and communication diagrams. Process view: Describes as system´s processes it's UML is the Activity diagram. The Physical view: Maps software artifacts onto the hardware that hosts them. It has the deployment UML diagram. Development view: Gives a building-block view of the system which is composed of  system's modules, or components, including packages, subsystems, and class libraries. It uses the component UML diagram and the package diagram. Use case View: Show the system functionality, is helpful in defining and explaining the structure and
Leer más

Is Design Dead?

It seems that XP calls for the death of software design.  Planned vs Evolutionary Design  Evolutionary design: "The design of the system grows as the system is implemented".  The benefits of Planned design are varied just like the disadvantages that some XPers use to justify choosing XP instead of Planned. The author mentions the following disadvantages: You can't think all the issues you'll encounter when programming.  Designers are so busy designing they don't get much time to code any more.  Changing requirements. You can deal with the changing adding flexibility into the design to enable an easy change of requirements. One reason in favor to simplicity is economic. Doing work that's only used for a feature needed for tomorrow means loss of effort and so of money. Another reason is that a complex design is more difficult to understand than a simple design.  In  XPE  Kent gives four criteria for a simple system. Runs all the Tests  No
Leer más