News for hackers. Stuff that matters.
Re:400 reasons to not use Microsoft Azure by Twirrim on Saturday March 01, 2025 @12:16AM (#43216217)
> Because if you under-provisioned stuff for your database, it might start going slow, and it would actually lag the web interface you would use to increase the resources!

What the ever loving heck... seriously?! Why wouldn't this be a control plane API that reconfigures a data plane?!

Re:400 reasons to not use Microsoft Azure by tombert on Saturday March 01, 2025 @01:05AM (#43216435)
I think it was querying the database to get usage information, and it was blocking the loading of the page as a result. It's been a few years, but if I recall correctly, the .NET API for changing the database provisioning did work, so some people would hack up a quick script to change resources in an emergency.

I think they did fix it eventually, because I know that multiple people on my team complained to Microsoft about it. Very short-sighted decision on their end, but to be fair it was a brand new product.

Re:400 reasons to not use Microsoft Azure by vosper on Saturday March 01, 2025 @01:11AM (#43216464)
This is how hosted Elasticsearch works today, too. Really mess up your ES? Good luck with the web UI!
Re:400 reasons to not use Microsoft Azure by motorest on Saturday March 01, 2025 @03:35AM (#43217294)
> 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.

Re:400 reasons to not use Microsoft Azure by BirdieNZ on Saturday March 01, 2025 @04:58AM (#43217760)
It'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.

Re:400 reasons to not use Microsoft Azure by UltraSane on Saturday March 01, 2025 @05:19AM (#43217885)
Control plane and data planes should be running on different hardware.
Re:400 reasons to not use Microsoft Azure by Twirrim on Saturday March 01, 2025 @09:37AM (#43219603)
It 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.
Re:400 reasons to not use Microsoft Azure by FridgeSeal on Saturday March 01, 2025 @05:49PM (#43224704)
Because that would be the smart and sensible way to design a service like that, and those words are unequivocally not associated with Azure in my experience.