As I mentioned in a recent blog about the In-memory Computing Conference 2012 (IMCC 2012) event, I found the presentation from Xiaoqun Clever (Corporate Officer, SAP AG Senior Vice President, TIP Design & New Applications, President of SAP Labs China) entitled “Extreme Applications – neuartige Lösungen mit der SAP In-memory Technologie“ interesting but didn’t go into details. In this blog, I wanted to describe what I found so interesting about the presentation.
The first slide that I found intriguing was the one that describes the various scenarios for HANA. You can visualize the evolution of Hana over time as moving from left to right: Accelerator -> Database -> Platform. The first thing that I noticed is that “Cloud” is not involved at all. Indeed, it is only mentioned in a single slide later in the presentation - it almost doesn’t appear to play a major role in such HANA-related endeavors.
The use case with HANA as a Database and the involvement of NetWeaver components would also cover the current intentions regarding the NetWeaver Cloud offering where HANA will be present as one possible data source. In this area, I will be curious to see what sort of functionality overlap (user management, etc) will exist between the HANA Platform and the NetWeaver Cloud as well as how the two environments will integrate with one another.
A later slide describing the scenario “HANA als Platform” is actually titled “Native HANA Applikationen”. The applications listed on the slide are either OnPremise or OnDemand (usually associated with the HANA AppCloud) applications. I started to consider what the portrayal of these applications as being “native” meant for the relationship between HANA and the Cloud. To be truthful, I’m starting to get the impression that we are slowly seeing a merging of the OnPremise and OnDemand worlds in terms of HANA runtime environments. Native applications might be able to run in both worlds since the underlying platform is fundamentally the same. Thus, other considerations (costs involved, customer presence, etc) might be important in making decisions regarding where such applications are hosted.
If we take this assumption forward a few years, you might think that a HANA-Platform-based Business Suite running as a native HANA application (and thus, perhaps easily available in an OnDemand setting) might be an option but another slide in the same presentation shows that a HANA-based Business Suite would be distinct from native HANA Apps.
What I liked about the presentation is that it reinforced my understanding of the differences between scenarios involving NetWeaver functionality and those based on native HANA functionality. What I don’t fully understand is the potential use of native functionality in scenarios where NetWeaver functionality (for example, NetWeaver Cloud) is used. Is this possible? Planned? As things evolve, I’ll waiting to see if the scenarios with HANA as a Database can hold their own against HANA as a Platform scenarios.