How to build an event-driven capability
Hyppönen, Turo (2020)
2020
Johtamisen ja tietotekniikan DI-tutkinto-ohjelma, Pori - Degree Programme in Management and Information Technology, MSc (Tech), Pori
Tekniikan ja luonnontieteiden tiedekunta - Faculty of Engineering and Natural Sciences
This publication is copyrighted. You may download, display and print it for Your own personal use. Commercial use is prohibited.
Hyväksymispäivämäärä
2020-05-25
Julkaisun pysyvä osoite on
https://urn.fi/URN:NBN:fi:tuni-202005075026
https://urn.fi/URN:NBN:fi:tuni-202005075026
Tiivistelmä
During the discussions with different internal stakeholders and from market review, Telecommunications operator’s architecture team of IT department has concluded that there is a need to focus on old paradigm. Some of the operator’s systems are coupled with each other that causes issues during system development and during normal operations. If a system is malfunctioning or has a planned service break, it might have impacts to other systems and cause loss of sales since customers cannot be served. There was a wish to view the issue through event-driven architecture.
An event is a significant change of state and the event can be viewed from system design point of view or computer science point of view among others. In this thesis, the events are limited to system and business events. A system event occurs inside of the software component, for instance, an internal log event. A business event reflects to real life events such as customer’s order to eCommerce platform where the order is the event of the interest.
Event-driven architecture is a way to create systems or software that are highly decoupled thus enabling parallel development cycles. In addition, it enables a system where malfunctioning piece of system does not affect to other systems. Event-driven architecture enables also faster data transfer and a way to create new information by combining events.
The goals of this thesis were to find out what is event-driven architecture, how to design and implement event-driven architecture through business cases and what kind of obstacles and possibilities a company may have. Literature review was used to define the meaning of the event-driven architecture. For design and implementing the event-driven architecture, both literature review and capability-based framework were used. The framework helps to create a roadmap for event-driven architecture for the company. The obstacles and possibilities are charted via expert interviews on the company’s personnel. The results of the interviews are applied to the capability-based and a tailored roadmap for the company was created.
As summary, the result of the thesis is a roadmap for event-driven architecture. The roadmap was achieved by using expert interviews and capability-based framework that IT organization can use while engaging in development activities.
An event is a significant change of state and the event can be viewed from system design point of view or computer science point of view among others. In this thesis, the events are limited to system and business events. A system event occurs inside of the software component, for instance, an internal log event. A business event reflects to real life events such as customer’s order to eCommerce platform where the order is the event of the interest.
Event-driven architecture is a way to create systems or software that are highly decoupled thus enabling parallel development cycles. In addition, it enables a system where malfunctioning piece of system does not affect to other systems. Event-driven architecture enables also faster data transfer and a way to create new information by combining events.
The goals of this thesis were to find out what is event-driven architecture, how to design and implement event-driven architecture through business cases and what kind of obstacles and possibilities a company may have. Literature review was used to define the meaning of the event-driven architecture. For design and implementing the event-driven architecture, both literature review and capability-based framework were used. The framework helps to create a roadmap for event-driven architecture for the company. The obstacles and possibilities are charted via expert interviews on the company’s personnel. The results of the interviews are applied to the capability-based and a tailored roadmap for the company was created.
As summary, the result of the thesis is a roadmap for event-driven architecture. The roadmap was achieved by using expert interviews and capability-based framework that IT organization can use while engaging in development activities.