A Platform-Independent API Integration Architecture for Scalable Enterprise Commerce Solution
Main Article Content
Abstract
In today's enterprise commerce ecosystems, achieving interoperability in enterprise resource planning (ERP), customer relationship management (CRM), inventory management, fulfillment, pricing and customer intelligence systems becomes more critical than ever as the back-end is becoming more complex and heterogeneous. Traditional integration models often create rigid dependencies between business applications and the underlying operational platforms, which can limit the flexibility of the system's architecture, reduce interoperability, make integration more complex, and present major constraints for enterprise modernization efforts. The restrictions are especially stark when part of a large-scale digital transformation initiative that entails shifting enterprise technology environments and decentralized operational environments
The paper describes the platform independent API integration architecture that can support scalable interoperability between enterprise commerce platforms and heterogeneous backend systems by abstracting the details of these integration, defining a set of canonical service models, and building a set of reusable orchestration layers. The proposed architecture in enterprise transformation programs explored in this paper decreased the number of direct integration dependency points by about 80.9%, decreased average deployment time from 14.2 hours to 3.8 hours, and reduced the percentage of integration failures from 20.0% to 2.9% of the deployments as compared to point-to-point baseline. A three-year total cost of ownership (TCO) analysis shows estimated savings of more than 64.4% when replacing legacy integration architecture with the canonical abstraction architecture. These quantitative results validate the architectural model as a scalable, budget-friendly and flexible platform to support enterprise commerce modernization at scale
Article Details
Section
How to Cite
References
1. Alshuqayran, N., Ali, N., & Evans, R. (2016). A systematic mapping study in microservice architecture. In 2016 IEEE 9th International Conference on Service-Oriented Computing and Applications (SOCA) (pp. 44–51). IEEE. https://doi.org/10.1109/SOCA.2016.15
2. Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables DevOps: Migration to a cloud-native architecture. IEEE Software, 33(3), 42–52. https://doi.org/10.1109/MS.2016.64
3. Cerny, T. (2018). Aspect-oriented challenges in system integration with microservices, SOA and IoT. Enterprise Information Systems, 13(4), 467–489. https://doi.org/10.1080/17517575.2018.1462406
4. Cerny, T., Donahoo, M. J., & Trnka, M. (2018). Contextual understanding of microservice architecture: Current and future directions. ACM SIGAPP Applied Computing Review, 17(4), 29–45. https://doi.org/10.1145/3183628.3183631
5. Di Francesco, P., Malavolta, I., & Lago, P. (2017). Research on architecting microservices: Trends, focus, and potential for industrial adoption. In 2017 IEEE International Conference on Software Architecture (ICSA) (pp. 21–30). IEEE. https://doi.org/10.1109/ICSA.2017.24
6. Dragoni, N., Giallorenzo, S., Lafuente, A. L., Mazzara, M., Montesi, F., Mustafin, R., & Safina, L. (2017). Microservices: Yesterday, today, and tomorrow. In M. Mazzara & B. Meyer (Eds.), Present and ulterior software engineering (pp. 195–216). Springer. https://doi.org/10.1007/978-3-319-67425- 4_12
7. Erl, T. (2005). Service-oriented architecture: Concepts, technology, and design. Prentice Hall.
8. Fielding, R. T. (2000). Architectural styles and the design of network-based software architectures [Doctoral dissertation, University of California, Irvine]. https://www.ics.uci.edu/~fielding/pubs/dissertation/top.htm
9. Fowler, M. (2002). Patterns of enterprise application architecture. Addison-Wesley Professional.
10. Hasselbring, W., & Steinacker, G. (2017). Microservice architectures for scalability, agility and reliability in e-commerce. In 2017 IEEE International Conference on Software Architecture Workshops (ICSAW) (pp. 243–246). IEEE. https://doi.org/10.1109/ICSAW.2017.11
11. Hohpe, G., & Woolf, B. (2003). Enterprise integration patterns: Designing, building, and deploying messaging solutions. Addison-Wesley Professional.
12. Knoche, H., & Hasselbring, W. (2018). Using microservices for legacy software modernization. IEEE Software, 35(3), 44–49. https://doi.org/10.1109/MS.2018.2141035
13. Newman, S. (2015). Building microservices: Designing fine-grained systems. O'Reilly Media.
14. Pahl, C., & Jamshidi, P. (2016). Microservices: A systematic mapping study. In Proceedings of the 6th International Conference on Cloud Computing and Services Science (CLOSER 2016) (Vol. 1, pp. 137–146). SCITEPRESS. https://doi.org/10.5220/0005785501370146
15. Pautasso, C., Zimmermann, O., Amundsen, M., Lewis, J., & Josuttis, N. (2017). Microservices in practice, part 1: Reality check and service design. IEEE Software, 34(1), 91–98. https://doi.org/10.1109/MS.2017.24