My Photo

My Online Status

Blog powered by TypePad
Member since 11/2005

July 2009

Sun Mon Tue Wed Thu Fri Sat
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

Sense

  • Google
Share |

14 July 2009

Microsoft Azure for Private Cloud: H1 2010

http://www.microsoft.com/virtualization/cloud-computing/privatecloud.mspx

  • The Microsoft Private Cloud enables:
  •  Management of the data-centre fabric as a single pool of resources
  •  Delivery of scalable applications and workloads
  •  Focus on the management of the data-centre service and it’s dependencies
  •  Federation of services across the full cloud continuum

Microsoft is enabling customers to build the foundation for a private cloud infrastructure using Windows Server and System Center family of products with the Dynamic Data Center Toolkit for Enterprises, availability scheduled in the first half of 2010.

The Dynamic Data Center Toolkit for Enterprises is a free, partner-extensible toolkit that will enable datacenters to dynamically pool, allocate, and manage resources to enable IT as a service.

  •          An architectural roadmap, deployment guidance, and best practices
  •          Familiar tools that are compatible with existing applications
  •          Interoperability with public clouds

With this new effort, Microsoft is keen to maintain a lead in “packaged” or “one-stop” PaaS Cloud Computing, opening the doors to small software companies to build tools(management, monitoring, custom solutions) to accompany the on-premises offerings from Microsoft.

 

-Charlton.

13 July 2009

NoSQL: leading Cloud's "NoBah" movement?

One of the remarkable aspects of the emergence of Cloud Computing has been the shift to addressing problems and providing solutions to them, from a focus on technology. The enterprise is still reeling from years of touting technology regardless of what problems needed to be solved. Whilst the industry loves to flog Microsoft, we need to point out other examples of this phenomenon, such as J2EE, which was sold as sledgehammer for every pin, tack, bracket, nail and spike - before innovators such as Rod Johnson started Spring, the MACR gang Flex/Apollo, and others Mule, Curl, etc. arrived to try to shift the balance back to sanity. The result has been a crimson tide of resources who were weaned on the coconut shies of J2EE, selling hammers for problems that couldn't any less be nails, and a current of architects/developers trying to solve real problems with Web/RIA and frameworks, whilst sorting out how to make any way against this tide. 

Cloud Computing has arrived, by virtue of 1) a lack of definition and standards, 2) riding on the coat-tails of Web and RIA, and 3) a backlash against the technology fun fair of the late 90s/early millenium, with a clear focus on solving real business problems. The drum beat of lower TCO/GreenIT has only grown louder with the development of the Cloud. Whilst technology purists may wince at the thought of something so "fluffy" having any real value, the evolution of Cloud from problem-solving, so-called "counter enteprise" (Web and REST, which position themselves as opposite to "enterprise software") movements is clear. These movements are very important, since, at a macro level, they are really pitched against the "every problem is a nail" set which "enterprise software" represents to them. 

These movements provided strong inputs into Cloud Computing, which has, if anything, positioned itself as a KISS approach to solving SMB (and by extension, enteprise) problems As Cloud has been somewhat challenging to pin down. it' has been targetted at scenarios (IT scalability, mobility, dynamic resourcing, adaptive) rather than technologies. Where as the "crimson tide" would attempt to sell you on something nonsensical as, "we're Cloud, just make your EJBs into Web Services," the Cloud and "counter enterprise" movements first ask, "what are you trying to solve?" and then sell their proposals. This focus on the problem/solution than hammer/nail has shifted SMBs and enterprises to a more comprehensive approach to service.

NoSQL is itself a remarkable proponent of this - by asking the question, "when do you *really* need a database?" There are enough scenarios where you do, and a growing number of scenarios where you don't. Flogging a database where you don't need one is madness, and by first asking the right questions as part of its fundamental value proposition, NoSQL may not replace the RDBMS, but is helping to replace an obsession with the latest vendors' offerings and hype with a better application of reason. In order to use specialised data sources, one needs to understand what they were designed to do. Likewise, RDBMSs are designed to model very highly and statically structured data which has been modeled with mathematical precision - data and designs that do not meet these criteria, such as data designed for direct human consumption, lose the advantages of the relational model, and results in poorer maintainability than with less stringent models.

