A couple of days after suggesting that Sun should offer cloud services they announced that they would be supporting Amazon EC2 by having it run Sun’s OpenSolaris and offer MySQL support for instances running on top of EC2. Nice, but not any where near what I’m hoping for. So I started looking at the other side of the coin, what things are keeping Sun from being able to offer pay as you go consumer services? One thing quickly came to mind: dealing with many payment transactions, often for small amounts.

The beauty of pay as you go cloud services is that you pay for what you use. If you only use a small amount, you only pay a small amount. My S3 bill each month rarely goes over $5, because I only use it in small amounts. Amazon charges my credit card and sends me an email with the details. But for most companies doing lots of credit card transactions for small amounts simply isn’t worth it. The fees associated with credit card transactions add up fast when dealing with such small transactions. At least for most companies.

Amazon has been doing large volumes of credit card transactions for a number of years, I’d be very surprised if they don’t have some custom fee structure for processing them. When you do the volume of transactions that a company like Amazon does, that gives you a little more leverage. So part of what has allowed Amazon to grow into the pay as go cloud services market is the fact that they already had a large payment system in place that allows them to process even fairly small transactions efficiently.

This gives Google Checkout an even more important role than just being a competitor to PayPal. With AdWords and AdSense already going, Google already has plenty of reason to want the same sort of leverage Amazon has for processing payments. With Google App Engine expected to have a similar pay as go structure as AWS, there will be even more focus on processing small amounts without taking a big hit on fees.

Now back to Sun. As far as I know Sun has nothing that even comes close to Amazon’s volume of transactions or Google’s small fee services. So they’ve had no reason to build up an efficient payment system that can handle small amounts. This leaves them with two choices, build one to try and gain the needed leverage to reduce the fees involved, or partner with someone else who already has. So far they’ve gone with the later, specifically Amazon and their EC2 service.

One way around the small transaction amount problem is to have customers pay in advance. Sun could still offer pay as you go services, but you have pay for them upfront in $100 increments. Each month your usage fee would be deducted from the amount you already paid them. If I only used $10 this month, I’d still have $90 left in my account. This isn’t nearly as attractive from the small customer side as simply paying $10 per month from their credit card, but not horrendous either, especially if you could get the minimum pay in advance amount down to something under $50.

I’d really like to see more competition in the cloud services space, but so far Amazon has it pretty much all to itself (which a small niche potentially going to Google App Engine). And unless companies like Sun can find ways to process small payments efficiently we might not be seeing any for a long time to come.

6

Google App Engine

Posted on April 8th, 2008 / 6 Comments »
Tags: , , , , , ,

Today’s big news was the announcement of Google App Engine. Plenty of people have been covering the details, I just wanted to leave a few thoughts:

This looks like an amazing service. Being able to make use of Google infrastructure for your web app is a wonderful idea. Currently limited to Python, so all the Python fans are going nuts.

What Google App Engine (GAE) isn’t is a direct competitor to Amazon’s web services (EC2, S3, etc). What Amazon provides are virtualized services, what GAE provides is a specific platform. While that platform is pretty amazing, it is also complete and total vendor lock in. If you needed to move your application off of GAE, how would you do it? This might give pause to those interested in buying your startup.

There’s an SDK for starting your app before going live, but no way to migrate data from your test system to the live server. I imagine as people begin to use this new platform they’ll find other issues as well. That isn’t to say that GAE isn’t worth while, just that it isn’t a miracle cure.

0

Links for Fri 14 Dec 2007

Posted on December 14th, 2007 / No Comments »
Tags: , , ,
1

Links for Wed 7 Nov 2007

Posted on November 7th, 2007 / 1 Comment »
Tags: , , , , , , , , , , , ,
0

Mac Backup To Dreamhost

Posted on April 2nd, 2007 / No Comments »
Tags: , , , , ,

When I posted a brief comparison to Amazon S3 and Dreamhost one thing I didn’t do was suggest how one could actually use Dreamhost in a similar way as S3, like backups. For S3 Jungle Disk is one option for backups. Now there is a how to on backing up your Mac to Dreamhost (part 2).

Another approach would involve using MacFUSE with the ssh module. Have I mentioned how much I’d like to see Apple include MacFUSE in OS X by default? Well, I would, a lot.

What this approach doesn’t do that Jungle Disk does is encrypt the files on your remote backup. But on the other hand S3 has a file size limit of 5GB, as long as it isn’t between 2GB and 4GB. So really S3 on supports files sizes from 1-2GB and 4-5GB. Each method has pros and cons.

2

Amazon Elastic Compute Cloud (Amazon EC2)

Posted on August 24th, 2006 / 2 Comments »
Tags: , , ,

I’m starting to wonder if someone over at Amazon really does have a master plan to take over the world. Today they announced the Amazon Elastic Compute Cloud (Amazon EC2). EC2 allows you to have a “virtual computer” hosted at Amazon which is roughly equivalent to a “1.7Ghz Xeon CPU, 1.75GB of RAM, 160GB of local disk, and 250Mb/s of network bandwidth”. Pricing $0.10/hour, $0.20/GB of Internet traffic and $0.15/GB/month of S3 storage used. Running a system 24×7 would set you back $72/month plus S3 storage costs.

The folks who thought S3 wouldn’t change things, may start changing mind now. Amazon has a ton of information up on this new service: Developer Tools, WDSL, Forum, FAQ and a Getting started guide.

Right now they only support Linux based systems, but hopefully we’ll see that expand. I’m voting for FreeBSD support! Amazon is using XEN to virtualize these systems, so hoping for FreeBSD support seems reasonable.

I’m on the waiting list for next beta round, I look forward to trying this out. Expect to hear more about this.

Ads