HOW to ARCHITECT for DEVELOPERS
The majority of new Technologies are refined and renamed old ones
by Michael Poulin & Kirill Derevenski European Journal of Business and Management (EJBM), ISSN 2222-XXXX (Paper) ISSN 2222-XXXX (Online) Vol X, No.X, 2011 Abstract This paper describes a comprehensive – and revolutionary – approach to effective organisational adaptation to change in a dynamic market environment. Disruption is all around and even the most established players …
Continue reading “Optimising a Target Operating Model through an Architecture of Business”
Part 1. Architectural Governance: What and Why A concept of an Architecture of Business organisation (AoB) includes four fundamental artefacts, one of which is an Architectural Governance (AG). The Architecture of Business’s AG is defined as a set of principles, policies and procedures or activities, by which The AG is designed in compliance with existing …
Continue reading “Architecture of Business: Architectural Governance”
Architecture of Business/Enterprise requires extension of Zachman Framework/Ontology to add contextual and ‘by whom’ dimensions
Ontology of the Architecture of Business/Enterprise with description (Organic Organisation Model supplement)
Are Clouds now heading to a Thunderstorm? by Michael Poulin, 2022. Does #Enterprise #Architecture need #protection in a #digital world? by Michael Poulin, 2022. If experts still define EA differently, what is EA actually? by Michael Poulin, 2022. This is the article #100; 12,184 Impressions. Shared Services in a Nutshell by Michael Poulin, 2022. Risks of …
What is system integration and what is not. API vs. Events. Point-toPoint vs. Platform. Which one to use when.
The article explains the gaps in applicability of ScrumMaster to individual Agile Spriner and describes the operational method that close these gaps and dramatically improved outcomes of ScopeMaster in application across increasing number of project sprints.
This is a complimentary comments set in support of the Code of DevOps Practice. Each statement of the Code is explainf in this document.
Code of DevOps Practice is an open proposal for organising creative work of DevOps in modern enterprise. The document includes: subject, cause, values, pillars and principles of the DevOps development as well as some best practice recommendations and a list of referred articles.
While DevOps have elevated delivery velocity to the level that only Sun is higher and made it the goal and work effectiveness criteria (regardless quality), they still claim they are agile. The article takes a look into Agile Manifesto and Scrum Guide for the role of velocity. Neither the Agile Manifesto nor the latest version of the Scrum Guide (2017) reveals velocity at all, but have many loopholes inherited by DevOps.
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.
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.
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.
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 …
The article briefly observes new risks, pros and cons for REST, gRPC and GraphQL interfaces for API and Microservices.
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.
The first time I heard about the automation of contract negotiation and agreement in 2001-2002. It was written in ebXML (backed by OASIS and UN/CEFACT). It was an amazing achievement because the first SML Conference took place just in 2001. The endeavour fails because of two major reasons, as I learnt later: Recent splash of …
This case is a perfect example where a business value requires an adequate technical instrument, but when the instrument is driven by technology convenience, nobody cares about the business values. We are talking about a well-known problem that UK Open Banking (OB) and EU PSD2 face with financial transactions. It seems that the technology considerations …
Continue reading “Jamming #ISO #20022 into #Open #Banking #API makes them #REST-ish, not #RESTful”
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 …
Continue reading “Multiple Ignorant #Faces of #Microservice”
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 …
Continue reading “Inevitable #Distributed #Transactions for #Microservices”
HOW to ARCHITECT for DEVELOPERS 