2 ms·
> What the ever loving heck... seriously?! What's so surprising about that? If your CRUD operations take longer to do, and you're doing those to drive a GUI, o
by motorest 2y ago
> What the ever loving heck... seriously?!
What's so surprising about that? If your CRUD operations take longer to do, and you're doing those to drive a GUI, of course the GUI will lumber along.
- BirdieNZ 2y agoIt's good practice to separate out your control plane and data plane, so in this kind of scenario you can use the control plane freely to manage and scale up the data plane without worrying about the data plane underresourcing affecting your control plane operations. The reverse also applies; by separating them you can have issues with your control plane but not have the database go down.
- UltraSane 2y agoControl plane and data planes should be running on different hardware.
- Twirrim 2y agoIt shouldn't lag the web interface. There are common ways to handle this, such as making all resource mutations asynchronous, or if you want to keep it synchronous, ensuring that control processes get guaranteed CPU resources. It is not a particularly challenging thing to do.