I am posting this as something that I believe is a negative example. The company is based around providing metrics for customers and provides a long list of issues they ran into, saying:
We couldn’t have known about any of this in the beginning. Sure, we could have assumed it, but then we’d also have never launched the product in the first place because we’d be spending all eternity optimizing for scale we didn’t have.
Building and, more importantly, shipping software is about the constant trade off of forward movement and present stability.
The thing is, what they described is entirely predicable given the service they are providing and they chose an architecture that does not handle the nature of metrics. This is being presented as a success of “shipping” but I think it is a failure of “thinking”. You can still ship after thinking. Building a metrics product around something like Cassandra is not more coslty than PostgreSQL.
I am posting this as something that I believe is a negative example. The company is based around providing metrics for customers and provides a long list of issues they ran into, saying:
The thing is, what they described is entirely predicable given the service they are providing and they chose an architecture that does not handle the nature of metrics. This is being presented as a success of “shipping” but I think it is a failure of “thinking”. You can still ship after thinking. Building a metrics product around something like Cassandra is not more coslty than PostgreSQL.