1. Towards a Scalable Architecture of SME application :Microservice Integration Approach
Presented by Munezero Immaculee Joselyne
PhD in Software Engineering
College of Computing and Information System
Makerere University

2. Outline Clarification of keyword Motivation of the study Related works
Our approach

3. Clarification of the keyword
SME application : Small and medium enterprises are playing a big role in the development of the country economy. In non developing country these firms are majority compared to big size enterprises. With the increasing adoption of new technology and devices, researchers have a big task to develop highly performing scalable applications that facilitate the usage of innovation within enterprises.
Due to infrastructure resource constraints these applications lack applicability and efficiency

4. Scalability: Scalability is important for the system to parallel
speed up operations without reducing the performance

5. Microservice Architecture: is an approach for developing single applications as suites of small services, each running in its own process and communicating with lightweight mechanisms.
These services are built around business capabilities and independently deployed by fully automated deployment machinery.

6. Monolithic vs Microservice architecture style

7. Motivation of the study
Performance and upgradability are critical quality attributes that every application user would lookout in which most of application developers emphasize on its optimization.
Most SMEs run monolithic applications. The problem with a monolithic architecture, though, is that all change cycles usually end up being tied to one another. As enterprises continue to grow, functionally and technically, has a significant impact on the performance of entire system.

8. Motivation
Microservice architecture have been adopted and widely used for designing more scalable applications, which it is the need of SME application also.
Most of the practices used in micro-services architecture come from developers who have created software applications for large enterprise organizations
However SMEs should benefit the usage of micro-service despite their limitations, by proper understanding SME characteristics and exposing optimum micro-service patterns to use

9. Related works
Different approaches have been proposed to integrate legacy systems of big enterprise and small enterprise to SOA.
Our approach is targeting of integrating SME application to microservice for scaling more. The common method used is migration. Different patterns
have been proposed for that migration, though, other integration methods like; replacement, wrapping and re-engineering can be embraced for efficient use of micro-service architectures.

10. Methods for integration
Strategy
Description
Replacement
consists of rewriting the existing system applications or replacing it entirely with an off the shelf product.
Wrapping
Wrapping consists of providing a new service interface to a legacy components by making it easily accessible by other software components
Redevelopment
Redevelopment or re-engineering consists of the analysis and adjustment of an application in order to represent it in a new form that facilitate the communication with services
Migration
Migration consists of moving the entire legacy system and its core framework to the new environment gradually

11. Our approach
In order to integrate microservice architecture to SME application for the purpose of increasing performance and scalability of the system, we propose the following approach.
This approach in general is concerned of designing architecture pattern, that will be achieved by performing different works .
to achieve the result expected, we propose a iterative approach composed of 4 stages described below where the test have to be made at every stage to ensure the relevancy of the proposed architecture.

12. Stage 1:Acquiring SME application details
In this stage, the emphasis is to know how monolithic applications are designed, what the actual performance and determine the path in the system that should be exposed to integration.
Data on how the system is designed in order to understanding the basic working principle and structure of the systems will be collected in the process of reverse engineering. The critical features will be documented in terms of mandatory functional requirements, design constraints and quality attributes..

13. Stage 2: Determine microservice integration pattern
Microservice integration pattern such as API gateway, service discovery, load balance, resource manager, container, etc will be exposed during this stage in the process of architecture risk analysis, to analyzed these patterns against functional requirement; design constraint and quality at-
tribute requirements of SME application.
The process of architecture risk analysis will prioritize the calculation of
performance on each pattern exposed or modiffied.
During this stage all pattern will be studied and determine how
pattern can be combined with others . Interpretation of the result by choosing the most appropriate pattern to use on integration

14. Stage 3 Generate integration architecture model
The architectural model will be designed according to the result of implementation of pattern in the software architecture simulator. this process is done by Replicating SME application specification obtained in stage 1, that have the same performance metrics as in live environment, then add micro-service patterns to the system simulated obtained in stage 2 , and measure the performance.
following by studying how the system can be modified without interruption of the performance. furthermore propose a better scalable design of integration.

15. Stage 4: Test and evaluate the performance of the
designed integrated architecture
Proposed architecture will be implemented and tested at SME pilot , and the result will be monitored over a period of time to study quality attributes such performance and scalability capacity of the architecture.
Automated test will be implemented to check performance parameter such as response time, loading time and throughput.
To test scalability capacity, a set of micro-services will be introduced
by using different containers(distributed environment). The new micro-service will be observed and monitored to determine the infrastructure and system breaking point of the architecture.

16. Output of WP2

17. RESEARCH STRATEGY
our research Strategy that will implement the approach described in 4 stages, is concerned of applying different research methodology in software engineering.
lab experiment and live operation observation. software architecture simulator like Palladio.
The choice of Palladio is that it is a model driven simulation software that evaluate and estimate required resource of a system architecture before it is implemented.
The construction phase itself starts by estimating required resources, evaluation of scalability by number of supported concurrent users, and by predicting the performance.

18. Thank you