GitHub purchase by Microsoft

From my view, Microsoft bought GitHub for 2 major reasons – access and information. Access is the first reason and it enables an extension of their own tools and cloud. My assumption is GitHub will soon find the first option for tools and for cloud to be Microsoft’s unique line up. Why would a developer publish to AWS, Oracle, Google, or IBM if a single button press got you the latest features and tightest integration by going to Azure. They won’t eliminate or block the others, they’ll just make Microsoft the default.

I don’t think Microsoft is buying GitHub to bury it or ruin it. Microsoft is not exactly the biggest promotor of open source, but they are an active player. This is not like Gillette buying the stainless steel razor blade patent so they could drag their feet on producing one and get more money out of their existing products. If Microsoft blocked GitHub, I think the world would just develop an alt-GitHub or shift to competitor.

The second is probably the more important: information. GitHub is where developers, programmers, and coders dream. They put snippets of code which are glimmers of the future. Simply understanding what libraries, language, databases, tools, and clouds are being used, frequency, and in what combinations will yield bright headlights into the near future. If you release a new library, you can now easily see its uptake in the community. Put more money into it if it’s yours, alter yours to look more like the winner, partner where you can’t win, or buy it up if it’s a good investment.

As long as Microsoft uses a respectful hand and doesn’t become the evil overlord, I think the purchase of GitHub will yield a bounty of information by which they can steer their own development of tools and products. For a company that has jumped in late on the Internet, Open Software, and Cloud, they sure do an impressive about faces.

 

Advertisements

Production HANA on VMware – for the few, for now

Production HANA on VMware is in “controlled availability, allowing selected customers, depending on their scenarios and system sizes to go live with SAP HANA on VMware vSphere immediately” per SAP OSS Note: 1788665 – SAP HANA Support for VMware vSphere Environments.  However, the SAP marketing team left this small stipulation off the press release and got everyone very hot and bothered.

It sounds like everyone should be able to put their HANA system on VMware.  First, my wife, who is not in the IT world, sent me a link to the NY Times SAP and VMware Head for the Future Together and then I got about dozen copies of the Market Watch Report: SAP and VMware Announce SAP HANA® for Production Use on VMware vSphere 5.5.  Well, at least that mentioned you needed the latest version of VMware.

So for now, if you want to production HANA on VMware, the main requirements are below and included in SAP OSS Note: 1788665 – SAP HANA Support for VMware vSphere Environments.

  • Must be approved for controlled availability by SAP
  • Must be on VMware vSphere 5.5
  • Must be on SAP HANA SPS07
  • Maximum of 1 TB
  • Must be on SAP approved HANA server and storage
  • Must comply to SAP’s current recommendations for vCPU and RAM
  • Must not over-provsion the CPU nor RAM
  • Maximum of 1 Virtual Machine (VM)

In other words you need the latest and greatest version of VMware and HANA running on your HANA approved appliance in a nearly non-virtual manner.  While this is less than what we all want, it is a step in the right direction.  It will allow you to manage the HANA instance under your VMware management utilities.  It makes HANA part of your Software Defined Environmental strategy.  I’m confident that over time, as it becomes Generally Available, that production HANA will have far fewer restrictions.

I’m actually looking forward to when we can run production HANA on lots of virtualization schemes.  I look forward to more of software defined service level agreement (SLA) with SAP so that other virtualization environments including the cloud providers can provide production services. Right now it is about shipping hardware to Waldorf, DE for certification and is so specific, it is not practical even for hardware manufactures.

SAP needs to move to software defined SLA would be good for everyone including SAP by making HANA more available and take less effort to certify platforms, hardware and cloud providers who want the ability to vary the make-up of servers based on market conditions and newer evolutions of chipsets, and especially my clients who want HANA, but in but running in a completely virtual word they are defining, not the one SAP is trying to define for them.

As Vishal Sikka (former SAP CTO) exits, limited Production HANA on VMware is great first step for the product he called his child, HANA. Unlimited production HANA on VMware would be a great toddler-hood.  I really look forward to seeing it rapidly reach its teenage years and start trying to run on everything everywhere.  Isn’t that what teenagers do?

 

SAP HANA MCOD – What I really want for my data center

