I am so surprised that so many people have been layed off from the HANA team. From execs all the way down to developers and PM's. How can this be? I thought HANA was core to SAP's future?
https://www.cmswire.com/information-management/a-tale-of-two-saps/
https://www.brightworkresearch.com/saphana/2019/03/08/saps-layoffs-and-a-brightwork-warning-on-hana/
Singapore also badly hit. None of us expected it.Heard Shared Service laid off as the whole operation will be transferred to Manila. Low or rather no morale. Heard another wave coming but keeping fingers crossed
You are earnest about in memory superiority, that I agree. But you have not checked out the competition. There are so many in memory data bases in the market now, and they are not half as expensive as HANA. Why should a customer invest in HANA, except for the fact that Sales has been arm twisting the customer during upgrades and renewal contracts
Reference to post @Y30tBHA-3maj regarding HANA being the right DB model for today and the future: Wow, if this is not the party line! Does Google and Facebook need HANA to search through massive amounts of data and do joins? What they do is OLAP on steriods and there are far better ways of searching, indexing, and processing data than putting it all in-memory. HANA was purely an academic exercise and should have stayed in academia.
Did Salesforce and Workday invent their own database? No. Are they both doing great and gaining market share? Yes. Why are they doing so great without their own invented in-memory database like HANA? Because they did not waist their time and $ inventing a new database and instead focused on inventing great applications and usability.
A real time database? Please. The only person I have heard that spews that nonsense is Hasso, because nobody has the stones to tell him the truth. I love seeing my colleagues faces cringe when Hasso speaks.
who buys HANA tell me other than SAP forcing s4hana.... HANA is c-ap
HANA was not "born" in the US.
So it will survive - just that the workload in other locations will increase.
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.
see https://db-engines.com/en/ranking_definition.
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.
one question - what is the HANA adoption outside of SAP ERP/S4 customers? I see it as almost zero when I look at the stats.
Containers are being build and shipped into Waldorf as we speak. In addition to build-up in China. So HANA will continue be developed, not in the US and may see all development coming from these 2 locations.
How will this work out, only time will tell.
We all drank the SAP cool aid - from your manager to your manager's manager. Somehow the music has to stop and everyone has to stop dancing and find a chair.
I think this is a cost cut strategy to cut side areas of HANA which were not looking too promising for the future strategy. There were a lot of extra modules and plugins, so maybe a hard cut and focus on core competencies was better and slowly diverging into too many areas.
Sad for the affected empolyees of course who did their best to support "their" module.
What happened to all the HANA servers sold to Huawei years ago? Are they consumed? The PR release had Bill’s name in it.
Big bosses in different HANA locations are not thinking how to corporately build better HANA, but try to hold things in hand to build their own kingdoms.
And the boss who close to 帝王...... win finally.
Not all the blog posts are written by “SAP” haters.. those in Germany have never experienced the cut backs and layoffs other countries do such as the US where we do not have laws protecting employees like in Germany and other countries. Unlike Germany layoffs are NOT voluntary unless you qualify for the voluntary early retirement when it’s offered, then employee can choose, otherwise layoffs are may have no relationship to performance as evidenced now. With this round of layoffs offices were closed, teams were let go, experienced, dedicated contributors let go. Cuts were deep — there was a financial target to be met. SAP lays off every year, most years done quietly but it happens, other years it’s larger more public, then certain years like 2019 — the numbers are larger than expected in areas not expected, but definitely haalening in the expected countries.
HANA leadership is arrogant. I'll leave it at that. Overall, the product is OK, but the leadership is messed up and I have hard time seeing them being really successful in anything they do. This is a biased one man (ex SAP) opinion, please treat it as such.
User @gam is correct when she/he says: "Those blog posts are written by authors/companies who have always been very vocal about not liking SAP" - also, keep in mind that they hammered the USA based resources, the rest of the teams are intact. Not sure if this is intentional and if cuts are coming to Korea and Germany but overall, the product is sound, the customers are buying it and a lot of hoopla in the research shared just does not have factual backing. But, you never know - we'll see if the executives agree with me.
I was in a team working with hana and we were getting successful metrics so nobody can explain why the product with growing adoption has some of the team laid off unless it is true functions were replicated in other locations... the technology is fine and i saw it working
Those blog posts are written by authors/companies who have always been very vocal about not liking SAP.. there are no facts backing up their statements so it just sounds like they are taking the opportunity... an opportunity left open by SAP not communicating what is going on... core hana dev teams are untouched and in Germany and Seoul
HANA definitely a failure. It was inevitable. Building commercial grade transactional databases are hard. Microsoft invested years/decades and still does not come near Oracle. SAP screwed themselves when some id--t on HANA team convinced senior management they could take a columnar database and make it a competitive OLTP. Years and energy wasted.
US development locations were never key locations for HANA.
It's Germany and Korea and they remain unchanged.
I am on the HANA team in Canada. Still have a job, for now. Not sure if it's a failure, but the organization part of it is a failure. The technology is fine. When you've gone boneheads running the sh*t show, and managers talking like hot shots, that's where the buck stops. I wouldn't be surprised if me and my team is the next to get eliminated.
Maybe it is true that HANA is a big failure?