NoSQL - and the problem-solution focus of it and Cloud as a whole - have come as a breath of fresh air, to me as I work to address problems at a strategic and architectural level, and to my colleagues as they work to implement solutions. Our ability to engage both these functions, without having technology shoved down our throats, leaves us free to develop the best and most appropriate solutions to real problems. I, for one, have encountered too many terrible architectures and designs which were driven by the need to adopt or pursue a particular technology. "Just make your EJB into a Web Service" as well as "you need a database" should send any reasonably intelligent architect and developer for the exits. Thus, I use the term "NoBah" - just as NoSQL seeks to challenge whether one needs a database, "NoBah" seeks to challenge whether every problem is a nail ("NoBah comes from the reaction I have to, "Bah, you can do that with Servlets/EJB/RDBMS/CORBA/DCE/EAI/COBOL"; you can likewise perform neurosurgery with a hammer, but it doesn't scale very well, or result in much success, does it?).





08 July 2009

Google Chrome, the next CloudOS

When Google introduced the Chrome browser, a broad discussion about it and about how it could be transformed in the OS of the cloud emerged. The biggest secret that everyone know was realised when Google introduced their plans for Google Chrome OS in their post on the Google Blog . Although based on Linux, it is really a greatly enhanced runtime environment that still abstracts away Traditional OSs. The highlights below talk about Google's consistent vision – the web is the platform . "Google Chrome OS is an open source, lightweight operating system that will initially be targeted at netbooks. Later this year we will open-source its code, and netbooks running Google Chrome OS will be available for consumers in the second half of 2010. Because we're already talking to partners about the project, and we'll soon be working with the open source community, we wanted to share our vision now so everyone understands what we are trying to achieve. Speed, simplicity and security are the key aspects of Google Chrome OS. We're designing the OS to be fast and lightweight, to start up and get you onto the web in a few seconds. The user interface is minimal to stay out of your way, and most of the user experience takes place on the web. And as we did for the Google Chrome browser, we are going back to the basics and completely redesigning the underlying security architecture of the OS so that users don't have to deal with viruses, malware and security updates. It should just work. Google Chrome OS will run on both x86 as well as ARM chips and we are working with multiple OEMs to bring a number of netbooks to market next year. The software architecture is simple — Google Chrome running within a new windowing system on top of a Linux kernel. For application developers, the web is the platform. All web-based applications will automatically work and new applications can be written using your favorite web technologies. And of course, these apps will run not only on Google Chrome OS, but on any standards-based browser on Windows, Mac and Linux thereby giving developers the largest user base of any platform. Google Chrome OS is a new project, separate from Android." I have before argued that the balanced compute model presents the greatest relevance to the user's daily work. This is precisely there where I think that products such as the Google Chrome OS will have a strong impact - not because they are rich or thin clients to access the Cloud, but because they enable the Cloud to actually work for users in a way that has real meaning to them. It's obvious that in a commercial perspective, a complete Could ecosystem is something in Google's interests - precisely why they need to be careful to maintain an open platform. In any case, this is no doubt a major step forward for the Cloud Computing paradigm.

01 July 2009

Will Cloud save the world?

Reading a generally insightful commentary in a post by Eric Knipp at Gartner: The Cloud Will Save The World, I started thinking more carefully about the value proposition of Cloud. In particular, I liked Knipp's statement that Cloud is not "an easy button - in the abstract. Someone, somewhere, has to do heavy lifting in any software development endeavor to build a high-quality, high-availability, highly-reusable Web architecture."

I couldn't agree more - security, audit, governance, certification, etcetera all represent considerable challenges in Cloud Computing. Yet,, "-- companies who learn how to screw down the cost drivers while simultaneously enhancing value drivers to satisfy customer needs have a competitive advantage in their industries." Indeed - satisfying customer requirements, and finding simplicity in complexity, are competitive advantages.

Nu, does this enable the Cloud to save the world? Knipp goes on to say "that as the world grows more complex, the only chance we have to head off the disintegration of modern society under the weight of complexity comes through technological leaps in the form of disruptive innovation. -- Could this new level of simplicity in complexity be the disruptive innovation that saves the world - or at least gives us a bit more time?"

I do believe the title does get a wee bit ahead of itself - Cloud Computing offers considerable opportunities for GreenIT and transforming both consumer and enterprise technology, but it is still a bit early to decide whether it will "save the world" or not. Yet, the sort of thinking that started the momentum of Cloud - and is verily needed to make Cloud succeed and fulfill its potental - is the same sort of thinking that is needed to conceive and execute on the broad transformations of which we are in dire need. Creative solutions almost always require a grim determination in the face of criticism and pedantry. Although it may not have come in time, Green tech is now recognised as a necessity. Likewise, Semantic Web, however the etymologists wish codify it, is now recognised as an enabler.. Cloud, and other movements, which drive this sort of creative, revolutionary-yet-evolutionary problem solving combined with the necessary persistence, will likewise have their day. 

28 June 2009

Why do cool kids write Ruby, PHP rather than Java?

Reading this article, I was inspired to articulate my thoughts on the topic. The short of it is that Ruby, PHP. JavaScript, and like languages address the desire for the right level of abstraction. Java, with all its innovation and genius, is still a compile-bound 3GL. It represented another realisation of the next step from C/C++ (as were Smalltalk, ObjectiveC) together the addition of standardised libraries. As it is, Java needs to perform some neat tricks to enable greater levels of abstraction.

Think about it this way: How quickly can one code and configure a data-driven Web application with Ruby, AIR/Flex, Silverlight/WPF, PHP or other next-gens? Now compare that to doing the same with Java. Although such inspired efforts as Spring have come a long way to narrowing this chasm, the precipices are still not close enough to encourage Java over these next-gens. 

The next-gens did something that Java once did, but stopped doing, when Sun decided to focus on it as a way to sell more Sun. They responded to the community - principally users (consumer & enterprise) and the developers striving to meet their needs. Java was simply stalled on the old-school concept that "If it is hard to build, it should be hard to use." On the other hand, the next-gens evolved from KISS concepts to fill this gap.

Although many development posts require knowledge of Java, this is more of an experience requirement than a practical matter. Should even the 'cool kids' be able to write a bubble sort or double-locking algorithm? Most definitely, they should. Will they be actually writing Java? More likely not, and why should they? If you can achieve far greater productivity with the next-gens, what is your motivation to use Java in development and production? (I challenge you to think hard about your assumptions w/r/t Java - the so-called stability 'gap' is not as far as you may have once thought, if it still exists)

I see the evolution and growth of the next-gens as a functio of their greater productivity, yet the prime factor is the community. Without the influence of the community, we would still be only talking about such next-gen languages, rather than writing web and cloud apps with them.  

Cloud as fulfillment of the Internet revolution

Recent discussions with Brian Madden and at CloudCamp, Structure09, and elsewhere this week started my thinking about the nature of Cloud. Rather than an euphemism of the Internet, I see Cloud as the next step of its fulfillment. The Internet has held the promise, if not necessarily the conscious intent, of any device, any where since its inception as ARPAnet. With every abstraction, Internet technologies have brought this promise closer to fruition. Only we technologists have been slow on the uptake to understand and realise the potential. Now, Cloud stands on the threshold of realising this across the plethora of connected devices in use. 

Recently, I argued that whilst the Internet itself has been a successful model, the curious Web 1.0 of star-architecture, J2EE-centric models to have hit its wall, run its course, seen its tail collapse. The Web communities as a whole are well aware of the spectacular FAILs of badly architected web applications, as is the Enterprise of the too little, too late of EJB and Servlets. Web applications' successes derived from the concurrent and thoughtful analysis, insight, and/or inspiration w/r/t scenarios *and* technology; at the same time, enterprise applications' (those which utilised internet architectures and technologies) successes were driven by the same, with the addition of the abstraction of resources. Only with the rise of RIA and Balanced Compute has there been a grand awakening amongst IT to the fit of Web 1.0 only to task worker and basic computing scenarios.

It is this combination that has inspired the latest evolution of Internet computing, the Cloud. The Cloud is more than hand-waving marketing smooth talk, more than co-location or hosting, more than the every present desire to reduce TCO. It is enabling any device, any where. Anyone in this industry would argue this as being the goal of compute models and architectures, and anyone with more than a couple years experience can attest to the mixed success/failure of technologies to make this a reality. 

Yet, what I recognise with the Cloud is a move to understand and solve a problem, rather than push a technology. This is where the current state of the Cloud, with the lack of solid standards at its level of abstraction, provides fertile ground. This is not to say standardisation is an impediment or negative. Rather, standardisation, just as with any other stage of compute maturity, has to be applied at the right time and place. Too early, and either the model/architecture/technology is not embraced, or technology is pushed as with the latest fashion without consideration for what problems are to be solved. J2EE, sadly, was one such victim. In the end, where it succeeded was largely, if not entirely, due to the inventiveness of IT (e.g. crafting their own abstractions to avoid the then high-latency, tightly-pinned EJB), and the development of models, architectures and technologies which came from outside the JCP process (e.g. Spring). Admist these successes have spectacular FAILs been observed, driven by the triumph of technological dogmatism (e.g. driving EJB when and where it clearly did not suit the task) over understanding and solving real problems. 

The Cloud is at a stage where the models and architectures are being subconsciously realised, whilst the technologies themselves are nowhere near standardisation. The vendors are pushing models in the vector of solving real problems, and pushing technologies only with respect to value add. To the untrained eye, this may seem to be more of the same sort of hype. However, what is remarkable is how Cloud has brought all the interested players to push scenarios and models/architectures rather than tout technologies. 

In a sense, we have Google to thank for this. Instead of speaking the babel tongue of operational semantics, and the ego-satisfying need to plough through gory details, Google 's desire to protect its IP has driven it to hide all that schmutz ;) behind abstractions. By hiding its value add, Google has encouraged its competitors to adopt the same focus. Whilst I see true Cloud success arriving with the fulmination of the Private Cloud, the Public Cloud-dominated bent has adjusted and encouraged our collective thinking in what I believe is and has always been the right direction. As such, I'll add that Cloud is any device, any where with the addition of abstraction; it is the next stage of the fulfillment of the Internet revolution, rather than an euphemism for the Internet. 

26 June 2009

Data Stores in the Cloud

The traditional ACID guarantees in databases have given way to newer approaches in the cloud emphasizing higher availability/scalability.

 

 

LWN has an article discussing alternatives to SQL databases: (Multiple extracts which have been reformatted for readability follows)

Cassandra is a data store written in Java that was open-sourced by Facebook and is now part of the Apache Incubator. Cassandra was originally designed to solve Facebook's in-box searching problem. Email reverse indexes were growing much faster than their databases could keep up with and they needed a affordable way to continue to grow.

Perhaps the simplest key-value store is Memcached. Memcached is widely used to to speed up web applications by caching dynamic content. Part or all of the web pages are served from the cache instead of generating them at each request. Unlike in-process or shared memory caches, Memcached listens on a network socket and can be shared by many servers. Memcached may also be run on multiple servers and it will spread the keys across those servers and transparently fall back to servers that are still available when one goes down.

For a key-value data store that won't throw out data, Tokyo Cabinet is a good choice. Like Berkeley DB, it uses either a hash table, B+ tree or a array of fixed-length records to store data on disk, but Tokyo Cabinet performs better and is thread safe. Tokyo Cabinet also promises to never corrupt data even in a "catastrophic situation". Tokyo Cabinet is actively maintained, and data stored is not limited by system RAM.

Redis is a disk-backed, in-memory key-value store with a number of additional features. Redis supports master-slave replication for redundancy, but not sharding, so all data must fit in a single system's RAM. Redis values may be binary strings, lists or sets. Redis provides atomic addition to/subtraction from integer values stored as decimal strings and push/pop/replacement of values in lists. The intersection of set values stored may also be calculated.

CouchDB is a JSON-based document database written in Erlang. CouchDB gives access to the database over HTTP with a RESTful API. Views of the database may be created on demand using Javascript to collect and filter document contents and are updated as documents change. Indexes are not maintained outside of views, so there is a start-up cost associated with constructing a new view.

MongoDB is a document database written in C++. MongoDB uses a binary-encoded JSON format that shrinks the data size and allows for faster searching and indexing. Large binary data, such as video files, can also be stored more efficiently in this format. Data is updated in place and MongoDB will automatically run a repair procedure on the database in the event of an unclean shutdown.

The new NoSQL community :) recently met - slides from their recent meeting go into details of a few alternatives:

