Gabriel Roldan

https://docs.geoserver.org/stable/en/user/extensions/netcdf-out/index.html

https://docs.geoserver.org/stable/en/user/extensions/querylayer/index.html

https://docs.geoserver.org/stable/en/user/extensions/mongodb/index.html

https://docs.geoserver.org/stable/en/user/extensions/sldservice/index.html

Implement GeoServer's [CSW Extension](https://docs.geoserver.org/stable/en/user/community/csw-iso/index.html) as a microservice Q: does it imply including the [Metadata extension](https://docs.geoserver.org/stable/en/user/community/metadata/index.html) (I'd say yes?)

There's no lock provider for the catalog backend. The client shall issue a request to the service, which should lock the resource on behalf of the caller service. Moreover, given...

Implement GeoServer's [OGC API](https://docs.geoserver.org/stable/en/user/community/ogc-api/index.html) extension as a microservice

Basically just what's described here: https://stackoverflow.com/questions/31901054/spring-cloud-how-to-get-benefits-of-retry-load-balancing-and-circuit-breaker-f We're not using `ribbon` as it's in maintenance mode only, switched to new spring cloud's `LoadBalancer`. So see this too https://dzone.com/articles/using-new-spring-cloud-load-balancer-in-microservi

Bring authentication and authorization to the front service (gateway)

1

Currently, only the default security authN/authZ is available, and worse, all services got to perform auth on their own. With each service having its own keystore, you can only guess...