The article addresses the problem of designing continuous integration and delivery (CI/CD) pipelines for large-scale microservice architectures at the enterprise level. The object of the study is the CI/CD processes in distributed software systems built on the principles of microservice architecture. The subject of the study is the set of architectural patterns and anti-patterns of CI/CD that determine the efficiency, reliability, and security of software delivery processes in conditions of high distribution and heterogeneity of the enterprise technology stack. The fundamental architectural challenges caused by the distributed nature of microservices are analyzed: coordination and consistency of multiple independently deployable services, management of inter-service dependencies, ensuring environment reproducibility, security control across the entire delivery path, and pipeline observability. The causes and consequences of a non-systemic approach to CI/CD are examined — one that generates persistent anti-patterns which negate the key advantages of the microservice paradigm, namely deployment speed and independence, ultimately leading to the effect of a "distributed monolith" in delivery processes. The methodological foundation consists of a systems approach combined with the monographic method, comparative analysis of existing practices, and a classification method applied to develop the author's original multi-level typology of CI/CD architectural patterns and anti-patterns. The scientific novelty of the study lies in the development of an original classification of CI/CD architectural patterns and anti-patterns across six architectural levels: service level, coordination level, artifact level, infrastructure level, security level, and platform level. For each level, a dominant pattern and a characteristic anti-pattern are identified, enabling the proposed classification to be used as a maturity audit tool for enterprise CI/CD architecture. It is demonstrated that an effective solution lies not in the isolated application of individual practices, but in their integration into a unified internal development platform (Platform as a Product) that provides teams with standardized, secure, and self-service golden delivery paths. It is concluded that a systemic approach — encompassing pipeline decomposition, a single source of truth for artifacts, infrastructure as code, security shift-left, and a centralized service catalog — transforms CI/CD from an automation tool into a strategic asset that directly affects time-to-market, stability, and security of the enterprise's digital products.
A. A Kuznetsov (Thu,) studied this question.