Planetscale is really being pushed on this site lately but all I see is theory and promises of doing things different for vague reasons. I hope I'm wrong or just not understanding something but it feels like a CEO trying to sell a product without understanding the technical reasons why a project like this hasn't existed before. I can't imagine that planetscale is going to solve something that Google, amazon, Facebook, apple, and Netflix all failed to solve for a similar use case and for well documented reasons.
I thought the common denominator for this was (and has been, for decades) ETL? Extract, Transform, Load and in that order, because what other order would make sense?
Getting such basic things wrong doesn’t exactly give the reader the impression that the writer knows the subject particularly well.
Its not a typo but describes a product difference. ELT is a common term for a new type of data eng workflow that isn't mapped to ETL. In most ELT products the raw data is loaded into and then transformed by the data warehouse tool. As opposed to the ETL pipelines many of us are used to where the data gets transformed in a separate process before being dropped into the DW.
data warehouses are now processing engines that scale compute independently of storage. you can simply dump your raw data into warehouse and do your transform there. Hence ELT.
worse, theyre pricing is based on innodb_rows_read, even includes cached rows.. so every single ELT job costs $$$ based on how many rows you have, even if all in buffer pool cache already
[+] [-] cosmiccatnap|3 years ago|reply
[+] [-] josteink|3 years ago|reply
Getting such basic things wrong doesn’t exactly give the reader the impression that the writer knows the subject particularly well.
[+] [-] edenlinger|3 years ago|reply
[+] [-] dominotw|3 years ago|reply
[+] [-] mmcgaha|3 years ago|reply
[+] [-] RHSeeger|3 years ago|reply
[+] [-] moltar|3 years ago|reply
[+] [-] NonNefarious|3 years ago|reply
[+] [-] ushakov|3 years ago|reply
i feel like every day of a month there's a new flavour coming out
[+] [-] dominotw|3 years ago|reply
[+] [-] mjirv|3 years ago|reply
Step 2: paywall customers’ access to their own data so you can brand it as a premium feature/product
Step 3: ???
Step 4: profit
[+] [-] throwusawayus|3 years ago|reply
double-worse, innodb_rows_read known to be buggy! example https://jfg-mysql.blogspot.com/2022/03/rows-examined-not-tru... -- this bug is in customer's favor but what if other bugs are not?!