Page Comparison

...

Overrides/Supersedes 

When applicable, provide links to all DRs that this DR overrides or supersedes 

RFC 

Provide links to all relevant RFC's

Stakeholders

@mention individual(s) who has vested interest in the DR. This helps us to identify who needs to be aware of the decision

Contributors

List individual(s) sposnoring/advocating for the decisionThis decision was migrated from the Tech Leads Decision Log as part of a consolidation process.  The original decision record can be found here.

RFC 

N/A

Stakeholders

• Edge API developers

Contributors

Craig McNally Mikhail Fokanov Viachaslau Khandramai (Deactivated) 

Approvers

This decision was made by the Tech Leads group prior to the adoption of current decision making processes within the FOLIO project.

Background/Context Explain the need that triggered the need for making a decision

As development teams begin to adopt the spring way for module development, it's become apparent that there's a desire for some of these teams to work with the same tech stack when developing edge APIs.  

Two examples:

• edge-dematic
• edge-search-srs

Assumptions

N/A

Constraints

...

• Pros
  • N/A
• Cons
  • N/A

Other Related Resources

JIRAs

• Image AddedUXPROD-2973 - Create Spring-way equivalent of edge-common CLOSED
• Image AddedEDGCMNSPR-1 - Create Project Skeleton CLOSED
• Image AddedEDGCMNSPR-2 - Port edge-common to spring-way CLOSED
• Image AddedEDGAPIUTL-1 - Initial development of edge-api-utils CLOSED

Notes

• edge-dematic can be used as a reference.  Much of this work can be seeded from that repository and generalized.
• The Concorde team has agreed to take on this work as it would allow them to use it for development of edge-search-srs.