Monday, September 13, 2010

Founding SkySQL

To be part of the MySQL journey was a great privilege in my life. Working for almost six years with great developers, energetic sales-guys, devoted support engineers and a management team capable of executing remarkable growth while driving good team spirit was a huge personal experience. I am grateful for the valuable learnings I got over the years from some of the best in the industry: The technical geniuses behind the technology and open source strategy, my fellow management colleagues, the top leadership (above all MÃ¥rten Mickos) which was impressive, and last but not least all the co-workers many of which became good personal friends over the years.

It was a sad day, when I about two years ago decided to leave the company. However, I noticed that after MySQL AB was integrated into a very large company, the flexible, effective and unproblematic culture that originally inspired me in the fast-moving MySQL AB was gradually disappearing.

This development can hardly be criticised; it was to be expected. New growing businesses inevitably go through a painful transformation when maturing to be integrated into mainstream corporations, many times their size.

Yet, it was simply not for me.

Being part of the MySQL AB success story made me realize that start up business was what really inspired me, and thus I decided to focus on working with start ups after leaving the company. I went forward to create a new VC operation together with 3 other partners, Open Ocean Capital, which manages funds collected from investors in Europe. For two years, we have now helped startups with cool products build communities and grow their businesses in a disruptive way.

After the first year at Open Ocean, I felt MySQL was something I had now left behind me. My focus was completely on building other new businesses.

However, in our VC practice, we naturally track the industry very closely, and gradually it became obvious that MySQL was not just an experience that helped me grow other businesses: the MySQL technology itself got further traction, leading me to believe that the peak of the MySQL impact is still to come. With the huge growth of online devices, and with the cloud and SaaS simply exploding, it has become evident that MySQL as the leading online database technology still has a lot of growth to go for.

This situation lead to a development during the last six month, where gravitation simply brought equal minds together. One day we noticed we had six key individuals around the table who were strongly involved in MySQL AB, and who all felt that the glory days of the MySQL technology is still in front of us.

At the end of June 2010 SkySQL was born. The purpose of the company is simple:
  • Serve customers with what they want around MySQL and its derivatives.
  • Reassemble much of the core team behind MySQL AB, that has reached out to us. We want to provide a superior service, and have the best skills that exist around the product directly available to the customer, and through us customers can be certain to receive the best technology to meet their needs.
  • Re-create the warm, flexible, effective and forward-looking culture we all remember from the good old MySQL AB years.
  • Naturally also learn from the past: improve some processes and add new, attractive business opportunities.
  • Be a technology and service provider, whose strategic interest entirely focuses on making the MySQL technology strive everywhere, for all customers, long term.
Some parties have already confronted us with the question, how we see the competitive landscape. Here my view is positive and simple:
  • We want to make the customers happy. Hence, we regard very positively all the companies, organisations and individuals who work to develop the open source MySQL technology forward to help customers. We are willing to enter into close partnership with those who advance the technology.
  • In some parts of the market, there is a competitive situation when others would like to serve the same customer we want to. In such situations, it is normal healthy competition that plays. The customer is free to choose, and we naturally hope they will see the benefits in choosing us, and we will do our utmost to keep them very satisfied. Secondly, we do foresee that we can play the leading vendor in certain market segments, simply because these are not the focus area of other vendors. Also, we see that gradually over the future years, we will move our products into other directions than other vendors, giving us a technology/service advantage in certain, even new, markets.
  • Finally, we see very strongly that we want to be a good member of the community and ecosystem. We will thus always view other vendors with the highest of respect. Of course, at many of the key players we still have a lot of friends, who we will continue to see as friends, despite the fact that perhaps in some sales situations we might both want to win the deal. But this is just normal business, and should never be mixed with emotions.
Another question presented to us by many is what our relationship is to Michael "Monty" Widenius and his company Monty Program. To ease some curiosity, let me explain the situation.
  • Monty Program will be a close business partner with SkySQL, and provide deepest-level engineering backing to the MySQL part of SkySQL's product offering, and provide SkySQL with access to top development talent on the product.
  • However, both companies are completely separate and have different owners and goals.
    • a) Monty and his company are focusing on future community development of MariaDB. The company is practically owned by the personnel, and has the goal of i) being a great place for engineers to work, ii) ensuring long term survival of the MySQL technology in the world, and iii) not be driven by outside investors, but share profits to personnel and not to owners. (BTW: number iii is the main reason why Open Ocean is not an investor in MP).
    • b) SkySQL Corporation Ab is a commercial, for-profit company. It focuses on serving customers with MySQL and MySQL-related products and services, to enable the customers to be successful in using the products in all their needs, at affordable cost, long term. As indicated by "MySQL-related" we plan to expand both the technology (through own development and through partners) and the service offering beyond what MySQL AB did, in line with how the industry and customer needs have developed and are expected to develop.
  • Monty himself has no active role in SkySQL. Yet, as a close partner through Monty Program, he is logically very supportive of our operation.
