Microservice architecture of the e-commerce system.
DOI:
https://doi.org/10.34121/1028-9763-2024-1-70-76Keywords:
e-commerce systems, architecture of information systems, microservices, microservice architecture, системи електронної торгівлі, архітектура інформаційних систем, мікросервіси, мікросервісна архітектураAbstract
The article explores the fundamental requirements for microservice architecture in information systems and justifies its suitability for e-commerce information systems. The concept of microservice architecture is based on developing software applications as a collection of independent modular services aligned with business capabilities and priorities. The characteristics of service interaction and factors influencing architectural decisions are discussed. Microservice architecture's flexibility to employ different technologies and platforms for individual services is highlighted, allowing the adaptation of technical solutions to the unique needs of each service. Functional, non-functional, and business requirements for e-commerce systems are defined, and an architectural approach for web services is proposed. This approach is based on a client-server and microservice architecture, enabling both horizontal and vertical scaling of the server-side components. The architecture involves creating separate services to correspond to distinct business functions, facilitating further scalability and expansion since each microservice can be deployed independently. A list of business requirements for microservices in an e-commerce information system, along with the specifications for their implementation, has been formed. An app architecture for the e-commerce system is presented, comprising a collection of microservices that collectively constitute a comprehensive e-commerce system, and the tools for practical implementation are justified. This architecture effectively embodies the advantages of the microservices development approach, allowing the system to dynamically adapt to changing business needs. It provides scalability and simplifies system maintenance, rendering it more agile and prepared to meet the challenges of modern business and technology.References
1. ISO/IEC 15288. Systems and software engineering – System life cycle processes. [Valid from 2008-03-18]. 70 p. (International standard).
2. Configure ESLint. URL: https://eslint.org/docs/user-guide/configuring.
3. Pattern: Monolithic Architecture. URL: https://microservices.io/patterns/monolithic.html.
4. Paulk М.C., Weber C.V., Curtis B., Chrissis M.B. et al. The Capability Maturity Model: Guidelines for Improving the Software Process. Boston: AddisonWesley, 2015. 456 р.
5. Amazon API Gateway. URL: https://aws.amazon.com/api-gateway.
6. Spring Cloud. URL: https://spring.io/projects/spring-cloud.
7. Service Registration and Discovery. URL: https://spring.io/guides/gs/service-registration-and-discovery.
8. Spring REST with a Zuul Proxy. URL: https://www.baeldung.com/spring-rest-with-zuul-proxy.
9. Design Patterns Typescript. URL: https://refactoring.guru/design-patterns/typescript.
Стаття надійшла до редакції 15.10.2023
Published
Issue
Section
License
Copyright (c) 2024 Mathematical Machines and Systems

This work is licensed under a Creative Commons Attribution 4.0 International License.
