1,141 karma · joined January 29, 2012
But for companies picking a cloud platform tomorrow, that’s a fate as good as death! AWS and Azure won’t slow down development and new features, so a couple years after GCP stops being a priority, it’ll start also being a bad deal, and a couple years after that it’ll be a straight-up strategic liability. THAT is why anything other than full-throated support from Google leadership for indefinite GCP investment will lose them business.
In other words, this case only directly applies to physical businesses with an online component (buy-online-pick-up-in-store or similar).
I’ll be curious to see – assuming that Robles eventually wins – if this case is ever used to argue that an online-only business is subject to Title III. It doesn’t seem like a slam dunk connection.
(Not a lawyer, but I do enjoy reading court documents.)
Jon Bois had the right of it: https://www.sbnation.com/a/mlb-2017-season-preview/there-is-...
If Instagram is using https://developers.facebook.com/docs/facebook-login/ with the little “log in with Facebook” button, it’s a social login. If they have their own proprietary way to do it in-house, it’s not, and not subject to Sign In With Apple.
That easy.
It's also worth looking up the story of why Coordinated Universal Time is abbreviated UTC and not CUT, if you haven't heard it. Time zones are great.
The “whims” of Amazon’s pricing are no more unpredictable than the pricing “mood” of your colo or your hardware vendor.
But if you need bleeding-edge Postgres performance, you hire a DBA, and they probably build something on EC2 or bare metal.
———
As I understand it, RabbitMQ is probably a better point of comparison for SNS/SQS, and Kinesis is the Kafka peer.
Regardless, the reason you don’t “just” run Kafka is: you don’t have a team that knows how to tune, deploy, and operate a production Kafka cluster. I learned enough about SNS and SQS to get it running in an afternoon, and I really haven’t needed to think about it since. Kafka (or RabbitMQ, or ActiveMQ, or etc) need instrumentation and monitoring and patching and quorums and capacity planning and etc, and at some scale those are worthwhile, but that scale is MUCH larger than what most Kafka clusters are actually serving.
———
The theme here is: if you have a business requirement for 90th percentile specialized performance, great! Hire domain specialists who can make your systems run at that tier! But for everyone else in the world, when you can get usage-based pricing, elastic resources, and automatic durability and patching... why would you go to the trouble of learning how to deploy and manage a service?
Suppose somebody working on Hacker News wants to redesign it, and wants to know if they should optimize for long visits or short visits. If they call me on the phone and ask me how often I open HN and what my mean usage duration is, I’m just going to make up numbers. Their website analytics, on the other hand, can tell them something closer to reality.
I’m not saying that’s good or bad; I’m just saying that our devices are often more reliable records of ourselves than our own memories and thoughts.
I say a lot of things in the form “I’m a little out of my depth in this subject, but my best understanding is that the behavior should be such-and-such; does that sound right to you?”