Transcript
0:00an impossible database per customer
0:02a database for all
0:03is a disaster I show you how
0:04we manage more than a thousand customers
0:05assets in production
0:06in invoicex our electronic invoicing sat
0:08we have more than a thousand customers
0:09assets if we had created a database per customer
0:12we would be talking about more than a thousand databases
0:14that is unmanageable
0:16what happened was as follows
0:17we group customers by volume of use
0:19today we have five databases and each one manages
0:21about three hundred
0:22customers all
0:23share the same structure
0:24but are logically separated by an id company and each
0:28company has a
0:29tenant id now when a customer grows a lot or needs
0:32isolation we move them to a group with less load
0:34in extreme cases to its own database each customer
0:38has a company and in each company is registered
0:40on a small field where they have a living
0:42the software reads
0:43that when logging in and dynamically connects
0:46to this database
0:47the customer never knows
0:48for him it is transparent and not a technical decision
0:50a customer business decision
0:52small will pull shared
0:53customer with high volume to less loaded group customer
0:56enterprise that pays more insulation
0:57total if required
0:58multitenan is not black and white,
0:59it is a scale.
1:00and defines it
1:01you according to size,
1:02risk and value of each customer
1:04how many customers
1:04you have in one database
1:06I read you in the comments
Mind Map
Loading mind map…
