Search: "business"

Considering the impact of business logic

From Business to IT

Key concepts == This microlearning centers around considering the impact of business logic * By business logic, we mean: Rules that determine what should happen to a message The most interesting point when talking about business logic is: * Where to draw the line?

Considering the impact of business logic == In this microlearning, we will learn what you should consider determining the impact of business logic within your integration solution.

Filling your eMagiz model with a lot of business logic opens you up for a continuous discussion about data and interpretations of business rules.

With this exercise, we will provide you with a business case to reflect on which of these patterns are best suited for the case.

Therefore, decide which pattern suits best based on the technical checks and balances. ===2.1 Business Case=== **Read and understand the following business case** ABC Logistiek B.V. is a medium-sized logistics provider offering land transport services in The Netherlands.

* To propose a better solution for this business case, what other questions should be explored and answered?

Now it becomes time to include the business (users) with your tests. This is what we call a user acceptance test.

* By user acceptance testing we mean: A test that is designed to let the users (business) test the functionality based on various scenarios.

With this test, the users (business) will test what you (and your team) have built to ensure that it works as expected.

Many transformations take place through discussions with business owners or by reviewing business documentation.

By the end, you will understand the pros and cons of each pattern and how to make an informed decision based on both business and technical factors. Should you have any questions, please get in touch with [[academy@emagiz.com>>mailto:academy@emagiz.com]]. == 1.

The answer is a series of checks and balances that look both at the business and technical aspects. === 3.1 Checks and balances === At first, look at the business side of your integration scenario before delving into the technical disqualifiers. You should ask the first question: **Does the business process require a real-time response (for both success and error messages)?

So in a sense, the failure of one integration blocks the business process as it prevents API clients from retrieving the complete invoice in this example. Being aware of these dependencies can significantly improve the choices you and the business make in terms of risk mitigation before developing your solutions via the eMagiz platform. == 4.

As a result, this means that when one synchronous process is busy, it can even hold up other synchronous processes.

So in a sense, the webshop has taken the responsibility of handling success and failure responses. === 3.2 Asynchronous vs Synchronous === The decision to handle an integration process in a specific manner depends on various relevant business and technical checks and balances that should be answered before choosing which integration pattern to choose and then subsequently which alternative method within an integration pattern to choose.

Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).

Before starting the Create phase, the test scenarios should be agreed upon with the business owners. This is one of the Definition of Done items from the Discovery (Capture & Design) phase we advise.

Should this connection be business-critical, you can use this failover functionality to create a passive failover situation that will take over when the active connection breaks down (regardless of the reason).