4 ms·
Great, you build only store and retrieve functionality. How: 1. Do you identify which types of content your users use the most? 2. Do you find users who are a
by bastawhiz 2y ago
Great, you build only store and retrieve functionality. How:
1. Do you identify which types of content your users use the most?
2. Do you find users who are abusing your system?
3. Do you load and process data (even on a customer by customer basis) to fine tune models for the QA service that you offer as an optional upgrade? Especially when there could be gigabytes of data for a single customer
4. Identify corrupt data caused by a bug in your code that saves data to the db? You're not doing a full table scan over hundreds of billions of records across almost 500 logical shares in your production fleet
These are just the examples I came up with off the dome. The job of the business is to operate on the data. If you can't even query it, you can't operate on it. Running a business is far more than just being a dumb CRUD API.
- fragmede 2y agoFwiw, you should able to answer #1 and #2 without hitting the main db if you've got good observability into your system.
- bastawhiz 2y agoObservability data comes from a drumroll database! Most analytics products that can answer these questions are just time series data warehouses.
- fragmede 2y agoa database, obviously, but are you really storing metrics and logs next to customer data in the same database, or did you skip over the part where I used the word “main”?