International Journal of Innovative Research in Computer and Communication Engineering

ISSN Approved Journal | Impact factor: 8.771 | ESTD: 2013 | Follows UGC CARE Journal Norms and Guidelines

| Monthly, Peer-Reviewed, Refereed, Scholarly, Multidisciplinary and Open Access Journal | High Impact Factor 8.771 (Calculated by Google Scholar and Semantic Scholar | AI-Powered Research Tool | Indexing in all Major Database & Metadata, Citation Generator | Digital Object Identifier (DOI) |


TITLE A Proposed Framework for Handling Cross-Cutting Concerns in Microservices Architecture
ABSTRACT Microservices architecture decomposes large software systems into independently deployable services, improving scalability, fault isolation, and team autonomy. However, this decomposition scatters non-functional, system-wide behaviours — commonly termed cross-cutting concerns (CCCs), such as authentication, logging, tracing, rate limiting, circuit breaking, and data validation — across dozens or hundreds of service boundaries. Existing strategies (library embedding, sidecar/service-mesh interception, and API-gateway centralisation) each address the problem partially but introduce trade-offs in latency, coupling, operational complexity, or update agility. This paper proposes a hybrid framework, the Layered Cross-Cutting Concern Framework (LCCF), which separates CCCs into three enforcement tiers — edge, mesh, and in-process aspect contracts — governed by a central declarative policy registry and propagated through a lightweight control plane. We implement a prototype of LCCF and evaluate it against three baseline approaches using a simulated e-commerce microservices testbed of up to 80 services. Results show that LCCF reduces average per-request latency overhead by 34–46% relative to sidecar-only designs, improves sustained throughput at scale by up to 28%, and cuts the developer effort required to roll out a new concern by more than 70% compared with library-embedded approaches. We analyse these results and discuss the architectural trade-offs, limitations, and directions for future work, including policy-conflict resolution and multi-cluster propagation.
AUTHOR DR. KAMLENDU KUMAR PANDEY Associate Professor, Dept. of ICT, Veer Narmad South Gujarat University, Surat, India
VOLUME 188
DOI DOI: 10.15680/IJIRCCE.2026.1409019
PDF pdf/19_A Proposed Framework for Handling Cross-Cutting Concerns in Microservices Architecture.pdf
KEYWORDS
References [1] Kiczales, G., Lamping, J., Mendhekar, A., Maeda, C., Lopes, C., Loingtier, J. M., & Irwin, J. (1997). Aspect-oriented programming. In Proceedings of the European Conference on Object-Oriented Programming (ECOOP), Springer LNCS 1241, 220–242.
[2] Lewis, J., & Fowler, M. (2014). Microservices: a definition of this new architectural term. martinfowler.com.
[3] Newman, S. (2021). Building Microservices: Designing Fine-Grained Systems (2nd ed.). O'Reilly Media.
[4] Richardson, C. (2018). Microservices Patterns: With Examples in Java. Manning Publications.
[5] Dragoni, N., Giallorenzo, S., Lafuente, A. L., Mazzara, M., Montesi, F., Mustafin, R., & Safina, L. (2017). Microservices: Yesterday, today, and tomorrow. In Present and Ulterior Software Engineering, Springer, 195–216.
[6] Sill, A. (2016). The design and architecture of microservices. IEEE Cloud Computing, 3(5), 76–80.
[7] Balalaie, A., Heydarnoori, A., & Jamshidi, P. (2016). Microservices architecture enables DevOps: Migration to a cloud-native architecture. IEEE Software, 33(3), 42–52.
[8] Taibi, D., Lenarduzzi, V., & Pahl, C. (2017). Processes, motivations, and issues for migrating to microservices architectures: An empirical investigation. IEEE Cloud Computing, 4(5), 22–32.
[9] Di Francesco, P., Malavolta, I., & Lago, P. (2017). Research on architecting microservices: Trends, focus, and potential for industrial adoption. In IEEE International Conference on Software Architecture (ICSA), 21–30.
[10] Soldani, J., Tamburri, D. A., & Van Den Heuvel, W. J. (2018). The pains and gains of microservices: A systematic grey literature review. Journal of Systems and Software, 146, 215–232.
[11] Vural, H., Koyuncu, M., & Guney, S. (2017). A systematic literature review on microservices. In International Conference on Computational Science and Its Applications (ICCSA), Springer LNCS 10409, 203–217.
[12] Li, S., Zhang, H., Jia, Z., Zhong, C., Zhang, C., Shan, Z., Shen, J., & Babar, M. A. (2021). Understanding and addressing quality attributes of microservices architecture: A systematic literature review. Information and Software Technology, 131, 106449.
[13] Villamizar, M., Garces, O., Castro, H., Verano, M., Salamanca, L., Casallas, R., & Gil, S. (2016). Evaluating the monolithic and the microservice architecture pattern to deploy web applications in the cloud. In Computing Colombian Conference (CCC), 583–590.
[14] Zimmermann, O. (2017). Microservices tenets. Computer Science - Research and Development, 32(3-4), 301–310.
[15] Larrucea, X., Santamaria, I., Colomo-Palacios, R., & Ebert, C. (2018). Microservices. IEEE Software, 35(3), 96–100.


Copyright © IJIRCCE 2020.All right reserved