When Google App Engine was announced one of the features that was heavily pushed was it’s ability to scale. Combined with Amazon’s AWS products, I’ve been thinking about other companies who could/should be in the cloud services business. There’s the obvious ones that everyone talks about like Microsoft and Yahoo, but then another name came to mind: Sun.

What service should Sun offer to the world? I’ll give you a hint, they recently spent $1 billion dollars acquiring the company behind the product. Yep, none other than MySQL.

Love it or hate it, MySQL is widely used by many companies and individuals. What I’d like to see from Sun is a MySQL cloud service that works just like your current MySQL server(s), only better. It should scale such that I don’t have to worry about performance and replicate data sufficiently that I’ll always have access to my data. There’s no need for a new API, since MySQL already supports network connectivity.

With MySQL already in such wide spread use, the benefits would be easy to see. For instance, I could use such a service to power my WordPress blog with only a few changes to my wp-config.php file. Effectively requiring zero code changes.

Pricing wise I’d expect something similar to EC2 or S3, a general pay as you go schedule. Perhaps even with a very low use free option, just enough for people to get hooked. But if I were Jonathan Schwartz I wouldn’t stop there.

As nice as it is to have an easy to use pay as you go web service, there are many companies that would like the performance, scalability and reliability of such a service but don’t want to send all their data to Sun. Enter Sun’s Modular Datacenter, a.k.a. data center in a box. Okay, a very big box, but a box none the less. Take all the lessons they learn making the MySQL cloud service work and put them in the data center box and sell it.

This would also appeal to hosting companies, who could then offer the same sort of service to the users. Imagine some place like The Planet having a few of these in their data centers. They’d get the benefits of the cloud service without having to haul all that traffic over their Internet connections.

In my ideal world this wouldn’t be limited to MySQL. I’d love to see this same sort of thing for PostgreSQL, since Sun has also been pushing PostgreSQL for Solaris as well. Sadly I’m not holding my breath on that one. With PostgreSQL being a much more community based project, there’s nothing to stop some other company from providing this service.

Perhaps Sun should have changed their stock ticker to MYSQ instead of JAVA.

0

Links for Tue 5 Feb 2008

Posted on February 5th, 2008 / No Comments »
Tags: , , , , , , ,
1

Sun Buys MySQL

Posted on January 16th, 2008 / 1 Comment »
Tags: , , ,

The big news today is that Sun purchased MySQL: Sun Press Kit, Sun Announcement, MySQL Announcement and Jonathan Schwartz’s Blog Announcement.

Let’s get the obvious issues/questions out of the way first. The purchase price is $1 billion, $800 million cash, $200 million in options. What is this going to mean for Sun’s PostgreSQL development? How will this impact the relationship between Sun and Oracle? Historically Sun has been one of the big iron Oracle platforms. Oracle owns a vital piece of MySQL, InnoDB. And of course, what will this mean to the MySQL community?

Now some of my own thoughts on this deal. This seems like something of a desperate move for both companies. In the case of MySQL, they need to find a way to stay intact as a company and bring in lots of cash. Guess all that talk of an IPO goes out the window now. So the list of potential buyers becomes pretty small. It would have to be to a company with lots of hard core tech but without a major database platform of their own, which rules out Oracle, IBM and Microsoft. Google and Yahoo might have smart folks who could make it better, but getting into the customer support business isn’t something that they’d want to do. So how many other big tech companies are left that would be willing or able to pay the kind of money that MySQL was looking for? Like I said, small list.

Then there is the Sun side of this deal. Recently Sun has been pushing PostgreSQL, but there isn’t one single company behind PostgreSQL, making it much more difficult to control in the manner that Sun prefers. In this respect MySQL fits perfectly, although it is Open Source (mostly), there really isn’t much of a developer community for it. Basically all development happens at MySQL the company. This would allow Sun to have the same massive grip over development that it has had for its other open source products. I think another factor is that Sun desperately wants to avoid becoming ignored in the world of big name web companies. They’ve developed some great stuff (Dtrace, ZFS) and even open sourced their OS (Solaris), but have still have failed to get their foot in the door in any big way for tech startups. So if you can’t convince them to like you, buy someone they already do. And better to do it now while you still have the money to do so.

Sun has just bought their way into becoming every tech company’s best friend. Maybe now they’ll change their stock ticker symbol from JAVA to MYSQL.

0

Links for Wed 12 Dec 2007

Posted on December 12th, 2007 / No Comments »
Tags: , , , ,
0

Links for Wed 12 Dec 2007

Posted on December 12th, 2007 / No Comments »
Tags: , , , ,
0

Links for Tue 11 Dec 2007

Posted on December 11th, 2007 / No Comments »
Tags: ,
0

Links for Fri 7 Dec 2007

Posted on December 7th, 2007 / No Comments »
Tags: ,
2

Kris Kennaway on FreeBSD 7

Posted on November 21st, 2007 / 2 Comments »
Tags: , , ,

Last month Kris Kennaway spoke about FreeBSD 7 (pdf). Lots of details about how FreeBSD 7 came about and what you can expect to see when 7.0 finally gets released.

Perhaps the most interesting part though was the SMP focused case study involving MySQL and PostgreSQL on pages 10 through 19. The numbers for 7.0 compared to previous versions of FreeBSD on transactions per second on multi-CPU systems is really impressive. The ULE scheduler gives a huge boost over the traditional 4BSD scheduler. Looks like ULE will become the default scheduler sometime during the 7.x life time (7.1 perhaps?). You want to see CPUs really put to use? Check out page 13.

I was rather surprised to see the MySQL numbers come in so much lower than the PostgreSQL numbers. There seems to be a MySQL specific problem that limits how well it can scale across multiple CPUs.

0

PostgreSQL Projects at Skype

Posted on March 15th, 2007 / No Comments »
Tags: ,

Skype has been PostgreSQL as their back end database and have made available their database projects as part of the Skype Developer Zone. For background how Skype has made us of PostgreSQL check out the whitepaper.

Skype has made the following projects available:

  • PL/Proxy
  • SkyTools (made up of Londiste, PgQ and WalMgr)
  • PgBouncer
  • Enhancements to PL/Python that are part of PostgreSQL 8.2

Nice to see Skype giving back to the PostgreSQL community.

0

Implementing a Queue in SQL

Posted on January 12th, 2007 / No Comments »
Tags: , ,

Greg’s Implementing a queue in SQL (Postgres version) is an interesting exercise. The goal was to implement a simple queue that can be managed via SQL. The example is a simple first in, first out (FIFO) queue, with a limit of 5 items.

Two methods are demonstrated to accomplish this, the first one makes use of the PostgreSQL Rules and is very short. The second one is a little bit longer and uses a PL/pgSQL function as a trigger. One advantage of the second method is that it lets you know how many rows in your queue were recycled. Both methods require only one table.

There’s also a queue in MySQL article as well.

Is it practical to implement FIFO queues in a DBMS? Maybe not, but it is a good example of thinking outside the box.

Mangus Hagander has a detailed how to for replicating from MS SQL Server to PostgreSQL. It certainly isn’t perfect, but for those willing to go through the work this would be a very interesting way to add PostgreSQL to a SQL Server shop. I don’t plan on using this right now, but I’m definitely going to file this away as something with potential.

Ads