Service infrastructure (bunch of web + cli...)?

Question

System administration

I am a system administrator. I am familiar with web technologies, but I do not develop anything in this direction. One day a great idea came to my mind: to create a service for providing apps to (different) clients. They go to the site a couple of clicks and app them. I figured that at the system administrator level, I could automate everything - ansible. Right now I am creating tasks and playbooks to automate the whole routine. But I need a level closer to the client. I need to understand how a pressed button on the site will make the task work on the server with ansible. Now I think clearly primitive: Pressed button on the site creates an entry in the database. On the ansible server, the script accesses the database (once every 60 seconds?!) and takes data, processes it and performs actions, then puts information into the database that the task has been completed. So? That's pretty much how it all works. But for sure there is already some ready-made solution (framework), developments on how best to organize it. As soon as I sit down to write such a bike, I’ll definitely sit down for a long time to accurately take into account and automate everything.
While my thoughts are occupied by ansible. But as soon as the main work is completed, tested on virtual hosts, I want to immediately move on. What to read, in which direction to dig a tunnel?

Answer 1

e.g. daemon
e.g. queue server - see how Worker registers in it