Aspect-driven Context-aware Services

Abstract

Abstract-Nowadays enterprise software solutions must deal with ever-growing complexity and a multitude of business processes. The mainstream system design decomposes the system into small reusable services. While these services isolate certain system logic and address efficient elasticity towards growing user demands, there are multiple issues related to such a design, such as limitations to deal with restated information, information reuse or the ability to address cross-cutting concerns across multiple services. This paper highlights limitations of service-oriented architecture and proposes an alternative decomposition through aspect-driven service-oriented architecture. Such architecture involves adaptive, context-aware services preserving simple maintenance while addressing information reuse and crosscuts across services. The paper provides a formal description of the proposed architecture as well as a demonstration through a case study, showing approach properties and benefits.

On Code Analysis Opportunities and Challenges for Enterprise Systems and Microservices

“…If one manages to capture business rules in such a unified approach, it is possible to extract business rules and consider them for transformation or even the AOP process for UI fragment derivation. For instance, [80], [81] shows that it is easy to extract business rules from Drools and convert them to documentation or even enforce clientside validation already in the UI. This could be utilized for knowledge base exchange across smart interacting systems.…”

“…For instance, in enterprises we can use DSL to describe processes [106] or rules [79]. It can be business rules [80] or security rules. Modern frameworks also make it possible to define specific processes using DSL and utilize modeling tools on top of the DSL [107].…”

“…Code analysis enables documentation extraction; as mentioned earlier, it is fairly common to use the analysis to determine data scheme and endpoints, and proper transformation may turn it into UML models or other appropriate structures [80], [127]. DSL makes it suitable for analysts to focus on specific system domain, and since these languages are interpreted, such can be part of the GPL system logic.…”

“…We can centralize data schemes, constraints, and input validation. Moreover, if the business rules are captured in readable form, as suggested in [80], [81] one can easily combine and formally verify the consistency of business rules from the overall system.…”

Eficiency of REST and gRPC Realizing Communication Tasks in Microservice-Based Ecosystems

“…usually deemphasized when analysing communication in large-scale industrial IoT deployments. In a paper [22], the authors identified REST as one of the leading standards for communication between microservices, without examining its impact on the overall system performance. Interesting, from the point of view of the conducted research, is an article available on the blog of the developers of the gRPC framework.…”