Now, the work begins.

We have some very hectic days in the months to come, to get everything ready to launch, and to then start entering the market with a strong presence. But the train is moving, and very soon you can expect to hear more about us.

On a final entertaining note, we chose on purpose to select a name which preserves part of our joint heritage. With SkySQL you are absolutely free to decide for yourself, if you pronounce it Sky - ess - que - ell, as Nordics do, or Sky - see - quell.


(To receive future information about SkySQL, we welcome you into our LinkedIn group.)

Wednesday, April 16, 2008

A fantastic day of Connector releases!

Georg and his MySQL Connectors Team today surprised the MySQL Community and most of his Sun-MySQL colleagues by releasing a "Full House" of Connector releases.


The ODBC 5.1 GA marks a very important milestone for the MySQL Connectors team. ODBC is one of our most popular drivers, yet it is a driver we historically have had problems supporting well. To correct the situation, much of the team has for over a year focused on this new version. A lot of hard work and sleepless nights have been spent while pushing towards this day. A Big Thank You goes to the core team behind it and all the supporters within the MySQL organization.
  • Core Team: Georg Richter, Jim Winstead, Jess Balint, Lawrenty Novitsky, Eric Malossi
  • Supporters: Kent Boortz (Build), Bogdan Degtyariov and Tonci Grgin (Support), and MC Brown (Docs)

The ODBC 5.1 is based on the ODBC 3.51 code, so much of the improvement work around ODBC has naturally covered this earlier version as well. I believe we have fixed close to 200-300 bugs in the 3.51 code alone in the last 15 months. We hope we now offer two solid ODBC products which matches the high quality expectations of our users and customers.

The PDO and Connector/OpenOffice.org previews are two new initiatives within the Connectors team. We recognize that part of the PHP community is interested in the benefits of PDO and naturally we want to support them well. We can thank Johannes Schlueter and Andrey Hristov for the coding work and Ulf Wendel for his vigorous testing activity in making this PDO preview happen. The OpenOffice.org support is an exciting initiative within Sun to make it easy to access MySQL Server and its schemata from the office-suite. This is an example of great cross-departmental engineering co-operation between MySQLers and other parts of Sun. Greetings to the OpenOffice.org team in Hamburg who helped us in this work!

Finally I want to highlight the great work by Reggie Burnett. Reggie is our key driver ensuring that MySQL supports well the Microsoft development community, and thanks to him MySQL is very easy to use over .Net and from Microsoft Visual Studio. Thank you for yet another Connector/.Net update that keeps the quality of this important support high.

Tuesday, April 15, 2008

Workbench 5.0 is GA!

I am very excited about the Workbench 5.0 GA release today, the ultimate Database Modeling Tool for MySQL Developers.


Mike calling to get Workbench GA online.
(about 15 min before Marten's UC keynote starts)

The team has worked extremely hard for the last months, eagerly awaiting this day. Congratulations to Mike Zinner, Alfredo Kojima, Vladimir Kolesnikov, Mike Lischke, Johannes Taxacher, Sergei Tkachenko and Maksym Yehorov for making this happen.

We invite all in the community to try out the product and provide us with feedback.


  • Maybe there is some specific functionality you miss in the product? We invite all our users to enhance the product and build plugins. Guidelines for how easy this is to do, you find on http://dev.mysql.com/workbench/?page_id=10

  • If you want to get access to some time-saving additional features, we offer the Workbench Standard Edition (soon available for a low cost on shop.mysql.com)

Now after the GA release we will first take a moment to celebrate! (and sleep). Thereafter we will start to plan for the next Workbench 5.1 update, which we intend to release still this calendar year. As the planning is still not finalized, we invite your input on what you think we should focus on. Together we can ensure we build the best modeling tool for you.

Post your thoughts and comments for the team in the Workbench forum.

Friday, March 14, 2008

Time to Contribute? - MySQL Community Development Program has been updated

 
MySQL geeks worldwide unite!
 
I am proud to announce that Georg Richter (our Community Engineering Lead) has updated the MySQL Community Development Program.
 
 
The updated program gives explicit suggestions for items you can work on, if you want to help out yourself and/or MySQL in development. 
 
We have published a list of Development Worklogs (read: design outlines) and Bugs which we are very interested in getting help with. If you let us know your interest in coding one of the items, we can assign a MySQL developer to guide you in your work. 
 
The intent of this assistance is to help you develop good code for MySQL. We hope this makes your end result function well, and makes it possible to merge your code easily with other MySQL code.
 
The list has been chosen by taking Worklogs for features we would like to include in the next development release, but for which we can't allocate resources currently. They are also of a suitable difficulty level so that we believe an external contributor can succeed in the implementation. 
 
The chosen Bugs are of lower priority which we currently can't allocate a developer on, but which we think can be relevant for a fair amount of users. We also regard them to be of lower to intermediate complexity.
 
We welcome your feedback to the updated program!