Student learning management system includes student recruitment

0

Executive Summary.........................................................................................................................1 Table of Contents.............................................................................................................................2 Introduction....................................................................................................................................3 Industrial Success Stories.................................................................................................................4 Spotify.............................................................................................................................................4 Walmart..........................................................................................................................................4 PayPal..........................................................................................................................................5 Service Modelling:...........................................................................................................................6 Service integration..........................................................................................................................8 Challenges to Splitting Monolithic System.......................................................................................9 Issues in Transition to Micro-Service Architecture..........................................................................10 Ethical........................................................................................................................................10 Legal...........................................................................................................................................10 Security......................................................................................................................................10 Recommendations.........................................................................................................................10 Conclusion.....................................................................................................................................11 References.....................................................................................................................................11

Above figure shows, the monolithic system compressed all component together which is difficult in terms of flexibility on the other hand micro-services separate the all component which is more flexible to handle. For example, student learning management system includes student recruitment, student enrolment, tuition fee payment, learning content management, academic record management, graduation and the issuance of qualifications and certificates. There exists initial challenge to store each component separately. I will discuss it in preceding paragraph.

Firstly, dependency between services. It will hard to identify dependency even if an individual builds one service then one has to be careful about other dependency. Testing will be the second major issue specially when all services integrated to the system. When final system will be ready then end to end testing will face major barrier. As student management and learning system have over hundreds of services that’s why remote debugging will be concerning issue. System security also another concern because it is not possible to keep one version of software. As world is changing over the time so

Much of this popularity is due to their potential to allow enterprises to become more agile, move more quickly, and innovate at a speed that allows them to keep up with the changing needs of their customers. Despite this popularity, implementation of a micro-services architecture that is scalable, reliable, and, of course, secure is notoriously difficult (Alshuqayran, Ali & Evans, 2016).

Despite these challenges, many leading enterprises today have found a way to capture the full benefits of micro-services and transform their business using them. These real-world examples of micro-services demonstrate how a micro-services strategy is incomplete without a strong, managed API strategy.

12

PayPal uses Node.js to run VMs to spread the workload as well as provide consistent service. Consequently, the machine can accommodate more than one billion visits per day without cracking.

Event-driven data model is a loosely couple and highly scalable distributed system where always maintain data consistency. Figure given below describes, how event-driven data model performs between numerous services. The below given figure will also show the difference between tight coupling and loose coupling. So, loose coupling provides better performance (Villamizar et. al, 2015).

Event-driven data model

Despite these challenges, many leading enterprises today have found a way to capture the full benefits of micro-services and transform their business using them. These real-world examples of micro-services demonstrate how a micro-services strategy is incomplete without a strong, managed API strategy (Cerny, Donahoo & Trnka, 2018).

One of the imperative aspects in micro-service is integration. If integration is working flawlessly then micro-service will retain its autonomy and work independently otherwise the whole system will suffer numerous drawbacks. So, now question is which integration technology to best for usage in student learning and management system. There are many characteristics which can be used to identify the best possible service integration, but it is also important to look at what are the available services for integration. There exist synchronous and asynchronous as two communication channels for service integration.

Despite these challenges, many leading enterprises today have found a way to capture the full benefits of micro-services and transform their business using them. Now I will discuss some of the challenges in splitting backend systems.

 Identify a moving part from monolithic system. This is the first task for programmer to identify the component which services going to where. When they will decouple the services then they will identify scalability of the component. As, many components are interacting, failure points will also increase. So, programmer has to make sure that he split the right component while checking flexibility and scalability.

 Monolithic traditional system logging will be abortive because micro-services are stateless services. So, developer will have to be careful about too many log files.

Issues in Transition to Micro-Service Architecture
There are numerous obligations to handle from students, teaching staffs and other employee’s data in transition to micro-services. As, each component provide service individually and independently therefore developer must be careful about ethical, legal and security issue. There are several ethical, legal and security issues along the transition period in micro-service which are given below:

Security

There exist several questions around the corner regarding security. For these issues, the company should take measures even before transition stage. Following questions will focus the security concerns in transitions to micro-service architecture;

12

References
 Alshuqayran, N., Ali, N., & Evans, R. (2016, November). A systematic mapping study in microservice architecture. In 2016 IEEE 9th International Conference on Service- Oriented Computing and Applications (SOCA) (pp. 44-51). IEEE.

 Nadareishvili, I., Mitra, R., McLarty, M., & Amundsen, M. (2016). Microservice architecture: aligning principles, practices, and culture. " O'Reilly Media, Inc.".

	12

 Le, V. D., Neff, M. M., Stewart, R. V., Kelley, R., Fritzinger, E., Dascalu, S. M., & Harris, F. C. (2015, July). Microservice-based architecture for the NRDC. In 2015 IEEE 13th International Conference on Industrial Informatics (INDIN) (pp. 1659-1664). IEEE.

 Sun, L., Li, Y., & Memon, R. A. (2017). An open IoT framework based on microservices architecture. China Communications, 14(2), 154-162.