// archives

cloud

This tag is associated with 12 posts

OblakSoft Cloud Storage Engine Newsletter, March 2013

ClouSE 1.0b.1.7 is released

OblakSoft is pleased to announce the release of Cloud Storage Engine (ClouSE) for MySQL Beta version 1.0b.1.7.  In this release we added support for a variety of environments to address the platform diversity of our growing customer base.

Here is the summary of changes that are included into 1.0b.1.7:
(more…)

WordPress on S3: going pro

WordPress-on-S3 makes professional website administration as easy as pie.

OblakSoft is pleased to announce availability of the ready-to-run WordPress-on-S3 / Yapixx AMI with enhanced configuration, performance, and website administration features.  Now website owners can use Webmin and phpMyAdmin for secure website administration over the Internet, and pre-configure Cloud Storage Connection for the instance.

(more…)

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:
(more…)

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?

(more…)

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

(more…)

WordPress on S3: the beauty of simplicity

My first computer program was written almost quarter a century ago on a BK-0010 computer.  It was very simple: the program asked the user to enter their name and then greeted the user using the entered name, like “Hello, Artem!”.  I was fascinated.  A couple of lines written in Vilnius BASIC transformed a piece of metal and silicon into a considerate thing that cared about a person’s name enough to remember it :-).  Of course, the first experience doesn’t represent the day-to-day routine of software development, but the moments when I see a couple of lines making an amazing transformation still enchant me, and remind me why I’ve been writing code all this time.

I’ve just experienced this very same first-time feeling as we’ve released Yapixx – a picture sharing web application using the cloud storage.   The most amazing thing about Yapixx is that we wrote very little code to make it happen: most of its functionality is provided by WordPress, which by the way we didn’t modify at all. 

On one hand Yapixx is just WordPress, enhanced with plugins and configured to provide good picture sharing experience. 

On the other hand, Yapixx has gone where WordPress could not go before – Yapixx runs completely on top of Amazon S3, using the enormous power of S3 to make serving the users’ pictures highly scalable and storing all data extremely durable. 
(more…)

“WordPress on Amazon S3″, OblakSoft Cloud Storage Newsletter, May 2012

WordPress on S3: run a beautiful website on Amazon S3 cloud storage

OblakSoft is proud to introduce the 1st ever dynamic WordPress site running on top of Amazon S3: Yapixx.  Now you too can launch your own beautiful website on Amazon S3.

While Yapixx stands for Yet Another Picture Sharing Site, it is actually one of a kind.  Yapixx is WordPress that was moved to run on top of Amazon S3 storage without changing a line of code in the WordPress core engine.

(more…)

WordPress on S3: how it works

OblakSoft is pleased to showcase how simple it is to run LAMP applications on the cloud storage.  OblakSoft configured the WordPress web publishing platform to run on Amazon S3 storage and made the recipe available for anyone to replicate.  A ready-to-run WordPress site (configured as Yapixx) – is available for public use for FREE.  Yapixx is WordPress configured as a picture sharing website that runs on top of Amazon S3 (Yapixx stands for Yet Another Picture Sharing Site).

(more…)

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…)

@Database Innovation, pleeease!

My response to Database Innovation, pleeease!

Sure :-) We’ve just recently released a Beta of ClouSE — the Cloud Storage Engine for MySQL that provides fully functional relational data management on top of Amazon S3.

Even though we still use the good ol’ B-trees (sorry), dealing with remote eventually consistent elastic storage provided plenty of innovation opportunities. We had to rework the ARIES algorithms that don’t really account for pages being physically deleted (traditionally they just go to a free list so the storage never shrinks); neither do they account for eventual consistency – to implement ACID the whole storage engine stack from buffer manager, to log manager, to transaction manager, to access methods had to go beyond gradpa’s algorithms and protocols.
(more…)

Categories

Twitting ...