Last Comment Bug 1313742 - Implement a "service" layer to manipulate table objects
: Implement a "service" layer to manipulate table objects
Status: NEW
Product: Release Engineering
Classification: Other
Component: Balrog: Backend (show other bugs)
: unspecified
: Unspecified Unspecified
P3 normal (vote)
: ---
Assigned To: Nobody; OK to take it and work on it
: Ben Hearsum (:bhearsum)
Depends on:
Blocks: 884662
  Show dependency treegraph
Reported: 2016-10-28 11:39 PDT by Johan Lorenzo [:jlorenzo]
Modified: 2017-01-23 11:19 PST (History)
1 user (show)
See Also:
Crash Signature:
QA Whiteboard:
Iteration: ---
Points: ---


Description User image Johan Lorenzo [:jlorenzo] 2016-10-28 11:39:43 PDT
Discussed with :bhearsum while implementing [1]. In a few words, the service layer is represent the whole business logic of a process, by dividing the business process into smaller ones. The smallest ones are then the table objects.
The idea of the back-end architecture would be the following: The web layer takes data out of the HTTP request and passes them to the Service. The service is then in charge of delegating to all the tables, and making sure data is consistent across tables

Here are some call diagram examples:
* Add a new scheduled change [2]
* Update a condition [3]
* Update a scheduled target value [4]

Comment 1 User image Johan Lorenzo [:jlorenzo] 2016-10-28 11:43:20 PDT
:bhearsum pointed out this may solve bugs like bug 884662.

Note You need to log in before you can comment on or make changes to this bug.