Doorgaan naar hoofdcontent

Microservices reference architecture, tools and frameworks

"The Microservices train" made by Roger van de Kimmenade (see my Photos page)

Intro

I am a fairly newby within the Microservices world but I have more experience with Service Oriented Architecture, Event Driven Architectures and more. So lately I began to read more about the architecture style of Microservices. In each blog item or news item I come across a new name of a tool/framework. So the idea came to try to make a reference architecture and a toolsheet in which each tool is mapped to that reference architecture. I have come to a state that I can use your help! Which concepts are missing and which tools can I add?
Please leave comments.

Reference Architecture

This is my first go of a kind of hybrid Microservices reference architecture, in which an integration layer is used to expose COTS products and legacy.


Tool/framework sheet

The next sheet is freely available and contains a list of tools and frameworks, that can be used within the Microservices ecosystem. I know it is far from complete, so thats why i need you!
The type is the most clearest capability of the tool. The other capabilities are also present. This list of capabilities needs to be extended too. And also here your help is helfull !

Link to the sheet:
Labels:

Reacties

  1. NagaKishore11 juni 2018 om 03:19

    Really great information on Microservices....

    BeantwoordenVerwijderen
  2. Manish12 juni 2018 om 16:11

    This is good with respect to key ingredients like API gateways, service mesh, devportals and infra monitoring but what's still left and to be defined is micriservices own implementation enabling Saga architecture and all related aspects to achieve overall API strategies. I believe people are still implementing microservices in a very simplistic way which is not the case in real world.

    BeantwoordenVerwijderen
  3. Unknown30 juni 2018 om 10:18

    I think a traceability solution is a must. You can use Zipking for this capability.
    On the other hand, monitoring is important, but teams are not going to watch always every dashboard: you need a solutions for alerts too.

    BeantwoordenVerwijderen
    Reacties
    1. Roger van de Kimmenade30 juni 2018 om 11:31

      True ! I will add this to the reference architecture. Thanks! Would it be nice if this is implemented within ServiceMesh frameworks?

      Verwijderen
  4. Unknown7 juli 2018 om 11:44

    Etcd is not a service mesh, just a key value store, like zookeeper.

    Kubernetes can also provide reverse proxy functionality when using ingress. The actual ingress controller (proxy server) can be implemented using nginx.

    I think nginx deserves a place on the list as well.

    React is not a container manager/orchestrator. DC/OS however is.
    I personally consider using a container orchestrator an absolute must when delivering your microservices as containers. Kubernetes send to become the defacto standard.

    Also perhaps replace AngularJs with just Angular. (AngularJs is the classic/v1 version noone should be using anymore).

    BeantwoordenVerwijderen
    Reacties
    1. Unknown7 juli 2018 om 11:46

      Regarding monitoring and logging, you may want to add the ELK-stack as well.

      Verwijderen
    2. Roger van de Kimmenade8 juli 2018 om 10:50

      Thanks Robert for your valuable feedback! Appreciated. I have updated the sheet

      Verwijderen
  5. Bhanu Sree14 december 2019 om 10:30


    I found some useful information in your blog, it was awesome to read, thanks for sharing
    Microservices Online Training
    Microservices Training in Hyderabad

    BeantwoordenVerwijderen

Een reactie posten

Populaire posts van deze blog

OSB 10gR3 and SWA and MTOM

This blog is about using soap with attachments and the use of MTOM within the OSB (10gR3). A service is created that accepts a soap with attachment (DocumentService) and translates it to a service that accepts a binary element. MTOM is used for performance reasons for the second. Some notes: * For the use of attachments you need RPC-style document instead of the usual document-style. This due to the fact that the document-style limits a message to a single . * A service can not have both SWA and MTOM within OSB. First a WSDL is setup for the DocumentService: The $attachments variable holds the attachments and the body holds the attachment data. Also other data is stored within the attachment element (see h
12 reacties
Meer lezen

Microservices mindmap

"The tree" - See also   my photo page When you are fairly new within the Microservices land, there are a lot of terms fired at you. So also for my own understanding i have made a mindmap. I think it has a good status now, so that i can share it with you. As always feedback is very welcome ! You can download the mindmap here .
47 reacties
Meer lezen

Book review: Data Management at Scale (Piethein Strengholt)

 This blog is a review of the book "Data Management at Scale (See also at bol.com ) Data Management is a hot topic nowadays and this book does a fantastic job at adding value to this topic. It is a must read and one of the few technical books I finished reading in a weekend. The book gives a fantastic overview on how to implement a Data Mesh data architecture. The Data Mesh concept is explained by Martin Fowler here . The book is a good mix between conceptual and implementation architecture level. It gives a lot of examples of how this architecture at scale can work, for both small and big companies. It is practical and I used it to implement it at one of my customers. The book describes an architecture in which the focus is on the DIAL (Data- and Integration Access Layer).  On a high level the book covers the following topics: The key principles for data management at scale - Domain-Driven Design  - Domain Data Stores - Meta data management Ready Data Store The concept of servin
5 reacties
Meer lezen