If you don’t mind, I’d like to ask a few questions. I think you are the main developer for this feature (if I’m not mistaken).
Is it really that easy to run a pool? Setup the config file, and launch the node?
What happens if the stratum server goes offline for a few minutes? Impact on connected clients… and how do they re-connect (manually or automatically?)
Assuming there is a database: What database and what data is stored in the database? And what credentials are needed to log into the database? (this would be helpful for making a dashboard or front end UI)
as of running our software it is comparable with running a full node. Actually, coordination server is build-in full node and enabled by config. So, yes, setup and launch. It covers maintenance of rewards etc, so all is in, but still running a pool needs a thought about security and monitoring. We provided business logic. That said, it is our first iteration over pool system. Next step, for us, is to separate it.
Currently we re-use the database available in full node. Full node runs as a erlang daemon, so you can attach to the console and query database as you wish. It is not suitable for dashboards etc. Erlang setup assumes it is in safe zone. For dashboards, we intended to extend HTTP endpoints that run on external interface. Later on when stratum is separate, it will be easy to migrate HTTP API as well.