GroupHelp.NET - Easy everything!

For obvious reasons, we care about what goes on in various parts of the world, particularly New Zealand and other areas that are underserved in terms of Internet access.

So, we were quite excited to learn this evening of a new proposal that would give New Zealanders - including a couple RWW staff members - a better broadband experience. According to NZ website Stuff, a haldful of well-known innovators and entrepreneurs are teaming up on a $900 million dollar project that would give Kiwis (and their Ozzie neighbors) "virtually unlimited" broadband access via an international cable that would run across the Pacific Ocean. Just how much of a difference would this cable make compared to current Internet access?

Sponsor

The difference would be significant, as Stuff's graphic shows:

The plan is to construct a 5.12 Terabits per second-capacity fiber cable to connect Australia and New Zealandto the U.S. - a cable that would deliver data at five times the speed of the current network.

This proposal puts Warehouse founder Stephen Tindall, TradeMe creator Sam Morgan, entrepreneur Rod Drury, and techies Mark Rushworth, John Humphrey and Lance Wiggs in competition head-to-head with Southern Cross Cable, a large network partially owned by Telecom New Zealand. The team, called Pacific Fibre, hopes to complete the project by 2013.

Of course, the next step is figuring out the exact cost of the proposed cable - the group thinks $900M might be a highball figure - and find investors. However, as Tindall eloquently noted, you have to spend money to make money - something anyone with an interest in NZ's economic future and global competitiveness must consider.

"The New Zealand Institute identified billions of dollars in economic potential by unleashing the Internet," he said, "and it is beyond time to address the issue. This is necessary and basic infrastructure - we must decrease the distance between New Zealand and the international markets.

"Doing so will be incredibly valuable for New Zealand and Australian businesses and consumers. If we are able to deliver on this cable this it could be as valuable to our NZ economy as the quantum leap refrigerated ships were to our export trade many years ago."

How feasible do you think this project will be? Is 2013 a realistic time table? And where do you think Pacific Fibre's investors will be found? Let us know your opinions in the comments.

As the cloud is getting more players and interfaces, best and worst practices are emerging. As the market grows and more companies try to plug in, the cloud may benefit from guiding principles.

Similar to new technology movements in the past, a natural process is underway to define "what is good", which, for some in the industry, equates to "what is open". Like religion itself, open can be defined in ways that are uplifting, or on the other side of the coin, restricting. Also, we learn again, nothing is free.

Sponsor

Cloud APIs Must Walk on Water

If you've been part of a software development project, you know that sometimes it's hard to get the team to all agree on best practices for interface design, database optimization, or even what technology to use. In this analysis, we take a look at some of the movements in cloud computing that start to lay a framework of good as it relates to this technology.

In this context, API designers for cloud applications need to think ahead and avoid common pitfalls. For several reasons, more than ever before. First, because many people will be accessing your one piece of code. Second, is that in this world of open APIs, it's easy to compare your code against another.

We notice that data management practices are at the core, and details matter when provisioning in platforms. At the same time that groups are forming to align practices and forms of virtualization and cloud standards, a voice whispers that perhaps this is a free-market problem. People who benefit at solving it, will; others will ignore it or compete directly. We enjoyed this post from Joyent on where standards matter in a practical sense.

In essence, the question raised: If a vendor makes it easy and bakes in the ability to "just do it", do you know or care about the standards? This seems to mirror an iPhone development paradigm, which is to expect work from the vendor SDK or libraries. The SDK wraps standards implementations, which is done in the way best understood by that vendor.

Do Unto Others as You Would Have Done To You

We know the cloud is big - perhaps it will inevitably be bigger than the Internet itself as it usurps our conception of location, space and time.

Where power forms, rules, groups, and organizations do as well. In information technology there is always tension between open standards and defacto standards. The former are crafted through agreements, the latter through leadership and market dominance.

We asked in a prior series "Will a single company become the dominant provider in the cloud?" Today we look at the more practical side of "who is winning now" - who is setting the rules and who is in the trenches.

Quite a number of the responses to our earlier posts emphasized that "the cloud should be free", meaning that it should have governing principles to avoid one vendor from owning the landscape.

Here are a few groups that have emerged to provide some context in how this may come together, both philosophically and practically. In both, the devil is in the details. A good summary of some of the current combining of forces is by the Open Grid Forum. (In our opinion, grids have given way to clouds as the dominant concept in this technology makeover).

• A resource directory of initiatives is located at the Cloud Standards Wiki, which in itself was formed by a handful of organizations and movements working to align around setting rules and patterns for cloud computing.
• The Open Cloud Consortium is organized around developing practices around sharing resources and has recently focused on a developing a test bed.
• The DMTF is working at the core definition of virtualization. It recently focused on the 1.1 version of the Open Virtualization Format (OVF) specification that focuses on packaging virtualization instances and creating a portable mechanic distribution by defining envelope and collection parameters around the virtual machine and its services. The organization, which contains members of IBM, Microsoft, Dell, VMware, XENSource, Sun, and NEC, has submitted 1.1 for consideration as an ANSI and ISO standard.
• The efforts by the federal government in its data.gov initiative shows that there's a market that's starting to see the value of raw government data formats. Soon, we would expect this to be powered by a mesh of computer resources that allow all sorts of jobs - integrated jobs - to work with these data sets. It would comprise an active government cloud.

Do Not Covet Thy Neighbors Network Resource

When looking for things to avoid, we found a lot of philosophical questions around data ownership, logging and portability. These discussions are alive and well and seem to be being absorbed into vendor solutions and consortiums like the ones mentioned earlier.

