Structures of control are spontaneously generated in every environment and every wave of computing.
Today on the web we have a model where browsers are the single point of control for much of what happens, not just at the level of applications, but at the meta-application level as well. Not simply usage (“point-click-type”), but things about usage – who is the user (browser cookie), what are they using the app through (user agent), where did they come from (referrer), what can we infer about their behavioral state, and so on – as well as modifications of usage (browser add-ins, content...
Mary Meeker’s Web 2.0 presentation made a strong case for the imminent boom on the mobile internet. Some statistics that caught my attention:
· Mobile internet users will exceed 500M human beings in early 2010
· The mobile consumer device market will exceed 10B in the next 5 years
· The current iPhone + iTouch user base is larger than Netscape’s base in 1999
· More than 20% of the world will be on 3G networks by the close of 2010
This is a serious change in how people are using the Internet. ...
In enterprise computing, scale has traditionally meant “lots of transactions per second." On Wall Street for many years, “20,000 TPS” was the magic number as it was the rate of a typical market data feed. Infrastructure like TIBCO’s UDP-based information bus and then IBM’s MQSeries became the base platforms for much of this scale of computing, and are still heavily used alongside modern JMS and MSMQ implementations.
Relatively little attention was paid to concurrent connections. Enterprise environments tend to be well-regulated, and most applications will have...
This article by Lori MacVittie of F5 makes some good points that whoever becomes the de facto API in cloud infrastructure might win - and goes as far to say that the API replaces the CLI.
Generally agree but might take it a step further.
Just as we drove a 'de facto' standard CLI at Cisco, de facto standard "infrastructure APIs" likely will emerge. (Already seeing this happening with the AWS API)
But APIs represent a significant evolution. Why? CLI commands and output are unstructured. API commands and output are...
Great to see an API showcased as the heart of an industry leader's core business strategy - and called out as such in the top business newspaper.
Paypal is executing an indirect strategy by opening their core services via APIs in order to have their payment capabilities more easily consumed in other applications and services.
Ten years ago, you could read articles like this about companies launching their websites to execute a *direct* business strategy… selling...
Open source has a role in all types of computing.
It has always reduced barriers to entry to a particular platform or programming model.
But in cloud computing open source plays a new role - driving the rate of evolution of the infrastructure to match pace with the rate of evolution of an early market.
Open Source in Cloud Platforms
Open source platforms like Xen, OpenNebula, and Eucalyptus enable universities and early-stage adopters to deploy the core platforms without financial risk. No up-front commitment in a cash-poor environment like the...
Last time I wrote about the difference between'open' vs. 'free' APIs.
Another interesting dimension is free vs. paid.
Free vs. Paid has to do with the business model of your service. If you have a service that’s valuable/revenue-generating to the user (unlike advertising/reach, which is valuable to *you*) then you might choose to ask to be paid - through a credit card, licensing or BD deal. (we've written before on the many API monetization models and resulting API roadmap and technology implications.)
While I hate the term "freemium" (more on...