Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

>A lot of what users need can be done this way in my experience.

In my experience, no, as the company gets to any complexity and size. The production DB is often optimized for use by the ORM/language of choice or there's twenty of them for microservices. This makes it really awkward to do some things in SQL. So now your engineering team is getting requests to keep changing the prod DB schema so analytics can be done more easily. More over the prod DB is likely 10% of the data your business needs. There's a reason companies like Fivetran exist to slurp fifty data sources into a warehouse. Marketing wants google and facebook and mailchimp data. Operations wants saleforce data. Finance wants stripe data. And they want all of this tied to the inhouse data.

Sure you can make reports in each of those services but then you need to tie them together and then people complain of differences in metrics and then you have a bad time.

edit: Not to mention analytics on what users do. Always fun when there's a billion row table in your production db for that.



Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: