B) A BL becomes a Calculation Engine if it performs complex calculations, (e.g. an invoice calculation engine or an insurance simulator). Engines are usually subject to versions.
A) Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
A) Logic to Synchronize data in CS's with an external system. Isolating this logic makes the CS completely system agnostic and it's easier to decouple or replace the external system.
I'm feeling lucky, so I'm going to go with option A. Synchronizing data with an external system? Piece of cake! Let's keep that business logic nice and isolated.
I'm going to have to go with D on this one. Reusable core services with public entities, actions, and blocks sounds like the way to go. Keeps things nice and modular.
I'm going with E. The API module should be used for isolated business logic or core widgets to manage complexity, composition, or have its own lifecycle.
I think C is the correct answer. The API module is a technical wrapper that exposes an API to external consumers, keeping the core services system-agnostic and supporting multiple versions of the API.
Rima
1 months agoVernell
18 days agoFranchesca
19 days agoShaun
19 days agoCatalina
28 days agoOra
1 months agoMatilda
2 months agoMyong
2 months agoKimberely
2 months agoLigia
2 months agoStefany
Reuben
4 days agoKallie
5 days agoAshley
16 days agoDyan
21 days agoBong
30 days agoFlorinda
1 months agoStaci
2 months agoLouann
2 months agoKiera
2 months agoHobert
2 months agoLoren
1 months agoMariann
1 months agoGayla
1 months agoSarah
2 months agoLaurena
2 months ago