// archives


This tag is associated with 18 posts

Amazon S3: no outage

When I talk to prospective customers about the Cloud Storage Engine for MySQL (ClouSE) the question of cloud reliability often comes up, especially recently in the light of the outages in AWS.

Cloud outages lead to a lot of publicity.  Cloud opponents jump in with “that’s why I haven’t moved to the cloud and never will”, cloud proponents rebut with “N rules for building highly available applications for the cloud”, cloud competitors call on customers to move to their cloud.  But it’s important to look into details, because not all outages are created equal.

Here is the data I found on the AWS outages in the last couple of years:

MySQL on S3: performance with storage located across the continent

Can OLTP database workloads use Amazon S3 as primary storage? Now they can, thanks to the Cloud Storage Engine (ClouSE), but the question is: how fast?


OblakSoft Cloud Storage Engine Newsletter, June 2012

ClouSE version 1.0b.1.2 and WordPress on S3 / Yapixx refresh is released

OblakSoft is pleased to announce the release of ClouSE version 1.0b.1.2 and WordPress on S3 / Yapixx refresh.

This release addresses performances and usability issues reported by our early adopters.  Thank you all for your feedback.

  • Support for MySQL 5.5.25

Now ClouSE supports MySQL thru 5.5.25.  To keep the distribution small, we don’t build binaries for MySQL prior to 5.5.14 anymore.  If you need one, please contact us.

  • Weblob content type improvement

Now the content type for Weblobs is set based on their name.  Previously, the content type for all Weblobs was set to application/octet-stream, which could lead to undesirable Web Browser behavior when the Weblob was downloaded from Amazon S3 directly.  For example, an image file could be downloaded to disk instead of showing in the browser.

  • “WordPress on S3” changes


Cloud Database Comparison

I went to a GSLUG meeting last Sat and gave a talk about ClouSE. The slides are mostly the same as here, with the addition of the cloud database technologies comparison chart:


OblakSoft Cloud Storage Newsletter, March 2012

ClouSE version 1.0b.1.0 released

OblakSoft is pleased to announce the release of ClouSE version 1.0b.1.0. This release addresses reliability and performance issues that were encountered by our early adopters, as well as it provides new functionality to better align with real life usage scenarios.

  • The weblob URLs now support user-defined file names.
  • The weblobs now has to be of the LONGBLOB type.
  • The AUTO_INCREMENT fields have now have semantics that is similar to InnoDB’s “interleaved” lock mode.

Thank you all for your feedback! (more…)

Slides for my presentation @Seattle MySQL meetup, on Feb 6, 2012

The slides have notes, they are a little hard to discover with the SlideShare interface, look for a tab below the slide that looks like "Notes on Slide X".

OblakSoft Cloud Storage Newsletter, January 2012

OblakSoft is ready to fly!

ClouSE v1.0 Beta is now available for public use

ClouSE is the Cloud Storage Engine for MySQL that can utilize cloud storage such as Amazon S3 to store user data. ClouSE provides transactional and ACID-compliant relational data management on top of cloud storage.

Databases powered by ClouSE enjoy all the benefits of cloud storage – scaling cost with usage, high storage availability and reliability, quick and easy disaster recovery, etc.  ClouSE can provide direct cloud storage URLs so content can be served directly from cloud storage relying on its enormous power to make serving the content highly scalable.

OblakSoft CEO – 1st blog: Happy Old New Year !

When I was a little boy, I thought the Old New Year (Jan 14) was the day when the New Year becomes “old”, becomes the current year, the thing of the present.  To the mind of a little systemic thinker it made perfect sense – if there was not a date when the New Year stopped being new, how would we be able to celebrate the New Year that comes after it?

Later I learned that the Old New Year was just Jan 1, but by the Julian calendar.  So in a sense the reason for this informal holiday is that little details of the relationship between the Earth and the Sun were ignored and it led to a growing gap between the tropical year and the calendar that tried to express it.

At OblakSoft we have other things to celebrate besides the Old New Year.  We started a new company and launched a public Beta of our first product: ClouSE – the Cloud Storage Engine.  At a high level, though, the problems that ClouSE is trying to address in Cloud Computing  are somewhat similar to the ones the Gregorian calendar has solved in date counting: to take into account little details of the relationship between the cloud provider and the cloud consumer and to close the gap between the cloud computing promise and cloud computing reality.


Twitting ...