In April 2011 during my keynote presentation at Financial Technology Forums Wall Street Breakfast Briefing, I cited Xignite as a building block, or participant in a Cloud web services ecosystem to illustrate how the Network Effect of web services and data in the Cloud will become more important than any other single consideration or success factor in the Cloud. During that presentation to Wall Street, one of the participants asked me if I had heard of the NYSE Community Cloud. I had not.
Beyond the "low latency / high frequency" use case, the real driver of where applications run and how they are designed is the data. If data is in the Cloud, it exerts a force, like matter, on everything within its field. And in the case of the Cloud, the presence of Big Data, such as the giant data sets maintained by Xignite and NASDAQ on Amazon AWS draws still more web services and still more data to the AWS Cloud. The "closer" a service is to the data, the better the application performs, the better it utilizes the network, and the more effectively the application can scale.
According to Metcalfe the value of a network is the square of the number of connections. In this sense it seems that "closing" a network severely limits the number of connections. How does this impact the economics of the Cloud?
For a lively discussion please see:
Which is Better?
Beckstrom's Law & The Economics Of Networks – ICANN
Economics of networks Rod Beckstrom National Cybersecurity Center Department of homeland security
2008 Black Hat Keynote Rod Beckstrom director-NCSC-DHS
Topics: Amazon Web Services, Amazon Kinesis, Cloud Computing, community cloud, Enterprise Cloud Adoption, latency, micro services, NASDAQ, NYSE, SaaS, SOA, web services, AWS Lambda, ecosystem, Market Data, Microservices, Network, Network Effect, Public Cloud, Strategy, Xignite
Stay up to date on our latest posts.