geonetwork / geonetwork/geonetwork-microservices
Proposal / Archiving of the geonetwork-microservice repository
- Dominant language
- Java
- Stars
- 15
- Forks
- 21
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/geonetwork/geonetwork-microservices/ was created in 2000 in order to evaluate the possibility to move from GeoNetwork 4 monolith approach to a more microservice based architecture. The main module developed was a first OGC API Records implementation which has been deployed in some places.
Main reason for archival:
* (alternative available) https://github.com/geonetwork/geonetwork provide a more robust and complete implementation of OGC API Records
* (lack of community effort) https://github.com/geonetwork/geonetwork-microservices/ is not maintained
* (technical difficulties) https://github.com/geonetwork/geonetwork-microservices/ docker images build is now failing due to old version of Spring
At last meeting, we agreed to put that proposal on the table aiming to:
* archive this repository https://github.com/geonetwork/geonetwork-microservices/ (switch to readonly)
* replace it in GN4 docker compose for future version by the GN5 implementation https://github.com/geonetwork/docker-geonetwork/pull/149
Looking forward the community opinions on this.
Thanks
Contributor guide
No contributing guide indexed for this repository
Research direction
Review the repository’s maintenance and Docker build status, then read the proposed geonetwork/docker-geonetwork PR #149 and the GN4 Docker Compose configuration. Done means the community decision is recorded, this repository is switched to read-only archival status, and the GN4 configuration uses the proposed GN5 implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, docker-compose, java, spring
- Domain
- devops, release
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100