One of the defining characteristics of this age is the notion of a technological singularity. Whether or not our civilization actually achieves such an event, there is surely little doubt that we are currently experiencing a period of time marked by incredibly rapid discovery and innovation. For some time I've been a fan of Ray Kurzweil, first for the musical instruments he makes, and secondly for his writing on futuristic themes. So I'm very excited to be attending The Singularity Summit at the end of October, an event at which I hope to meet some like-minded folks, and hopefully sharpen my vision with respect to what may come...
Friday, September 26, 2008
Tuesday, September 23, 2008
I finally got around to playing with Amazon's EC2 yesterday, just going through the basic tutorial. Pretty much as I expected, it was trivial to create and start a new instance, although I could see getting tired of keeping track of the access identifiers for command line usage and wanting to find a GUI such as RightScale, which will even automatically launch new instances to deal with increases in demand on your site.
The idea of being able to quickly add extra compute power, and only pay for it when you need it is quite appealing. Many web sites experience significant peaks in their business and could potentially save on infrastructure costs with such a model. For example, at my last gig we designed systems that had to deal with peak traffic that was more than twenty times the average for just a couple hours at a time, requiring a significant investment in hardware that went largely unused most of the time. It's also nice for companies just starting out that don't have a firm grasp on their hardware requirements yet.
I do wonder how well Microsoft can play in this new space given their server-centric licensing model. If I want to have a hundred servers on standby, how would I license Windows for that? Some quick Google searching for "windows cloud computing" turns up some information on a future cloud-centric operating system called "Midori", a beta offering of Microsoft Online Services, and even references to Windows Live. But this wouldn't help me deploy a .NET application to the cloud today. This fairly recent post on ZDNet echoes my confusion, and adds even more concepts. Red Dog? Microsoft appears to be playing catch up again with respect to understanding the Internet.
Regardless, I want to start taking advantage of cloud computing. Even if it's not yet ready for mission-critical applications, one could start by moving certain workloads into the cloud, such as load testing or compute-intensive batch processing. I don't know of any other way I could start up a server or two and play with them for an hour for just $0.25.
Monday, September 01, 2008
This week I'll be attending the Business of Software conference in Boston, where folks are getting together to discuss all the gnarly difficulties associated with building software for money. Judging from the presentation topics people are worried about how to build software, how to market it and how to charge for it. Clearly these are all very worthwhile topics. I guess for myself, however, these are the least of my worries. I classify them as rational problems. You can try things, see what works and what doesn't, experiment, and move on. Easy.
But patents. Patents lurk around late at night, watching and waiting, ready to strike at the worst possible time. Patents are not rational. They're a problem I clearly don't understand. Richard Stallman himself will be speaking at BoS 2008, mostly on the evils of patents as applied to software. I'm already convinced of the evils, what I need now is a strategy to manage patent risk!