[SERVER-80331] (SA) Introduce "Service" objects between ServiceContext and Client Created: 23/Aug/23  Updated: 26/Sep/23  Resolved: 07/Sep/23

Status: Closed
Project: Core Server
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Improvement Priority: Major - P3
Reporter: Billy Donahue Assignee: Billy Donahue
Resolution: Duplicate Votes: 0
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
Depends
is depended on by SERVER-77921 (SA) Support for different ServiceEnt... Closed
is depended on by SERVER-78976 (SA) Adapt command registry to suppor... Closed
Duplicate
duplicates SERVER-80355 introduce Service under ServiceContex... Closed
Sprint: Service Arch 2023-09-04, Service Arch 2023-09-18
Participants:

 Description   

ServiceContext will become something of a "process context".
It will own N "services".

A Service is an OO abstraction of a service entry point + its state. The "makeClient" function will have to migrate from ServiceContext into Service. A Client will have a reference to its Service of origin. In this way, a Client will have access to the Service's CommandRegistry and Service-Specific stats and metrics, or other service-specific state.

If we put a simple sketch of this infrastructure in place early, other tickets in the PM-635 project should have a framework under which to operate and can be more concretely specified acceptance criteria, etc.


Generated at Thu Feb 08 06:43:16 UTC 2024 using Jira 9.7.1#970001-sha1:2222b88b221c4928ef0de3161136cc90c8356a66.