Business logic for microservices architectures
Developers and business managers often run into problems trying to work together. Issues can arise from inadequate documentation of business rules. To explain this further let me share an example I always use.
A young developer gets a requirements document to build a sales order system. He immediately reads the requirements and builds the required tables and the front-end of the system and presents it to the marketing group for testing. The marketing group says it is great, but they need a few additional things before it will work for them. They list the following requirements:
- You cannot have a new customer without an order; otherwise, the customer is really a prospect.
- A new order must have at least one order line for a real product that the customer is ordering
- The new customer must either pay cash, credit card or have an approval from the Credit Department to allow an accounts receivable.
- The order cannot go to the warehouse for shipping without the previous rule's completion in a positive manner
You can see that the simple sales order system is now extremely complex. There is probably no way the developer will ever achieve the result that business needs within an acceptable timeframe, unless the development group has a rules or logic layer. Let's take a look at different ways you can instate a logic layer.
Azure Logic Apps
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here
or
login
FREE Membership Required to View Full Content:
Joining MSDynamicsWorld.com gives you free, unlimited access to news, analysis, white papers, case studies, product brochures, and more. You can also receive periodic email newsletters with the latest relevant articles and content updates.
Learn more about us here
Microservices should be…
Microservices should be loosely coupled, meaning that each service operates independently and does not have direct dependencies on the internal implementation details of other services. This allows for independent development, deployment, and geometry dash lite.