Table of contents
...
...
Introduction
There is community momentum toward the Eureka environment, and it was extensively discussed in 2024. There will also be significant benefit from well coordinated migration to the new platform and quick consolidation on just one platform. EBSCO plans to shift their support from the Okapi-based FOLIO architecture to the Eureka-based FOLIO architecture in the Sunflower release. The FOLIO chairs recommend coordinating community resources to follow in EBSCO’s steps and transition to Eureka in Sunflower.
...
Continued knowledge transfer to community dev ops teams
Onboard additional hosts into early adopter program
Appendices
Eureka adopter support
Existing support
End-user early adopter program has begun (private slack channel #eureka-early-adopters)
Some documentation exists on the Wiki: Eureka - How to ...
Docker-based minimal eureka platform: https://github.com/folio-org/eureka-platform-bootstrap
CLI for local deployment: https://github.com/folio-org/eureka-setup
Planned support
Hosting early adopter program will begin in January 2025 with GBV and potentially others
Gaps in support
Additional operational and development support will be needed
Implications of Eureka adoption
Changes
Move from module based platform to application-based platform
Change in maintenance through deprecation of homegrown modules:https://folio-org.atlassian.net/wiki/spaces/TC/pages/518946885/0010-eureka#Deprecations
Benefits
Challenges
Uncertainty of non-EBSCO hosting providers and self-hosters ability to adopt for Sunflower
Incomplete documentation
RFC process not completed
What if the community does not transition to Eureka in Sunflower?
If the community were unable to shift to Eureka in Sunflower and must continue supporting the Okapi architecture these high level requirements will need to be met, we believe these needs exceed the community’s capacity:
...