Changes for page Communication between models
Last modified by Erik Bakker on 2024/09/05 14:00
From version 21.1
edited by Carlijn Kokkeler
on 2024/09/03 11:49
on 2024/09/03 11:49
Change comment:
There is no comment for this version
To version 22.1
edited by Carlijn Kokkeler
on 2024/09/03 12:30
on 2024/09/03 12:30
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,5 @@ 1 1 {{container}}{{container layoutStyle="columns"}}((( 2 - Whenyourintegration landscapegrowsthroughtime,youmightdecide tosplitfunctionalbusinessprocessesintomultiple eMagizmodels.In those cases,thequestionofconnectingthesemodelseasily,stable,andsecurelycouldarise.Thismicrolearningwillfocus on that questionandprovideanswerbased on our visionand bestpractices whendealingwiththeplatform.2 +In this microlearning, we'll explore the best practices for communication between two eMagiz models. Effective communication is crucial, and it's important to prioritize security, loose coupling, maintainability, and clarity. We'll discuss why using queues for inter-model communication is generally discouraged and why alternatives like web services and Event Streaming are preferred. By focusing on these key considerations, you'll be better equipped to design robust and maintainable integration solutions within eMagiz. 3 3 4 4 Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. 5 5