0010-eureka
Start Date | Oct 21, 2024 |
End Date | TBD |
Contributors | @Craig McNally @VBar |
Status | PRELIMINARY REVIEW |
Summary
The Folio Eureka Platform (henceforth referred to as Eureka for brevity) represents the next generation of Folio’s architecture which allows the project to operate at enterprise scale and expand its solution space. It seeks to replace custom-developed core components found in the original Folio architecture, with feature-rich, best-of-class, specialized open-source components. The need for this has become critical as Folio has become widely adopted, and particularly in ever increasing numbers in complex configurations such as consortia and national libraries.
Motivation
It became increasingly clear that requirements imposed by some high-profile libraries adopting Folio were going to be very difficult, if not impossible to meet on the current platform.
Scope
This RFC is intended to cover all aspects of Eureka at a high level. This includes:
Authentication
Authorization
Sidecars
API Gateway/Routing
Dynamic Scheduling/Timers
Role Based Access Controls
Application Formalization
Covered in more detail here: 0005-application-formalization
Application Composition is Out of Scope
Detailed Explanation/Design
Risks and Drawbacks
Rationale and Alternatives
Timing
We would like to get the Eureka platform formally approved and adopted by the Folio community for the Sunflower release.
Unresolved Questions
Keywords