4 ms·
Whether to use infrastructure depends on the complexity of what you need and how many steps removed it is from the core value you're delivering. Infrastructure
by naasking 5y ago
Whether to use infrastructure depends on the complexity of what you need and how many steps removed it is from the core value you're delivering. Infrastructure has configuration costs, an opaque debugging and hardening process, and maintenance costs too. The more complex the problem this one component solves, the better the value proposition of using a third-party solution as infrastructure.
However, if the component is key to your value-add, the less likely such solutions will fit your needs exactly, and so it might quickly become a bottleneck. You might then find yourself rolling your own solution anyway. Just use good judgment.
This is why there are so many different database types now, ie. key-value, time series, etc. Relational databases aren't perfect for every problem, they're just good at most problems. But you should probably stick with relational databases unless you know for sure you're better off without one.