Is it the Lakehouse suitable as a OLTP and OLAP system at the same time? Recently I have seen some discussion in the company I work and it is basicall...

[Anonymous]

Is it the Lakehouse suitable as a OLTP and OLAP system at the same time?

Recently I have seen some discussion in the company I work and it is basically if the Lakehouse is a tool to be used as both transactional and analytical system.

The discussion has gone around the pros of having everything centralized vs the original purpose of a transactional system.

I know this is not a question but I would like to hear your opinions around implementing a Lakehouse solution for both purposes.

[-werners-]

I would not use it as an OLTP system. The reason why is simple:

lakehouse is heavily dependent on 'big data file formats' like parquet, delta lake, orc, iceberg etc.

These are typically immutable.

In an oltp system you have to do a lot of small synchrone updates which is cumbersome in a lakehouse (because of the immutability of the files).

I don't see the added value (compared to an RDBMS) using a lakehouse for OLTP.

For OLAP workloads: totally.

[Anonymous]

Hi @Esteban Sierra-Munera​ 

Hope all is well! Just wanted to check in if you were able to resolve your issue and would you be happy to share the solution or mark an answer as best? Else please let us know if you need more help. 

We'd love to hear from you.

Thanks!