Scaling PiGO API

In a lot of projects, I've seen PiGO API as a relatively standalone microservice for let's say one or two data sets. On the other side, with my work with the Midlage Service of Canada, we use PiGO API to deploy thousands of layers and millions of hits per day. So there is something to be said around scaling PiGO API. But from a scalability perspective, it allows you to scale things accordingly according to your requirements. We do have this element of facades in PiGO API which I think will be valuable as we move forward regarding the evolution of moving on to these OGC APIs in the future.