Presentation slides and videos
Intro session - Todd Lipcon, Cloudera (slides, video1, video2)
Voldemort - Jay Kreps, Linkedin (slides, video1, video2)
Cassandra - Avinash Lakshman, Facebook (slides, video)
Dynomite - Cliff Moon, Powerset (slides, video)
HBase - Ryan Rawson, Stumbleupon (slides, video)
Hypertable - Doug Judd, Zvents (slides, video1, video2)
CouchDB - Chris Anderson, couch.io (slides, video1, video2)

VPork - Jon Travis, Springsource (slides, video)
MongoDb - Dwight Merriman, 10gen (slides, video)
Infinite Scalability - Jonas S Karlsson, Google (slides, video)

Additional Commentary: 

Is the Relational Database Doomed ?

Anti-RDBMS: A list of distributed key-value stores

The current database debate and graph databases

BASE: An Acid Alternative

Trading Consistency for Scalability in Distributed Architectures

25 June 2009

Never say "never"

Larry Ellison has exhibited a grudging about face regarding Cloud Computing. As the saying goes, "never say never". After touting the "network is the computer" together with Sun (before its time had come), Larry's distate for Cloud seemed odd, illogical. In light of the acquisition of Sun, Larry seems to be coming to grips with the lay of the land. Courtesy GIGAOM Newsletter:

