InSync09, AIA, Oracle-Sun Deal and MySQL

Posted in: MySQL, Technical Track

I enjoyed InSync09 conference and the networking opportunities there — great place to meet bunch of good old friends and make some new ones. The content of the presentations and direction where Oracle is going to provided some interesting food for thoughts on Oracle’s strategy and how it’s going to make money with all those acquisitions they’ve done recently including current Oracle-Sun deal.

My take now is that Oracle’s focus is integration of all those products. It’s absolutely clear that Oracle won’t be able to merge so many different product lines together. It’s difficult and time consuming task and customers often suffer during this transition process. Oracle does not want its customer suffer — it’s the best way to shrink their customer base.

What Oracle intends to do now is to keep all those new acquired products, continue development while work heavily on integration solutions. Integration products and services is where Oracle will find its new direct revenue stream. If Oracle integration initiative works well over the next years, Oracle customers using one or few Oracle products will naturally look to extend into other Oracle products because it’s easier to integrate within existing business solutions and processes.

Businesses need efficient solutions implemented quickly these day. Companies are moving very fast and if you missed the time spot, the opportunity is gone. It’s not a problem to find a product to suite your needs — there are plenty on the market. However, nobody has the luxury of having enough time to integrate new products and services in their existing business so a vendor with fastest implementation time-frames is the king on the market.

Watch this space — Oracle Application Integration Architecture. Everybody keeps talking about SOA (Service Oriented Architecture) these days. Some find it uber-attractive and is the way of the future. Others are skeptical and proclaim that adoption can be messy and brutal. While both have some valid points, it looks like those of us who find the fastest way to integrate solutions together will be the winners. If SOA adoption requires years and there is a quicker solution available for comparable cost then SOA will most likely loose. The question is, is there another way?

Now, what about this Oracle-Sun deal that everyone is talking about? Well, looking in the past, it does look like Sun failed to make money on a number of great technologies and products such as Solaris and Java. Why is another story — there were great deal of speculations from people who must know it much better than me. My conclusion is that IBM is a great money making machine while Sun is the technology making machine.

What about Oracle? Well, I think that so far they have excelled in both – money making and technology making. Isn’t that a wonderful combination?

When Sun bought MySQL AB a year ago I was really puzzled how they (Sun) were intended to get those money back — MySQL revenue was order of magnitude lower compare to what Sun paid and, knowing Sun’s history of making money on great technologies, I couldn’t see that revenue exploding in the near term.

Will Oracle be able to explode the revenue stream from MySQL? No doubt they are positioned very well for that and database technologies have been Oracle’s bread and butter. Furthermore, pushing on integration, Oracle will have serious advantage over any other software (and now hardware) vendor as well as great revenue stream.

So does Oracle want to kill MySQL technology? Absolutely not! The more technologies and solutions Oracle supports, the broader market of integration initiatives and the more money Oracle can make.

What does it mean for Pythian? Well, I can’t stop smiling as I write this especially after the announcement about Sun/MySQL remote DBA program with Pythian being the founding partner. Coming from Oracle background, I’m more and more involved with MySQL technology these days. Many of you are using MySQL monitoring plug-in for Oracle Enterprise Manager that I authored and Pythian released it with Oracle’s blessing and certification. Pythian has achieved lots of efficiencies for customers supporting the *right* database technology and the fact that MySQL is now falling into Oracle hands completely, is going to strengthen our positions in both Oracle and MySQL services.

Still have doubts about Oracle’s direction with MySQL? Just look at the MySQL 5.4 release and what it’s main improvements are — it’s what Oracle has excelled at with their mainstream RDBMS — deliver features customers require the most!

Want to talk with an expert? Schedule a call with our team to get the conversation started.

About the Author

What does it take to be chief technology officer at a company of technology experts? Experience. Imagination. Passion. Alex Gorbachev has all three. He’s played a key role in taking the company global, having set up Pythian’s Asia Pacific operations. Today, the CTO office is an incubator of new services and technologies – a mini-startup inside Pythian. Most recently, Alex built a Big Data Engineering services team and established a Data Science practice. Highly sought after for his deep expertise and interest in emerging trends, Alex routinely speaks at industry events as a member of the OakTable.

3 Comments. Leave new

Oracle Exadata v2 — No “HP” Prefix? | Pythian Group Blog
September 10, 2009 11:28 am

[…] you, I don’t have any confirmed insider information so it’s based on some assumptions, my perspective on Oracle-Sun acquisition and some vibes I can feel in the […]


Most of the InnoDB changes in 5.4 have been made redundant by the latest InnoDB plugins. But it is great to see InnoDB/Oracle and MySQL work hard to make InnoDB scale.

Larry Ellison to Announce OLTP Database Machine on… Sun Hardware | Pythian Group Blog
September 13, 2009 6:42 am

[…] will excuse myself for self-quoting from half a year ago: … it does look like Sun failed to make money on a number of great technologies and products […]


Leave a Reply

Your email address will not be published. Required fields are marked *