Skip to main content
10 events
when toggle format what by license comment
Jul 25, 2023 at 9:10 comment added Francesco Mantovani Let us continue this discussion in chat.
Jul 25, 2023 at 9:09 comment added Alexandru R yes, account are customers. So I was thinking of adding account_id as part of index (never query between customers). Yes, I know I need to move away from nosql, but is hard as I've used it intensively in last 10 years. Google and AWS but staging is on premise. You mean diff databases, not different tables? Why would be the benefit?
Jul 25, 2023 at 9:07 comment added Francesco Mantovani Well, what do you mean for "per account"? Are these "Accounts" customers? In that case I will use a different database per customer. You need to move away from the NoSQL way of thinking. No huge tables. On what Cloud are you?
Jul 25, 2023 at 9:03 comment added Alexandru R I'm on cloud, but needs to be portable. So need to go with something that's "standard" somehow. Indeed, I'm moving attributes to a separate column. Remaining question is if is worth 1 huge table or separate per account. (300-400 updates / minute in total and 500-3000 rows / account / day)
Jul 25, 2023 at 9:02 comment added Francesco Mantovani I totally agree with @LaurenzAlbe , the attr1 and attr2 need to become 2 separate columns. Are you on-prem or on the Cloud?
Jul 24, 2023 at 19:12 answer added Laurenz Albe timeline score: 3
Jul 24, 2023 at 15:43 comment added Alexandru R @FrancescoMantovani to design a database structure that is efficient for intensive updates and scalable. Reason to move is that current architecture does not do well with queries that are not based on compound key and have to do too many things in memory.
Jul 24, 2023 at 13:47 comment added Francesco Mantovani Why are you moving from NoSQL to RDBMS? I don't understand the problem that you are trying to solve here
Jul 24, 2023 at 9:00 history edited Alexandru R CC BY-SA 4.0
added 505 characters in body
Jul 24, 2023 at 8:50 history asked Alexandru R CC BY-SA 4.0