6 ms·
"At Dropbox, Kafka clusters are managed by the Jetstream team, whose primary responsibility is to provide high quality Kafka services. " And this is why AWS's
by deanCommie 8y ago
"At Dropbox, Kafka clusters are managed by the Jetstream team, whose primary responsibility is to provide high quality Kafka services. "
And this is why AWS's "Managed Kafka" service has a place.
I get why Dropbox moved off S3 - storage is their core competency and they thought they could/should do better/cheaper. But I'm surprised they would be wasting valuable dev time with this kind of overhead.
- Zecar 8y ago> storage is their core competency Not so sure about that. I post in every one of these threads, but they deleted our honeymoon photos on my wife's account and then deleted my account several months later without notice. I wouldn't trust them with a swap file. Move fast and break things is a terrible mantra for a file storage company.
- pwaivers 8y agoTheir core product is still storage, even if you had a bad experience. You may think Dropbox is a bad product, but OP's point still stands.
- gitgud 8y agoCan't say that I've ever had an issue with the reliability or service at Dropbox. Not sure they're known for moving fast either, as the product has changed very little in 10 years.
- toomuchtodo 8y ago> But I'm surprised they would be wasting valuable dev time with this kind of overhead. I'm not surprised at all. They have reached a scale where managed services are looked at with a critical eye, and are no longer the default.
- foobiekr 8y agoThis. AWS is most valuable when the management overhead is a double digit percentage of your revenue. At some point the AWS margin itself is genuinely larger than DIY. That should be obvious as it has to be so unless AWS’s own costs are dramatically lower which is only possible if their value is smoke-and-mirrors.
- halbritt 8y agoI don't think it's that hard to reach a scale where DIY makes sense. As was stated up above, the AWS kafka offering isn't complete. One could do something similar with a cloud formation template. The ElasticSearch offering on the other hand is fairly complete. At my scale, it would cost me ~$15-20k/mo for ES in AWS. However, I DIY my own ES cluster (in k8s) which costs me something like $5k/mo. The delta is roughly $120-180k/yr. An engineer costs me roughly ~$200k year with salary and benefits, so let's say the delta is .75 of an engineer. There are also risks to DIY that are hard to put an number on. ES is definitely a PITA to run, but it's core enough to our infrastructure offering that dedicating .25-.5 of an engineer to it seems like a worthy trade-off to me. It is also a unique enough type of workload that it yields an interesting learning opportunity for my team.
- toomuchtodo 8y agoI don’t disagree at all. Far too often, people wait too long to optimize away from a vendor’s offering. Their margin is your opex. Put that money back in your pocket.
- technion 8y agoIt also means you're in a position to pick up your stack and deploy it elsewhere if such a thing makes business sense in future. A lot of organisations are putting themselves in a position where that's not an option.
- halbritt 8y agoThe AWS kafka product is a non-product. One would have to reproduce the same effort there as anywhere else. 60MB/s per broker Took me about two hours worth of testing to reach that same conclusion. I like the Dropbox approach though, it is very thorough. One presumes that kafka is going to become a fundamental part of their infrastructure, in which case, this effort is a prudent investment.
- vaishaksuresh 8y agoAs it stands today, AWS' managed kafka is very limited. Single region and no TLS is a non-starter for a lot of places.
- deleted 8y ago[deleted]
- cbsmith 8y agoI'd use the Confluent managed Kafka service before I'd touch the AWS one.