This Beats Everything: Koding in the Cloud

OK, now this beats everything I’ve seen so far. I can now code in the cloud with Koding.com. From a first, very quick glance, I get:

  • A VM with a terminal (looks like a Debian distribution)
  • PHP and all sorts of stuff that is already installed
  • An app store for apps like PostgreSQL or MySQL
  • 1.2 GB of free disk space and 2 GB of RAM

Wow. Coding in the cloud. Sounds awesome. What’s next!? And who are they? See the Koding, Inc. blog for their press release about opening up their services to the public:
http://blog.koding.com/2013/08/koding-is-public

VM with a terminal on Koding

VM with a terminal on Koding

Cloud Fever now also at Sybase

After SQL Server (SQL Azure) and MySQL (Google Cloud SQL), there is now also a SQL Anywhere database available in the cloud:

http://www.sybase.ch/fujibeta

It’s called Sybase SQL Anywhere OnDemand or code name Fuji. I guess the connotation is that your data might as well be relocated to Fuji. Or your DBA might as well work from Fuji. Who knows ;-)

I don’t know where to start adding integration tests for jOOQ with all those cloud-based SQL solutions. Anyway, exciting times are coming!

Google Cloud SQL, the next step for jOOQ?

“The Cloud” is probably the biggest IT buzzword in 2011. It may as well be as meaningless and as short-lived as its predecessors “web 2.0” and “dotcom”, but clearly, the big companies are aiming for “The Cloud” right now. After Microsoft’s all-out marketing campaign for Windows Azure and its sub-product SQL Azure, there is now a comparable Google offensive on Google Labs:

http://code.google.com/apis/sql/docs/developers_guide_java.html

OK, marketing-wise, the term “offensive” is way over the top: Google Labs products often look quite geeky and by far less professional than those by Microsoft. But the approach is interesting, especially the choice of using MySQL as a SQL platform in the cloud. NoSQL was a response to traditional SQL’s inability to scale horizontally. If you buy a big box for your Oracle database, you’ll add memory and CPU power to make it scale vertically as your application grows. You’ll fine-tune your SQL, preferably with jOOQ ;-), to prevent performance bottlenecks in single queries. You’ll pay expensive DBA’s for the job.

When SQL goes to the cloud, however, horizontal scaling might become more realistic… I’m very curious to see where this goes. Clearly, jOOQ should be one of the first Java database abstraction tools to fully support Google Cloud SQL as well as SQL Azure.