Presented by Munezero Immaculee Joselyne PhD in Software Engineering

Slides:



Advertisements
Similar presentations
Database Planning, Design, and Administration
Advertisements

Presentation by Prabhjot Singh
Lecture # 2 : Process Models
Enterprise Resource Planning
MIS 2000 Class 20 System Development Process Updated 2014.
1 Prescriptive Process Models. 2 Prescriptive Models Prescriptive process models advocate an orderly approach to software engineering Prescriptive process.
ITIL: Service Transition
Basic guidelines for the creation of a DW Create corporate sponsors and plan thoroughly Determine a scalable architectural framework for the DW Identify.
© 2006 IBM Corporation IBM Software Group Relevance of Service Orientated Architecture to an Academic Infrastructure Gareth Greenwood, e-learning Evangelist,
Database Planning, Design, and Administration Transparencies
1 Pertemuan 14 Perencanaan, Desain dan Administrasi Databases Matakuliah: >/ > Tahun: > Versi: >
Physical Database Monitoring and Tuning the Operational System.
Lecture Nine Database Planning, Design, and Administration
All content in this presentation is protected – © 2008 American Power Conversion Corporation Rael Haiboullin System Engineer Capacity Manager.
Chapter 9 Database Planning, Design, and Administration Sungchul Hong.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle © Pearson Education Limited 1995, 2005.
Overview of the Database Development Process
Chapter 6 System Engineering - Computer-based system - System engineering process - “Business process” engineering - Product engineering (Source: Pressman,
Developing an IS/IT Strategy
Engineering, Operations & Technology | Information TechnologyAPEX | 1 Copyright © 2009 Boeing. All rights reserved. Architecture Concept UG D- DOC UG D-
ITEC224 Database Programming
The Challenge of IT-Business Alignment
So What? Operations Management EMBA Summer TARGET You are, aspire to be, or need to communicate with an executive that does not have direct responsibility.
1 Minggu 9, Pertemuan 17 Database Planning, Design, and Administration Matakuliah: T0206-Sistem Basisdata Tahun: 2005 Versi: 1.0/0.0.
What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.
Methodology - Conceptual Database Design. 2 Design Methodology u Structured approach that uses procedures, techniques, tools, and documentation aids to.
Database Planning, Design, and Administration Transparencies
Database System Development Lifecycle 1.  Main components of the Infn System  What is Database System Development Life Cycle (DSDLC)  Phases of the.
Methodology - Conceptual Database Design
Systems Analysis and Design in a Changing World, Fourth Edition
Cmpe 589 Spring 2006 Lecture 2. Software Engineering Definition –A strategy for producing high quality software.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
SOFTWARE PROCESS IMPROVEMENT
ANALYSIS PHASE OF BUSINESS SYSTEM DEVELOPMENT METHODOLOGY.
Banaras Hindu University. A Course on Software Reuse by Design Patterns and Frameworks.
Chapter 9 Database Planning, Design, and Administration Transparencies © Pearson Education Limited 1995, 2005.
 System Requirement Specification and System Planning.
4.2 SOFTWARE DEVELOPMENT METHODOLOGGY PRESENTED BY : AZURA IBRAHIM SYARIFAH SYAZA BTE SEYD ZULKAFLY CS230(5A)
KRISHNACHANDER KALIYAPERUMAL PROJECT MANAGER
Process 4 Hours.
ITIL: Service Transition
Methodologies and Algorithms
Chapter 8 Environments, Alternatives, and Decisions.
Methodology Conceptual Databases Design
BIL 424 NETWORK ARCHITECTURE AND SERVICE PROVIDING.
Information Systems Development
IT Architecture Technical blueprint for evolving a corporate infrastructure resource that can be shared by many users and services processing systems hardware.
Fundamentals of Information Systems, Sixth Edition
Methodology Conceptual Database Design
Software Project Management
ICT PSP 2011, 5th call, Pilot Type B, Objective: 2.4 eLearning
Design and realization of Payload Operation and Application system of China’s Space Station Wang HongFei 首页.
Preface to the special issue on context-aware recommender systems
IEEE Std 1074: Standard for Software Lifecycle
System Development Life Cycle (SDLC)
Methodology – Physical Database Design for Relational Databases
Software Project Management
Model-Driven Analysis Frameworks for Embedded Systems
Software life cycle models
Object-Oriented Systems Development Life Cycle (CH-3)
Nada Al Dosary Edited By: Maysoon AlDuwais
Baisc Of Software Testing
DMAIC Roadmap DMAIC methodology is central to Six Sigma process improvement projects. Each phase provides a problem solving process where-by specific tools.
SAMANVITHA RAMAYANAM 18TH FEBRUARY 2010 CPE 691
Methodology Conceptual Databases Design
Presented By: Darlene Banta
Chapter 5 Architectural Design.
SDLC (Software Development Life Cycle)
Presentation transcript:

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

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

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

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

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.

Monolithic vs Microservice architecture style

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.

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

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.

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

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.

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..

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

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.

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.

Output of WP2

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.

Thank you