81–90 of 223 posts
Earlier quoted context omitted.
> It's going to be a lot more involved Yes, and you can't escape that by outsourcing it. The complexity is still there, and it will still bite you when your outsourcer fails to manage it.
Same thing applies to AWS...
Earlier quoted context omitted.
Bottomline is that AWS gives you the tools to survive this outage within their own ecosystem. If there's an issue with relying only on AWS it has not been expressed in this outage.
exactly what tools helps make your large volume of data stored in a down region available to other regions without duplicating the monthly storage fees?
Kieran Healy @kjhealy@mastodon.social Always worth taking sentences that use “the Cloud” or “the Internet” and try replacing those phrases with “A shed in Virginia” to see how they hold up. “Our service is fully based in a shed in Virginia”; “All my files are in a shed in Virginia”; “A shed in Virginia was designed to survive a nuclear war”, etc. https://mastodon.social/@kjhealy/115407725852594322
On a serious note, resiliency takes effort and investment no matter where you host your content.
Earlier quoted context omitted.
Why is docker to blame?
It's subjective I guess, but I feel as though containerisation has greatly supported the large Cloud vendor's desire to subvert the more common model of computing... Like, before, your server was a computer, much like your desktop machine, and you programmed it much like your desktop machine. But now, people are quite happy to put their app in a Docker container and outsource all design and architecture decisions per…
Containers allow me to outsource host management. I gladly spend far less time troubleshooting cloud-init, SSH, process managers, and logging/metrics agents.
Earlier quoted context omitted.
Why is docker to blame?
It's subjective I guess, but I feel as though containerisation has greatly supported the large Cloud vendor's desire to subvert the more common model of computing... Like, before, your server was a computer, much like your desktop machine, and you programmed it much like your desktop machine. But now, people are quite happy to put their app in a Docker container and outsource all design and architecture decisions per…
Before Docker you had things like Heroku and Amazon Elastic Beanstalk with a much greater degree of lock in than Docker.
ECS and its analogues on the other cloud providers have very little lock in. You should be able to deploy your container to any provider or your own VM. I don't see what Dynamo and data storage have to do with that. If we were all on EC2s with no other services you'd still have to figure out how to move your data somewhere else?
Like I truly don't understand your argument here.
The only reason we can't leave AWS is because we have 500 terabytes of data in S3
Talk to the other vendors. I know of a place that had about that same amount and decided to have a redundant copy of all of their data in another vendor's S3-compatible product. That vendor paid for all of their egress fees as long as they signed a 12-month contract and used their tool for the migration.
https://aws.amazon.com/blogs/aws/free-data-transfer-out-to-i...
The 'experts' also made similar criticisms with the Fastly outage in 2021 and did anything obvious change as a result? In a week's time no national newspapers will be talking about this. Meanwhile, everyone that spends actual time in these areas: - Knows that running an operation at AWS scale is difficult and any armchair critism from 'experts' is exactly that. Actions speak louder than words. - Understands that the…