> Generally you want a hybrid model. Databases for SQL users and data lake for everything else.
I do a mix of data science and software engineering, dealing with the datalake is a nightmare and I avoid it at almost all costs.
You know what the first thing everyone I worked with wanted to do after pointlessly pouring everything into the black hole that was the datalake? Re-implement some kind of SQL (and database semantics) back on top of it again; except now it's worse.
I do a mix of data science and software engineering, dealing with the datalake is a nightmare and I avoid it at almost all costs.
You know what the first thing everyone I worked with wanted to do after pointlessly pouring everything into the black hole that was the datalake? Re-implement some kind of SQL (and database semantics) back on top of it again; except now it's worse.