SAP HANA Enterprise Cloud – What the HEC(K) is going on?!?
Time flies – SAPPHIRENOW is already past us and as everyone is heading home from the annual pilgrimage to Orlando I find myself in my hotel room digesting all the news we’ve heard the last couple of days. There were plenty of announcements big and small again, yet the one topic that I’ve been thinking about lately has been the SAP HANA Enterprise Cloud (HEC). For various reasons this caused a lot of interest (which is good) and confusion (which is not so good) within the ecosystem/industry. Given the importance of this topic and the fact that I’m very passionate about it I would like to weigh in and do my little part in helping to make you understand of what the “HEC(K) is going on” – and how it all fits together.
One word upfront: please note that all of what is to follow is my personal point of view and must not be mistaken as any official statement by SAP. I rather summarize and build up on some great blogs by SAP Executives and well-respected analysts and bloggers alike and weave them together. As such, I strongly recommend to everyone to read the referenced articles, blogs and twitter conversations themselves in order to get the complete picture. If my own reasoning should be off (your judgment!) than at least the collection of references provided may help people to quickly come to their own conclusions…
So, what is the SAP HANA Enterprise Cloud? How does it relate to the SAP HANA Cloud Platform? Is the term Cloud justified? Is it IaaS, PaaS or SaaS? What’s the impact for customers and partners? For developers? These are the sorts of questions I would like to address.
Let’s start by getting a common understanding of what the SAP HANA Enterprise Cloud is. As HANA is Vishal’s “little girl” it’s only fair to let him be the first to raise his voice and talk about the fusion of HANA + Cloud:
“With the SAP HANA Enterprise Cloud […] we are simplifying customers’ experience and expanding their choice in how they want to adopt SAP HANA, now bringing it to a massive scale for enterprise mission critical applications – and we are doing this without disruption through the cloud.” – Vishal Sikka [Ref]
For me this paragraph of his blog summarizes all there is to know to get the discussion started into the right direction. It’s all about:
- simplifying the customers’ experience (simplicity)
- expanding their choice (openness)
- massive scale (scalability)
- without disruption (faster innovation cycles)
These four principals are the motivation for and the foundation of the SAP HANA Enterprise Cloud itself and as well the underlying platform (SAP HANA Cloud Platform). Before we dig deeper, let’s have a closer look at what HEC is offering. The high-level (!!!) marchitecture diagram looks like this:
Aiaz Kazi describes the SAP HANA Enterprise Cloud offering as follows:
“SAP HANA Enterprise Cloud is a cloud based managed service offering for SAP customers and partners to deploy their HANA applications on a modern peta-scale cloud. By running mission-critical SAP® ERP, SAP® CRM and SAP NetWeaver® Business Warehouse applications in a managed cloud service model ,SAP aims to enable organizations to realize faster time-to-value coupled with lower total cost of ownership. SAP HANA Enterprise Cloud also supports custom HANA applications, including non-SAP centric ones.” – Aiaz Kazi [Ref]
In a nutshell, the value proposition is to provide our customers with an additional deployment option enabling them to run the SAP Business Suite, BW and other HANA-based applications in the cloud. In my own understanding this deployment option is best described as providing a Software as a Service (SaaS) offering, yet others may interpret it differently and call it little more than hosting. One common argument being the licensing model associated with the offering (Bring your own license – BYOL.)
Finalizing questions for SAP executives at #SAPPHIRENOW on HANA Enterprise Cloud ; my take is still it sounds more like hosting then cloud
— Harald Reiter,PMP (@hreiter) May 12, 2013
Whatever your stance on this matter, the underlying motivation adheres to the value proposition of SaaS, which is to allow customers to focus on other things than managing and operating their core business systems. In today’s fast-pace world companies are well advised to focus on driving innovation that sets them apart from the competition. Managing and running their core processes while keeping them constantly up-to-date is something that many would be willing to have a trusted partner (such as SAP) do for them.
The Licensing debate
“The announced HANA Enterprise Cloud follows the “Bring Your Own License” paradigm. While this is great for customers that already have a HANA license and would like to relocate it into the cloud, it is useless for customers that might have largely fluctuating data volumes or user numbers and might specifically use a cloud because of its elastic business model.” – Stefan Ried [Ref]
While I understand that pay-as-you-go is considered an important aspect of cloud computing I wouldn’t go so far to make the (current) lack of this option a legitimate reason to state that HEC is not a true cloud offering! Looking at the current ecosystem and the nature of the Business Suite systems of our existing customer base it make sense to start off with a business model that is closer to what the business is used to, because it eases the transition and onboarding. It would surprise me if there wouldn’t be some smart minds at SAP working on some alternative pricing models right now to complement the current offering. Plus, the vision and value proposition of HEC is far greater than just “hosting” the traditional SAP applications in the cloud, there’s also a Platform as a Service (PaaS) component to it!
SAP HANA Cloud Platform
The close observers of SAP’s cloud activities know that SAP is offering an open-standards based PaaS solution since fall last year launched as “SAP NetWeaver Cloud” (internally known as NEO). A very common question I’ve heard frequently these days has been whether or not SAP HANA Cloud Platform (HCP) is NEO.
Yes it is! SAP HANA Cloud Platform is NEO – our New Enterprise Offering in regards to PaaS.
OK, jokes aside. The best way to look at it is that NEO has been integrated into the broader SAP HANA Cloud Platform plus a whole lot more. Björn Goerke wrote a great summary blog post about it, which hopefully helps to clarify some of the confusion.
For those that are not too familiar with this PaaS offering, here’s a short description:
“It is (and remains to be) SAP’s only public Developer Platform-As-A-Service (PaaS) offering that allows SAP partners, SAP customers and SAP development itself to build, deploy and operate applications in an open and standards-based Cloud environment. Building these applications is made easy by our offering of a number of shared application services and in particular the power of SAP HANA in a service-based manner. The SAP HANA Cloud Platform is hence tailored towards the huge SAP developer community: It provides both Java and Java VM-based language environments like Java itself, (j)Ruby, Scala, Python, Clojure or Groovy as well as HANA native development capabilities like e.g. SQLScript or River Definition Language.” – Björn Goerke [Ref]
The corresponding marchitecture illustration of the SAP HANA Cloud Platform looks as follows:
For software engineers this is great news, because the platform provides a lot of capabilities typically required in software development without enforcing a pre-defined programming model, but rather it’s all about choice. Aiaz summarized it as such:
@fredverheul HANA Cloud Platform 2 offer Native (XS), Integrated (River/RDL based), and Open (Neo-Java/JVM based) dev experiences.
— aiazkazi (@aiazkazi) May 8, 2013
In other words, the vision of NEO is stronger than ever. It only spells NIO now (Native, Integrated and Open).
I believe that this is a powerful combination and a platform that provides developers with lots of capabilities to develop great applications. Which programming model to use is up to you! Platforms are all about adoption, so it sounds like the best only way forward to not restrict it to one programming model, but instead let developers use their programming model/language of choice!
Personally I see that XS may be the best choice for data-centric applications such as analytical dashboards, as XS provides native access to SAP HANA and it’s simple to expose endpoints to be used by the UI. RDL will come in handy as a Rapid Application Development tool for smaller use-cases focusing on very specific tailor-fitted scenarios and such. And thanks to the flexibility of the JVM-based runtime capabilities through NEO you can develop more complex business applications in Java (or any other JVM-based language).
Cloud is all about scaling. What surprises me to hear though is that prominent voices wonder about SAP HANA Enterprise Cloud’s capability to scale?!?
Given Amazon’s almost infinite capacity, can SAP’s own HANA cloud scale as it moves away from AWS?bit.ly/105qUUY #sapphirenow
— Vinnie Mirchandani (@dealarchitect) May 17, 2013
As announced during the keynotes at SAPPHIRENOW the whole thing (internally named “petabyte farm” [Ref]) has been brought to life considering the scale it would require to run ALL SAP Business Suite systems of our existing customer base. One of the guiding design principels of SAP HANA has always been the ability to scale and it has been build with parallelism from the ground up. Last year we already had a 100TB system [Ref] and we sure didn’t stop there.
However, that debate is missing the point I think. Shouldn’t the question rather be whether or not HEC can scale as required/driven by demand? Should SAP ever be confronted with the challenge of not being able to cope with the demand then the adoption would probably be exceeding SAP’s wildest imaginations! If that’s the primary concern, then we are up for a ride!
Faster innovation cycles
As I already stated, companies are in need to adopt to the demands of a constantly evolving global market. They need the ability to quickly adjust in order to stay competitive. Taking the burden of operating their core systems off their shoulders and providing them ways to develop and roll-out new innovative products is how SAP tries to support them in achieving this. The former is addressed by the SaaS aspects of HEC, the later by the integrated PaaS offering (SAP HANA Cloud Platform). I recently wrote a longer post on the value proposition of PaaS titled The Cloud Platform Play, hence instead of repeating it all here I rather like to encourage the interested reader to check it out.
I’m an SAP employee and hence the critics will probably say that I drank too much of the “kool aid“. This is why I collected all the related information I deemed important so that you can come to your own connclusions. I believe the SAP HANA Enterprise Cloud and the integrated SAP HANA Cloud Platform are the foundation of the “new SAP” and the result of our intellectual renewal that Vishal is driving within SAP.
It’s surely in its infancy and there are valid questions yet to be addressed, but isn’t that underlining SAP’s ambition to establish open communication? With this post I tried to provide a solid set of reading material for people to familiarize with the topic and personally I’ll be closely following the discussions. Matter of fact, I see it as the primary part of my role as Cloud Platform Evangelist to engage with the community and exchange thoughts and ideas. I may not have all the answers myself, but I’m willing to surface them so let us know what you think!
SAP’s Point of View
- Sunshine on a Cloud Day by Vishal Sikka
- Evolution of the SAP HANA Cloud Platform by Aiaz Kazi
- SAP HANA Enterprise Cloud, SAP HANA Cloud Platform, SAP NetWeaver Cloud, “NEO”, … Confused? by Björn Goerke
- SAP HANA Enterprise Cloud Pro and Cons by Stefan Ried (Forrester)
- Understanding the HANA Enterprise Cloud: An initial whiteboard by Dick Hirsch
- SAP HANA Enterprise Cloud: early thoughts by Dennis Howlett (diginomica)
- Bluefin on SAP HANA Enterprise Cloud by John Appleby (Bluefin Solutions)
- Hana Enterprise Cloud helps SAP discover the cloud (benefits) by Holger Mueller
Hi Matthias, thanks for that great blog.
It helped me a lot to understand "What the HEC(k) is going on with NEO?" and alleviated many of my headaches.
Many thanks for the kind works Matthias, but I'm clearly standing on the shoulders of giants here. Björn and Aiaz did the major work of clarifying the messages for SAP and teh referenced bloggers from the outside added a lot of food for thoughts.
Still, happy my post helped you to find your way through it. That was all I wanted to achieve with it anyway. 😉
thank you. Great Blog. However i maybe have some "understanding problem" by the offered service and here it comes:
These 4 words in relation are contradictory (in my opinion).
We talk about 7 x 24 applications, if we mention mission critical applications, that needs to be available all the time. We usually talk about a system landscape with a lot of satellite systems and end devices (like wireless scanners, printers and so on).
Apart from the "still needed" technical customer infrastructure the most important point is "without disruption". Is this really realistic by putting your mission critical system / application in the cloud on HANA?
We usually talk about data center and database mirroring over long distances, real high availability (like transparent application fail-over), flexible recovery scenarios (like multiple rolling forward or backward), no single point of failure (like network) and so on if we want to realize real 7 x 24 systems. Is this possible with HANA in the cloud?
I am not aware of such technical HA / DR possibilities with HANA right now.
The name "mission critical" seems to be more a marketing approach, but has currently nothing to do with real "mission critical / not to fail" systems (in my opinion).
Have found the related information in the FAQ pdf
So my assumption was right ... "Mission Critical" is only a marketing name.
99.5 % availability of the application per month means: 30 days * 24 h = 720 h * 0.005 = 3.6 h downtime per month or 1.8 days downtime per year due to disruption. RTO of 4 hours for mission critical systems? 😕 .. and what about RPO in case of a disaster?
P.S.: Please correct me, if i am wrong and missed some technical innovations by HANA as a cloud service.
Sorry for the late reply Stefan, but I published that post just before entering the plane home from Orlando.
Sounds like you found the FAQ document in the meanwhile. Well, since you found the promised SLAs I leave it up to you to decide whether that justifies the "mission critical" term. I'm not a basis guy myself and hence cannot compare it to the average availability of the installed on-premise systems of our customers these days. However, compared o other cloud SLAs it seems rather comparable...
maybe this blog by David Hull about SAP HANA's HA and DR capabilities in SP6 will be of interest to you: http://www.saphana.com/community/blogs/blog/2013/06/27/the-truth-about-sap-hana-and-hadr
thank you very much. That kind of information was missing all the time. Now it is clear what a HANA infrastructure can do right now and what not.
Thanks again - it is very good.
first thanks for teaching me a new word with "Marchitechture".
Secondly, I still find myself confused:
So the open JVM PaaS part of the SAP HANA Cloud Platform is the thing we have previously known as NEO. Cool with that!
Right now I go to developers.sap.com and read:
So the "open" part of NEO, (the JVM standards based PaaS), is called SAP HANA Cloud.
Which lead to the remarkably obvious observation that
"SAP HANA Cloud" is part of "SAP HANA Cloud Platform".
Now if I just consider the above to be chains of characters - then yes this makes sense.
But if I even attempt to use my brain in just the slightest little bit, I get immensely confused.
I'd suggest that actually the "open standards based PaaS" (formerly known as SAP NW Cloud) is part of SAP HANA Cloud Platform which is part of SAP HANA Enterprise Cloud, which all described as "SAP HANA Cloud"?
This last way of think make some logical sense when I think of the words involved. I.e. an Enterprise Cloud is a specialisation of a Cloud and a Cloud Platform makes sense underlying it all.
Yet - I don't think I've seen "my" way of putting it reflected in SAP's message (i.e. on SAP's websites). So, I guess I'm wrong. In which case, I think it's not surprising that we're confused.
many thanks for bearing with us. You almost got it right. First off, "SAP HANA Cloud" and "SAP HANA Cloud Platform" is the exact same thing. The "Platform" suffix was recently added by One-Voice. Yet, as the product formerly known as NEO was always a Platform we did not make a big announcement about this. :/
So, the SAP HANA Cloud Platform (HCP) is the PaaS aspect of the SAP HANA Enterprise Cloud (HEC).
In a nutshell, HCP provides three different developer experiences - NIO:
N = Native via XS
I = Integrated (RDL)
O = Open (JVM-based) runtime
Now, one could think that the O is what we called NEO in the past, but as some of the platform capabilities (called SAP HANA AppServices in my 2nd illustration) provided through NEO will be available to other developer experiences of HCP as well that would not be semantically correct.
We have already started working on a much clearer messaging - so please stay tuned!
Man thanks for all your support through-out the last year and keep up the great work!!!
Thanks for the BLOG. I to am trying to work my through how all the various parts fit together and you've helped clarify with what you've written...but you've also muddled one thing I thought I understood. "SAP HANA CLOUD Platform (HCP) is the PaaS aspect of the SAP HANA Enterprise Cloud (HEC)"....Really?I? I thought HEC for the time being at least is (on-premise) "SAP Business Suite on HANA" hosted by SAP. And isn't therefore (yet) built on the HCP.
Well, if I did give impression that the Business Suite in HEC would leverage HCP at the moment then it wasn't by intention. You're absolutely right, this is not the case yet.
Please keep in mind that the vision of the overarching HEC is not limited to running the Business Suite and BW as a managed service, but is much broader. If you take a look at the first illustration in my blog you also see this bucket "Custom Apps | Big Data | Consumer". There's a variety of applications developed by SAP, partners and customers that are based on HCP already.
Aiaz mentioned a couple at the end of his blog:
So, yes... HCP is really (!!!) the PaaS aspect of HEC. Or in the words of Björn Goerke: