3 ms·
The interesting thing is...how long before you have 10M users? I'm very much a fan of this sort of work--it's obviously useful for things like data collection
by angersock 11y ago
The interesting thing is...how long before you have 10M users?
I'm very much a fan of this sort of work--it's obviously useful for things like data collection from sensors--but I can't help but wonder if it has any practical business value for early-to-mid stage startups.
- phamilton 11y agoOthers have cited the Phoenix example of 2M. We sort of take it for granted that you will have to rebuild your architecture once you hit that point. What you gain for that is a platform where you can be productive and iterate quickly. What the Phoenix example shows is that without a huge loss of productivity up front, you can put off the rewrite much longer. Presumably, Go would provide similar benefits.
- rozap 11y agoThe important thing about Phoenix is that it uses regular old pg2 groups for pubsub that can be distributed across nodes. Phoenix already does sharding for you, you just need to add another node and the stuff just works. When I was first playing with multi node Phoenix stuff I was amazed. It was too easy to scale horizontally. I'm not sure what the distribution story is for Go...
- phamilton 11y agoThe distribution story in this article is "publish via Redis". I much prefer Phoenix's approach.
- tim333 11y agoI guess if you're writing anything with messaging you may ponder how to work it if you get millions of users even if the probability is low.