3 ms·
A lot of startups' products are write-intensive applications with the following requirements: - strong read-after-write consistency (or their users could recei
by jamesmishra 5y ago
A lot of startups' products are write-intensive applications with the following requirements:
- strong read-after-write consistency (or their users could receive inaccurate information)
- as-high-as-possible availability (because they lose money whenever the site goes down)
- low-latency operations that are difficult to optimize--such as recommendations, complex full-text search, or large graph traversal
And engineering teams don't notice that their solutions are suboptimal until their product hits scale.
- Nextgrid 5y ago> And engineering teams don't notice that their solutions are suboptimal until their product hits scale. A lot of engineering teams scale prematurely. Maybe their complicated engineering playground will indeed scale to 100M users, at the expense of being extremely complex and costly from an infrastructure point of view, where as a more "boring" stack may not scale to 100M but will handle up to 10M in a much simpler & cheaper way. The more complex solution makes sense if you're sure you'll hit 100M, but megalomaniac founders' dreams aside, this rarely happens and they end up dealing with the unnecessary complexity & expense of a stack whose scalability isn't actually required.
- deleted 5y ago[deleted]