https://alguidelines.dev/bcpatterns/Recent content in BC Patterns on AL GuidelinesHugo -- gohugo.ioen-ushttps://alguidelines.dev/bcpatterns/event-bridge-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcpatterns/event-bridge-pattern/<Created by waldo & Arend-Jan Kauffmann, Described by waldo> Abstract In the world of interfaces, it is important to preserve (certain) events over multiple implementation of the interface. Context An app can have interfaces. It makes it possible for other apps to extend/change the implementations of a certain part of the business logic. Like in this example, we have an interface, to implement different ways for getting weights from scales:https://alguidelines.dev/bcpatterns/facade-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcpatterns/facade-pattern/Created by Erich Gamma, Richard Helm, Ralph Johnson, John Vlissides (Gang of Four), Described by Jesper Schulz-Wedde (Microsoft) Abstract The intent of this pattern is to provide a unified API to a single or a collection of potentially complex subsystems. If you apply this pattern as a general pattern, you will ensure improved: Decoupling Encapsulation Readability Testability Maintainability Context Whenever you want to write an isolated piece of business logic, from now on referred to as subsystem, this pattern should be applicable.https://alguidelines.dev/bcpatterns/generic-method-pattern/Mon, 01 Jan 0001 00:00:00 +0000https://alguidelines.dev/bcpatterns/generic-method-pattern/Created by Gary Winter (Cloud Ready Software), Described by waldo (iFacto Business Solutions | Dynex) Abstract The goal of this pattern is to facilitate a lot of things in one single awesome way of writing code. If you apply this pattern as a general pattern, you’ll implement: Extensibility Decoupling Readability Testability Encapsulation Context Whenever you have to write an isolated piece of business logic, this pattern should be applicable.