Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

The current implementation for of the persistence service Persistence Service SPI is provided in 'cps-ri' which is specific to relational DB. If we want to use another type of DB later, the Persistence and Repository layer needs to be re-written. To Therefore, to achieve the original intent (use a different DB type later), it is important to keep the business logic in the 'Service' layer and have only database-specific logic in the 'Persistence' layer. 

...

In the existing implementation, the 'Admin Service' and 'Module Service' have the implementation to delete Data Node which is managed by 'Data Service'. This behaviour is not expected as 'Data Service' is responsible for deleting DataNode and should control how it can be done. The other services should utilize this functionality from DataService wherever required. 

As a part of In this proposal, the business logic 

Delete Anchor

...

  the business logic of the 'Delete SchemaSet' and 'Delete Anchor' functionality will be moved to Service Layer and domain-specific services will be used to do any operation of those domain objects. 

Delete Anchor

draw.io Diagram
bordertrue
diagramNameExisting Delete Anchor Sequence Diagram
simpleViewerfalse
width400
linksauto
tbstyletop
lboxtrue
diagramWidth629
revision2

draw.io Diagram
bordertrue
diagramNameProposed Delete Anchor Sequence Diagram
simpleViewerfalse
width400
linksauto
tbstyletop
lboxtrue
diagramWidth629
revision2

Delete Schema Set

draw.io Diagram
bordertrue
diagramNameExisting Delete Schema Set
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth688
revision2

draw.io Diagram
bordertrue
diagramNameProposed Delete Schema Set
simpleViewerfalse
width
linksauto
tbstyletop
lboxtrue
diagramWidth688
revision2