stackskipton

I mean, it's worth pointing out because either API pricing is crazy marked up and thus subscriptions are still profitable if they are used at full amount or subscriptions are subsidized and API pricing is more true cost. Sure, it could be second one but due to average usage, it's profitable overall.

If you price out Subscription limits against API pricing, subscriptions are 20x-100x less depending on model and so forth.

Easy. They hired Americans to be actual keyboard people but they didn’t know anything so they were basically a KVM. However Microsoft could say “Yes only Americans were making changes. “

>spotting the hallucinations

SRE here, spotting the hallucinations requires you to have the knowledge to know when it's wrong. Best way to gain knowledge on systems is actually working on them. If AI do all the work, then you don't get the knowledge.

Antitrust does not have "important service" requirement. What has happened in gaming is another travesty but there is plenty of people who would say it's not "important service". Antitrust must be universal.

I would agree but it doesn't change the fact that many companies do not have CD and have processes that must be followed for rollouts.

It's same problem we have when libraries get massive security vulnerabilities. Updating them is not always as easy as many would like.

You still have to rebuild each Application Container with new CACert and deploy them. Depending on teams are working, that can be disruptive.

No, companies don't use CosmosDB because it's NoSQL and plenty of Devs can and will screw that up. Not great when you are paying per transaction.

However, I know many which have switched MSSQL to Postgres/MySQL happily. Azure supports those well.

Azure using SRE here.

And Microsoft totally doesn't care. Azure supports Linux fine, DotNet supports Linux and everyone on $NonMicrosoftThing is likely still using O365.

Microsoft has done Forward Deployed Engineers; they just weren't call that. Nowadays, most of consultants are focused on Azure since that's where money is.

Windows ecosystem is not Microsoft focus. It's in supported phase where Microsoft will make some updates to it, but they are not spending a ton of money or attention on it.

I have but it's rarely done by buyouts or with same IC mass layoffs. There is also generally less managers.

Most of time, it's after all IC, they look at what's left, decide what moves to make and lay off the managers.

However, I have seen more and more where managers are told what's happening and they find new jobs before layoffs.

Not to mention that already have direct access to large consumer base, ad network to add on more revenue and supporting revenue in case they need to infuse it temporarily with more cash.

Yea, redeploying probably means relaunching the container and anyone using a JIT language can cause some CPU constraints.

Last job had a ton of .Net applications once when we did multiple Kubernetes redeploys, CPU spiked for 4 minutes on a bunch of nodes causing problems.

Ops type here, generally you have to fail an AZ and see what happens. If you have Dev/Staging environment that is exactly like production with plenty of tests, you can use that. I've seen only one environment actually like that though.

Since most companies would have to do it in production and they don't want to have customer impacting outage, they tend to do it during an actual outage.

Flares and spraying sounds like aerial firefighting. Small aircraft go ahead of big boys to mark positions with aerial flares and tankers come in to drop.