Oracle CEO Larry Ellison is rethinking his earlier disdain for software as a service and all things cloud, according to a report today in The Wall Street Journal. Maybe a dismal economy and a drop in Oracle sales are forcing him to change his position. The Journal quotes comments made on Oracle’s earnings call yesterday, when Ellison was asked by analysts if the software company would embrace cloud computing. First off, software as a service isn’t cloud computing, but perhaps I’m being too picky here. Anyhow, Ellison said Oracle would be getting “a little bit” into cloud computing, according to the Journal.
But is this really a far cry from Ellison’s early mocking of cloud computing as being driven by whims of fashion? Ellison said he sees a gap in the market between true software as a service and providing on-demand software that’s hosted inside a customer’s own data center. That sounds like software as an appliance rather than anything on demand — and it’s something Oracle already offers through a partnership with Hewlett-Packard that puts its database software on a specialty server that customers pop into their own data centers. Oracle may also be selling some of its Fusion middleware products on demand, or as Ellison said, they could be “on-demand ready.” This is not a very convincing change in position for Oracle.
However, Oracle is buying Sun, and Sun had a true cloud computing strategy that involved building out infrastructure as a service for compute and storage. Maybe once that deal closes, we’ll see if Oracle wants to take cloud computing all the way up the stack.

24 June 2009

