26-Sep Updated table formatting
"If I have seen a little further it is by standing on the shoulders of Giants" Isaac Newton 1676*
"If I have seen a little further it is by standing on the shoulders of Giants"
Isaac Newton 1676*
As a Developer Evangelist, I'm often talking about the value of "the Platform" and sometimes it takes a little while for people to see that value. I like to tell a story about the evolution of a platform
One of the questions I often get asked is whether abstracting away the details of the working of the platform makes us less connected from the source and therefore somehow less capable. There's no requirement to not understand how the platform works (just like, as a Civil Engineer, I understand water supply systems pretty well), but equally, there's no requirement to rebuild the platform every time you want to build something on top of it. Whether I'm installing an espresso machine or a hydroponics farm, I can use the water supply platform without having to drill a well, install a reverse-osmosis plant, install solar panels for power and so on.
This also makes a distinction between platform and services. Pat Helland pioneered the concept of a metropolis where he described the various utilities (water supply, sewerage, electricity, roads, railway lines, ports, telecommunications infrastructure etc) as services (I haven't done Pat's work any justice at all here - go and read his paper). I'd argue that these are actually the platform on which services (schools, high-speed internet access, parcel delivery, banking, petrol stations etc) can be built. In a similar way, in the Software plus Services story both the software and the services are built on a platform (or platforms). The more common functionality the platform provides, the more time service providers can spend on the provision of the actual service. For example, pretty much every provider of any significant services in the cloud needs to have a way to authenticate and bill (or otherwise gain benefit from) users of the service. There aren't that many schemes for doing either of these things and so it makes sense to have the platform (on which the service is built) provide this functionality. By factoring out commodity platform capabilities (i.e. billing, provisioning, SLA monitoring and management, auth[n|r], messaging, CRM, monetization services etc.), the service provider is free to invest fully in an offering in their domain of expertise, without being encumbered by having to build out these concerns. Customers are also free to pick and choose those services that make the most sense, again without having to build out (and care and feed for) commodity capability.
This has the related effect that the costs of these cross-cutting platform capabilities – which cost a lot to develop and maintain – can be amortised against a much larger population of users. In turn, this tends to bring the cost of the services down, which makes them more accessible to smaller organisations (i.e. further along the tail). This is a democratising effect - i.e. now a small software firm can afford an enterprise-grade provisioning, billing and SLA management engine, and can scale this according to their needs, and therefore potentially compete with larger players, or offer lower-cost services to customers who are also further along the tail.
Time to value is shorter. If a service provider can focus on their offering sans the surrounding infrastructure, they can deliver services much more quickly, and can respond to opportunities in the market more rapidly. Related to this is the expectation that markets and offerings will evolve much more quickly than ever before. If you aren’t tied down by infrastructural drag, you can innovate much more quickly.
Many thanks to Nigel Watson for his insight and additional thoughts.
* Yes, I'm aware that Isaac probably wasn't the first person to use this phrase, but he's probably the most famous** OK, OK, the picture's obviously not from 150 years ago (of course, the first one is from 10,000 years ago), but I really wanted a picture of this pump - it's because of my background in GIS
PingBack from http://www.artofbam.com/wordpress/?p=2680
A book I was reading recently claimed that the reason Newton said that was to cover the fact that the work he'd described at the time was somewhat "leveraged". Nonetheless, it was a really memorable statement and describes so much about the whole scientific process.
I saw your keynote on this topic at the Open Spatial User Forum recently, both my colleague and I commented about how well (especially in terms that us GISers can understand!) you explained the concept of platform evolution.
I think that you & I might be reading the same books :).
The phrase does sum up the scientific process rather well, but it also sums up more generally the value of building on the work of others.
Thanks for your kind words - I really enjoyed doing the keynote at the Open Spatial User Forum. As I think I said at the time, I felt a bit like I was coming home.
I've always felt that GIS is in many ways the cannonical platform on which great services can be provided, so it was a particularly appropriate forum for telling this story.
Great analogy Andrew.
The Broad St pump article was very interesting too.
I love the Broad Street Pump story. It's a great example of cross-discipline thinking, something that we should all be concentrating on.
I LOVE O v3! As part of my demos for Graham Seach's Office DevCon , I've developed a VSTO v3 Outlook
Yeah, I know I'm about 3 months late with this, but I'm coming out of the tunnel (between here and here
Anyone who's been to any of my recent presentations knows that I'm a passionate advocate of developing
One of the common questions I get asked when I do sessions on VSTO / OBA development is "how can
After chatting with a few people about Visual Studio Tools for Office (VSTO) recently, it’s clear that the technology is not that well understood (even though, in my opinion, Microsoft have done a pretty good job of articulating it – much better than
I was chatting to some community folk in the pub last night after presenting (on Architectural patterns