3 ms·
Yeah that's what people who don't have much data do with good results. If you can do that, it's the right choice. Once you have data you move code to data and
by baq 2y ago
Yeah that's what people who don't have much data do with good results. If you can do that, it's the right choice.
Once you have data you move code to data and not data to code. It isn't a decision you get to make. You only decide how you do it.
- halflife 2y agoI’m sorry, but we have a lot of data. We just implemented the right procedures to consume it
- baq 2y agoIf you can do processing outside of the database you don't have a lot, that's basically the definition of a lot of data. Don't be sorry, try to not have more data.
- nejsjsjsbsb 2y agoThat's an odd rule of thumb. You going to do some processing outside of the DB, e.g. transformations, views. Then you have the event streaming and aggregations world. Then different type of DB. Distributed DBs where you could do processing on each node in code for example.
- baq 2y agoI think we agree. Transformations and views bring code to data (if you are willing to consider them code, which I am). Then when you say 'Distributed DBs where you could do processing on each node in code for example' it also sounds like exactly what I have in mind - code brought to data, not data to code.
- nejsjsjsbsb 2y agoAh I see- you mean network-wise. I was thinking domain wise.