81–90 of 187 posts
Minor nitpick, 10.2.0.0/8 is not a valid subnet mask. The largest subnet you can make starting with 10.2.0.0 is 10.2.0.0/15. As far as I can tell everything was done in 10.0.0.0/8 but Amazon has took down EC2-Classic documentation. https://web.archive.org/web/20150302235811/https://docs.aws....
Earlier quoted context omitted.
I see Reader as Google's attack on RSS' popularity. The product was killed off when its job was accomplished.
I think it just was never going to get the mass adoption it needed to justify the upkeep.
Earlier quoted context omitted.
Google Reader. Never forget.
I see Reader as Google's attack on RSS' popularity. The product was killed off when its job was accomplished.
https://www.theverge.com/23778253/google-reader-death-2013-r...
The article above is actually very interesting, because the story it tells is that Google's two highest-profile failures are actually one failure. Facebook freaked them out so much that they scrambled to build something comparable with Google Plus. Google Plus stole most of the company's mind share but was executed so poorly that it never went anywhere. The company got major egg on their face from suffocating Reader to make Plus, then again when Plus died after having been pushed so hard.
So if I'm understanding correctly, all the classic instances were migrated to more modern types with no intervention from the account holder? Did they suffer a reboot during that migration, or was it done via some live-migration process (it's hard to live-migrate off a virtualization platform that was never designed with that in mind!). What about the original network setup? Is that still emulated, or might some cust…
I don't know the details of this particular migration, but I used to have a VM in some low-price tier that was running for a long time (few years), and, eventually AWS sent me an email telling they are going to shut it down for maintenance reasons. Guess this was something similar. VMs, if not specifically configured to be able to move cannot really be moved automatically. Think about eg. randomness of ordering in PC…
> one giant network of 10.2.0.0/8 Huh? Do they mean 10.0.0.0/8, or 10.2.0.0/16 (/15 would also work), or is this a new CIDR notation? Something specific to AWS, maybe?
This is something Google Cloud should learn from. It doesn't matter if product XX still makes money or fits in your business model. There are people who rely on it. And they'll remember if the vendor kept it running trouble free for years. They'll also remember if it was arbitrarily shut down or the price was suddenly increased by 4x and they had to spend many man hours migrating to another option. (Google maps api?)…
Google Reader. Never forget.
OTOH, I successfully skipped the whole AMP saga because I could tell from the start that it was bullshit.
Earlier quoted context omitted.
Do they really not do live migration or at least auto-restart (if configured) in those cases?
They have live migration now (for many years) but they didn’t back in the early era. I’m not sure they set it up for the classic environment but I think they must have - in the early 2010s you could get notices that your VM’s host had failed or was about to fail and you needed to launch a new one but I think that stopped by around 2015 as I had servers running for a deprecated project which were finally shutdown this…
I haven't spun up anything in the cloud in a while. I used to dabble in both AWS and Digital Ocean. Usually went with DO because it seemed simpler and my projects were super small (and they had a lot of relevant guides to spinning up X, Y, and Z service on their systems). What is the difference between EC2-classic and whatever is available today? Are you still able to just get a linux box with a public IP address?
I think there's Lightsail for such use now - https://aws.amazon.com/free/compute/lightsail-vs-ec2/
Stated justification was "If we don't bake this in now, it'll be harder to do later", but it was mostly a couple fokls in charge wanted to learn new stuff (someone said that out loud later, confirming my concerns about resume-driven-development).
EDIT: FWIW, my couple small experiences with lightsail itself were fine. Seems like a decent onramp to ease in to the AWS ecosystem, if that's on your roadmap.
Earlier quoted context omitted.
They don't need to threaten. Their SLAs don't offer to run VMs indefinitely. AWS will send you an email about shutting down your VM if, eg. they need to rotate the disk used for storing VM image etc. It's somewhere there in the contract, and it's a usual process for someone who keeps long-running VMs in EC2.
Do they really not do live migration or at least auto-restart (if configured) in those cases?
Earlier quoted context omitted.
I think it just was never going to get the mass adoption it needed to justify the upkeep.
The upkeep was apparently 12 engineers and they had tens of millions of users. It doesn't take that many users to justify 12 engineers plus infra, so it sounds like it was more that Google doesn't care to operate any product unless it will have users in the hundreds of millions.
Otherwise, those 12 engineers and infra are pure negative on the balance sheet