Problems in #Microservice #QA and #Solutions

One of the major task of DevOps is a speedy delivery of Microservice into production. The major objective of QA and Testing is to find as many bugs as possible. Fixing these bugs slows down the delivery. The article describes this conflict in details, outlines problems in testing articulated by Mr Martin Fowler, proposes additional tests and explains how to improve quality of the released Microservices.

#Microservice #Protection based on the principle of #Zero #Trust

The task addressed in the article is about protecting Microservice’s functionality and resources in the inter-Microservice interactions. Known techniques like OpenID Connects, JWT and OAuth2 were reviewed from the perspective of Microservice interactions. It has been found that these techniques cannot be applied as-is to the Microservices either because unanswered questions to them or because of doubtful trustfulness of related workflows.
The article proposes two protective methods for Microservice (or service) that have sensitive functionality and/or resources. While the Basic Protection Method is just a classic identity verification and following access permission control, the method does not require single centralised Identity and Permission Authorities. The latter can be distributed as needed following the distribution of Microservice-based applications. The Closed Optimised Protection Method replaces Identity and Permission Authorities with Dependency Catalogue Service per application and provides full protection with performance comparable with OpenID-JWT/OAuth2.

Split and Join of #Functional and #Informational #Microservices

Article defines Functional Microservices using gRPC interface versus Informational Microservices accessible via RESTful interface. The Functional Microservices are validated against distortionless criteria. The code example of Interface definition for Functional Microservice is provided together with options allowing passing data together with function invocation.

#Distorted #Microservices

People like rubbish because it is convenient… Almost a Fairy-Tale about Microservices Are We Clear about What is What? Let’s Expose the ‘Devil’ that is Sitting in Details Distortions 1 to 12 A First Glance on Modelling Distortionless Microservices Almost a Fairy-Tale about Microservices Once upon a time, technology was conquered by marketing buzz and …

#Contribution of #Architects into #Testing

Article discusses issues with modern light-weight testing applied via automation in DevOps practice and states that such testing is not necessarily enough for quality products, especially in the case of distribution in Cloud.

Multiple Ignorant #Faces of #Microservice

Published on August 16, 2019 It seems we cannot say explicitly that a Microservice is a Service. Here is a clear (to me) boundary between what Microservice implements and how it is used. At least, we know that Microservice is a small application realising the particular business function and providing a certain outcome. End of …

Inevitable #Distributed #Transactions for #Microservices

Published on July 23, 2019 Part 1 CONTENT Business Case Does Compensating Transaction Compensate? DT Transaction Manager / Orchestrator Orchestrated DT over multiple MS DT Implementation Options (how to) Business Case For many years technology tries to resolve a contest between business operational logic needs and technology means available for the logic implementation. This race …

#Implementation-agnostic #Logging for #Microservices

Published on May 10, 2019 After several years of using Microservices, people still debate what would be the best or minimally sufficient logging mechanism for independently deployed and loosely-interacting autonomous Microservices. Nowadays, when DevOps are responsible not only for the fast development and deployment, but also are made liable for supporting produced Microservices, the perception …

#Rules #Pattern for #Microservices

Published on July 9, 2019 “…back to the future”. Industry counts many different applications where components have to make automated decisions about something. Typical representatives of such applications are Workflows, Business Process Automation and alike.  The values of gathered experience are significant and it would irrational to lose them only because developers use new technologies …

#Microservice #Polling: #Tandem #Pattern for Reliability

Published on April 30, 2019 Intent This pattern increases durability of polling data by a Microservice (MS) and, as a result, increases robustness of the overall application or system. A Microservice, in contrast to SOA Service, can initiate its work based on a schedule with no other elements of the Application (App) being aware of …

#Sib #Pattern for #Microservice #Fault #Tolerance

Published on March 3, 2019 Fault tolerance requirement was known for a long time before Microservices were defined. This requirement has surfaced again because when working with relatively small applications or components like Microservices, it is much easier to observe fault tolerance and it replicates at a higher scale than when working with monolith applications. …

#Microservice #Database #Anti-#Pattern

Published on February 24, 2019 By definition, Microservices (MS) are supposed to possess such service-oriented aspects as being independent (from what: from each other, or from environment, or both, or this is a signal of different ownership of the MS in the same Application),  autonomous (can perform its business tasks on its own), specialised. While …

Beware: Sprint Abuses SOA in Microservices

Published on December 22, 2018 For the last couple of years, people were debating whether Microservices realise SOA. With my experience in Services of 22 years, I can confirm that Microservices do realise SOA at a “teenager” maturity level, while Web Services and REST were at the kindergarten SOA maturity level. How am I count …

Jeopardy of an API Economy

2015 Why I am moving against the flow again? Why all around are getting excited about APIs and I don’t? Probably, this is because of negative post-taste after DOT-COMs and global webinisation of industry  15 years ago when the most sensitive information was offered to anyone, including competitors and simply not good people or it …

‘How-to’ for MoSCoW Method: Resolving Fundamental Problems

Published on December 8, 2018 The MoSCoW method exists for many years already and the common opinion is that this method is for prioritising requirements, business or technical. It is used for achieving a shared understanding (Problem #1) with stakeholders on the priority they (Problem # 2) identify for each requirement. Apparently, MoSCoW is only …

An API Economy under the Business radar

Published on November 8, 2017 While business is more or less familiar with the imperatives of global market and government regulation for different industries, new options and trends appearing via technology revolution are “new boys in the town” and require a special attention. We can anticipate that more and more resources will become available to …

Do we really need identity propagation in SOA and Clouds?

2012 IT developers and, especially IT Security specialists struggled for years trying to create an identity control at the enterprise level. The most known initiative and model in this area is Single Sign On (SSO) where an identity of an end-user can be propagated between systems and can be recognized across an enterprise. In today’s …

#Updated #Principles of #Service #Orientation

2014 Motivation Current Principles of Service Orientation (SO) were formulated about 15 years ago when Service-Oriented Architecture (SOA) fought its way up into the mainstream of enterprise IT. They are widely known from publications of Thomas Erl 1,2 where the vocabulary of SO was compromised for the sake of mass adoption of Web Service technology. …

#Patterns In The #Context of #SOA #Business #Services

2010 Introduction Along the evolutionary path through centuries, the Mankind  has found that we need some things stable, immutable, and even ‘untouchable’ to grasp the other constantly changing things. The examples of such immutable things include religion postulate, mathematical axioms and the Earth shape.  Nonetheless, sometimes, the knowledge acquired in the evolution pushed us to …