Earlier quoted context omitted.
Thats a strong statement we only know about breaches that have a) being identified b) publicly disclosed
It requires concurrent execution on the same core of multiple VMs, which none of the major cloud providers do (at least on machines new enough to have Zen cores).
Move Back to Datacenters
11–20 of 97 posts
Re: Move Back to Datacenters
#12Re: Move Back to Datacenters
#13The conclusion completely handwaves the massive overheads that come with not only owning your own infrastructure, but also having to manage a complex platform stack and its security. The security points, which the main points hinges on, seem hyperfocused and in most cases misguided. Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere. The CPU attack example given is for AM…
Re: Move Back to Datacenters
#14The analogy of this article would be: Stop using airbnbs when traveling, just build a house.
Re: Move Back to Datacenters
#15The analogy of this article would be: Stop using airbnbs when traveling, just build a house.
Re: Move Back to Datacenters
#16The conclusion completely handwaves the massive overheads that come with not only owning your own infrastructure, but also having to manage a complex platform stack and its security. The security points, which the main points hinges on, seem hyperfocused and in most cases misguided. Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere. The CPU attack example given is for AM…
Genuinely feels like there’s a constant trickle of arguments from people looking to do all they can to shift the tides such that their skill set is more in demand. Or maybe it’s just an ideological obsession. I don’t know. I feel the same way whenever the “use C for everything” people catch a whiff of performance mattering and very strongly suggest that the only way to dig ourselves out of this mess is to move back t…
Re: Move Back to Datacenters
#17Re: Move Back to Datacenters
#18Re: Move Back to Datacenters
#19The conclusion completely handwaves the massive overheads that come with not only owning your own infrastructure, but also having to manage a complex platform stack and its security. The security points, which the main points hinges on, seem hyperfocused and in most cases misguided. Redshift is not internet facing. If your Redshift is internet facing, you've messed up somewhere. The CPU attack example given is for AM…
This completely misses the business case for cloud, and is why these sorts of analyses don't convince that many business folk, and why cloud use continues to grow fast.
The business case is that someone else is doing the infrastructure management for you, at commodity prices, but you still have complete, direct control over "your" resources and ability to easily automate everything.
This tends to save much more money than any % of your CPU, memory, and disk budget could possibly achieve.
It's sort of like saying, instead of taking cars from your corporate fleet to a repair shop when they break, repair them yourself! Just hire some mechanics, build or rent a garage and equipment, and voila! And also, why are you buying electricity from the electric company anyway? Just build a generator next to your office building! Maybe make it nuclear just like some of the big electric companies!
For many companies, the "just host it in a datacenter" argument is no less silly than these scenarios.
Re: Move Back to Datacenters
#20Is there some plugin that removes GIFs from blog posts? IMHO an article looses a lot of credibility if I also have to look at some unrelated GIF in an otherwise very well written article.
.gif^$domain=*.substack.com,image
.gif^$domain=*.medium.com,image
this would probably work, right?