HTC takes Android, Flash to the next level with Sense and Hero

HTC announcing Sense and Hero, showcasing the next (available) generation of Android-powered devices, and making Flash on the MID a reality. From Engadget:


"With HTC's official launch event today, some details appear on HTC's own website of the much rumored Hero. Through some URL trickery, we've managed to unearth several details that confirm the previous rumors. Hero includes the new HTC Sense widget-based interface that puts at-a-glance info right up front on the home screen where it belongs. A new Scenes profile feature lets you transform your phones focus from business to weekend mode. Viewing your contacts shows the usual data in addition to the interactions you've had through social networking status updates and photos from the likes of Facebook, Flickr, YouTube, and Twitter. A dedicated search button searches the phone as well as services like Twitter. In fact, like Palm's Pre, the HTC Hero seems ready to fully integrate your local data with all your subscribed social media sites. The big unveiling is just about an hour away, until then, have a poke around HTC's Hero site yourself by hitting the read link below.

Update: First images are out! More after the break. Inside you'll find Qualcomm's MSM7200A proc running Android at 528MHz, 512MB/288MB ROM/RAM, 3.2-inch TFT-LCD with 320 x 480 pixel rez, 900/2100MHz HSPA and Quad-band GSM, trackball, GPS, 802.11b/g WiFi, 3.5mm audio jack, G-sensor, compass, and 5 megapixel auto-focus cam with microSD expansion. It's all there baby.

Update 2: A bit more detail just rolled in. The White version has an industry-first Teflon coating (right, just like your pans) to keep things clean and grime free. Multi-touch and anti-fingerprint coating too. Hero arrives in Europe in July with T-Mobile and Orange, Asia later in the summer, and North America even later in 2009.



23 June 2009

MIT Technology Review - Key Players in Cloud Computing

MIT Technology Review has published a series of Cloud Computing articles in the July/August issue - Jim Blakley has been listed as a key player and Intel has been named a key Public company to watch w/r/t Cloud. Also, Enomaly has been named a key Private company to watch in the space. 

To read the articles please see the following links:

» Technology Overview: Conjuring Clouds
» Industry Challenges: The Standards Question
» Market Watch: Virtual Computers, Real Money
» Companies to Watch Private, and Public
» Open Source Projects and Research Consortiums
» Key Players
» How it Works: Cloud Computing
» Webcast Interview with 10Gen CEO
» Case Study: Making Art Pay 
» Map: Water-Powered Computers

Congratulations to Jim, Intel and Enomaly!

MIT's 'House of Cloud':

House_p55_x600

LINKS

  • OnlyWire
  • Bloglines
  • Sound Copy
    say no to copyright extension
  • TwitterCounter
  • FOWD
  • LIFT
  • ZoomInfo
  • barCampLondon
  • FOAF
    my foaf data | about foaf
  • Technorati
    Add to Technorati Favorites