3 ms·
Yes. Customer analytical record tables are extremely wide. I have a number of enterprise customers who have use cases with tens of thousands of columns. And tru
by threeseed 9y ago
Yes. Customer analytical record tables are extremely wide. I have a number of enterprise customers who have use cases with tens of thousands of columns. And trust me that every enterprise is moving to having one since they are needed for fast supply of data to decisioning systems like PEGA.
That's why I always find it hilarious when HN goes on about just using PostgreSQL or some other SQL database for everything when they don't understand the use case. They simply doesn't work in these scenarios.
- YCode 9y agoI'm ignorant on this topic... Why so many columns? I would expect there would be some way to break the data down or transpose it somehow to make it more manageable. At that point are you even really dealing with a database as most people use the term?
- threeseed 9y agoBecause they are attributes of a customer or a product. And many companies these days know a LOT about you as a customer e.g. everything from your age to how likely are you to purchase product X. It has to be one table because you need to get attributes of a customer very quickly (single digit milliseconds) in order to respond with the next best action e.g. show this advertisement or route them to this call centre person. And of course this is a database. It's all of the information about a customer in one place.