For a more practical view, we turned to a friend of ReadWriteWeb, Thorsten von Eicken, and have summarized his thoughts from a recent post, "Top Cloud API Sins. Bold items are our (loose) mapping to biblical terms.

• Do not covet your neighbors resources.: Listing of resources without the details, e.g., a list-servers call that doesn't return all the details for each server. This makes it very expensive to poll for server state changes ...


• Do not make cast idols: Not returning a resource id on creation. Some APIs don't give you a server i.d. when you request a server...


• Labor six days, rest on the seventh: Providing a task queue. Several APIs I've seen have a task queue that is supposed to provide updates on tasks that are in progress E.g., you launch a server and you get a handle onto a task descriptor. For us that's just overhead...


• Though shall not bear false witness: Not returning deleted resources in a "list resource" call. In particular, terminated servers must be returned in a list servers call for a certain duration, probably at least for an hour. Ouch!...


• Shall not covet his neighbor (or force me to repaginate): Pagination that goes page-wise instead of using a marker, e.g. where you get page one or the first 100 resources and then issue a query for "page 2? or "from 100 on". Explain to me how a client can get a consistent resource listing when resources can be added and removed concurrently...


• Randy Bias added to Torsten's post: Treat others as you want to be treated Your UI MUST use your API so you understand how to be a consumer of your own API...

We plan on keeping up with this list and seeing how it intersects with implementations and standards that evolve.

Nirvana: Smells Like Services Orientation

Torsten goes on to describe a picture of the future. "Now here's what I'd really like to see. This is what we're working on for internal purposes and it's not easy, which is an event based interface instead of a request-reply based interface... "

Smart services in the cloud, rather than resources alone. This starts to get us closer and closer to an object-orientated network. Maybe that's what the cloud will be for platforms, infrastructure and software. The industry has been quick to identify the layers. But perhaps the point is piecing them together in a smart transactional framework.

A way to engineer highly reliable systems around these architecture challenges may sound familiar to those who monitor existing data centers today.

Torsten continues, "We run a good number of machines that do nothing but chew up 100% cpu polling EC2 to detect changes. Fortunately cpu cycles are cheap :-)".

This is practical intervention between vision and get it done.

We find it refreshing to hear this type of dialog in the industry and see a fresh opportunity for defining efficient patterns for this next generation of the cloud infrastructure.

Perhaps a new concept is forming: "Divine Computing".

What buying decisions will be based on the openness of cloud resources and common APIs?

Photo credit: tsarkasim, Amsterdam Esogna

Google just launched a new Google Labs product for Google Reader: Google Reader Play. Reader Play is a new, highly visual way to browse your Google Reader subscriptions that is somewhat reminiscent of Google's Fast Flip. It replaces the busy Google Reader interface with an interface that focuses on a single story. Whenever a post includes videos or images, Play with highlight these and give you the option to read more of the text as well. This new interface allows you to browse through the feeds you already subscribe to, but Google Reader Play also emphasizes Google Reader's ability to recommend items from around the web for you based on your preferences.

Sponsor

Big on Recommendations

As Google notes, Play will learn from your preferences, based on the articles you read and "like." You can also choose from a set of categories (tech, entertainment, arts, business, etc.) and Google Reader will create a personalized stream of items just for you. According to Google, Play uses the same algorithm as the Recommended Items feed in Google Reader.

Play will even work if you don't have a Google account. While you can't star, like or share items, you can still browse interesting posts based on the categories you choose. This should make it a good tool for those users who don't want to go through the effort of setting up a feed reader and subscribing to hundreds of different feeds.

Get Started

To use Google Reader Play, just head over here or look for "View in Reader Play" in the folder settings in Google Reader. You can switch stories by using your arrow keys or choose the slideshow mode that will automatically forward to the next story after a few second.

As many in the Twitterverse have dubbed this week, the battle of location based apps continues, as both Gowalla and Foursquare release yet another update to their iPhone apps today. And these are some big guns coming out to accompany the various real-life incentives, contests and whatever else these the two companies can do to take the focus at this year's SXSW.

Both apps are showcasing new design features the companies are calling "fresh" and other such things, and while they surely are, some of these other features are what really stand out.

Sponsor

Foursquare is surely the less notable in this release, in our opinion, as it's list of new features is shorter and less impressive. It's boasting a faster, more efficient check-in and shout flow, a "Places" view that supports categories, a history view of places you've been and a "pull-to-refresh" feature. These are nothing to sneeze at, but we think Gowalla is releasing some functions that blow these away.

First of all, Gowalla is bringing photos to the location based game, allowing users to upload a photo after checking in. Users can also browse their friends' photos and look at any that have been taken at that specific location.

Next, it's bringing some interactivity to the game, with check-in commenting. When a friend checks in at a place down the street, you don't need to change over to your Twitter client and send them a DM, you can just comment on their check-in. And if you forgot to type a check-in message when you checked in to a spot, you can go back and add it.

In addition to these, Gowalla is bringing out new friend browsing features, enabling you to look through friends, friends of friends, and even their bookmarked spots and trips. With "spot details", including address, phone, Twitter name, Facebook page and website, Gowalla is adding that Yelp (or should I say Foursquare) aspect that was really missing - real world connection information.

And one more feature that may be overloaded next week or may be the talk of the town, "Hot Spots", tells you what the most popular spots near your location are. We haven't had time to really play with it yet, but it sure sounds interesting.

The updates just popped up in the App Store right now so go get updated and let us know what you think - who is going to win the location based battle of SXSW 2010? As far as this round goes, we're calling it for Gowalla.