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.
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 […]
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 […]
Published on July 21, 2019 For #Business & #Technology #Executives, Product Managers, and Business and #Enterprise #Architects The Subject & Context Recently Gartner published the research – “How Unlocks Digital Product Management Opportunities for New Value Creation”, authored by Analyst Lars Van Dam – has caught my attention with a new term “Digital Product Management”. […]
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 […]
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 […]
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 […]
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. […]
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 […]