I have no doubt HANA is the right DB model for today and future, with lower and lower price of RAM (price per GB) today, in-memory computing is a very effective way to handle both OLTP +OLAP requests. And the importance of OLAP requests is growing, we are stepping in the big data era.
HANA's core competence is it gives you nearly real-time feedback for OLAP requests, despite slower for OLTP. Even for OLTP requests, there are solutions: it is being solved by simplying data model, reducing footprint of index and aggregation tables in S/4 HANA, early-returning acknowledgement of commit. Application design shall consider more of this patter, no aggregation tables, no secondary index tables, put more fields in one table, let HANA do compression, thus avoid joins of many tables.
BTW, the rank for DB-Engines is based on popularity, how could HANA compete with Oracle regarding google searches + Twitter tweets + mentions in the web? 39 years old Oracle vs 9 years old HANA.
I read the so-called independent research by brightwork, is it really a independent research? it criticizes HANA takes 30-40 times memory than other DBs. Come on, it is a in-memory DB.
Its article is full of biases and without any convincing proof.
To the colleagues who are losing jobs, you might get hurt by this restructuring event, it is not your fault. Don't be sad, my friend, you expertise/skills will be respected and rewarded by the market.