The real SAP game changer will be when I have one (1) HANA DB for all my production applications.  I want single, giant in-memory DB where my ECC, BW, CRM, PLM, SCM, BOBJ, etc. all consume the same data.  I want a row  view for the OLTP ECC-like applications and column view for OLAP BW-like applications.  It would look like the picture below.

sap hana mcod system
What we really need from SAP! The SAP HANA MCOD system.

Right now, I can’t really recommend using HANA on anything but OLAP based applications.  In the future, when we can do the analytic transformations in memory without silly exports, extractors, DSO’s and the like, we will really have a very* different scenario.  For now, the cost of the HANA license and risk of losing transactions only committed to memory is not justifiable.

In this new vision with MCOD, there will be two (2) key issues.  First, how do we support MCOD.  I’ve seen MCOD come and go since 1993 several times. Each time, it was easy to build and impossible to support.  The overlapping requirements became overwhelming. Second, HANA will need a data aging architecture which can age data out of main memory to some slightly slower memory or device.

IBM is working on some important technology, Phase Change Memory, that will be of great value (http://www.zurich.ibm.com/sto/memory/).   It may provide the near DRAM speeds while being cost effective and non-volatile.  Maybe IBM will build out series of servers specifically designed to run in-memory databases such as HANA with massive DRAM and massive PCM capacities.  PCM could then provide the roll-back logs and more at near DRAM speeds. PCM won’t solve the MCOD and data aging problems, but at least the risk of running rapidly transacting OLTP systems would go to near zero and certainly lower than that of even today’s highly cached disk writing databases.

It is going to be a fun watching HANA make it from infancy to toddler-hood.  I wonder how fast she’ll mature.

* Mark Twain said every time a writer was tempted to use “very” in a sentence, they should use the word “damn” and then the editor would strike the word and the sentence would read as it should.

 

When will Sybase ASE be FREE for all SAP system users

I am surprised SAP has not announced that the standard database from the Sybase acquisition is free to all SAP system users.  I will even be more surprised if they do not make the announcement at Sapphire 2012.

Why would SAP give away Sybase ASE?  They could make some amount of revenue by selling it, but by giving it away they improve the ROI of the migration.  Migration costs are the biggest barrier to any DB or OS change under an SAP system.  In addition, they take away the 20% maintenance and enhancement (M&E) fees their number #1 competitor, Oracle, is gaining from every SAP system running on Oracle.  I wonder how much of the reported $12B Oracle reported of support revenue in 3rd quarter is driven by SAP systems running on Oracle RDBMS.  That is potentially billions of dollars that Oracle does not have to attack SAP, develop new applications, or build a cloud business.  Oracle’s M&E, like everyone in the software business, is a substantial part of the revenue and more importantly profit stream of the business.

In addition, SAP can optimize the ASE database for SAP.  In fact they could make all other vendors’ database versions a port.  The best and brightest capabilities would be in found in the latest release of ASE coupled to SAP.  In addition, they can up sell Sybase Replication Services (SRS) as an Extract, Translate, and Load (ETL) engine, Disaster Recovery (DR) solution, and high availability (HA) solution.  They also can  up sell to HANA for higher performance.

Pushing out ASE will cost something.  SAP will have to support, develop, and move ASE forward.  They should have those resources from the acquisition and from previous DB efforts like mySQL.  Most of that cost is already accounted for excluding the go forward actions to stay on par with other major DB vendors in the SAP world; however, Sybase is are major player in the financials arena today, too.

SAP is going to break some glass with the big database providers, Oracle, Microsoft, and IBM.  While I’m sure they don’t care about Oracle’s opinion, they are strongly partnered with Microsoft and IBM.  It may be taken very poorly by IBM and Microsoft; however, I’m not sure either of them can let go of all the other areas they are linked into SAP especially IBM who has the world’s best (my opinion and Forrester’s) largest SAP practices.

HANA may be getting all the headlines, but the world is not done with RDBMS.  There is still a need.  There are still companies making lots of money, especially Oracle, on RDBMS software.  When is SAP going to give its clients something FREE to smile about and at the same time take so much away from their biggest competitor, Oracle.  Seems like a win-win for SAP and its clients.