multiple layers of interoperable elements • Each elements operates with defined interfaces • Example: car gearbox made the engine independent of differential • Example: credit cards abstract us from cash 7 Hardware Operating System Virtualization Application Software Infrastructure Operations Middleware Manage complexity through defined interfaces Abstraction compute storage network compute storage network MS Linux DB Email File Runtime
server hardware and operating system • Docker abstracts the application from the operating systems • Overlay networks abstract packet forwarding from the physical network hardware 8
Google • hosted email is “convergence” • hosted documents • Cisco is getting into servers, storage, security and more • Dell is getting into software products 9
HTTPS in the API for Apps. • developers must request exception to use unencrypted HTTP • installing root certificates to IOS ? • US Government is mandating HTTPS on all sites • Google is preferentially SEO ranking HTTPS enabled sites 10
• EVO:Rail & EVO:Rack • Cisco UCS • Data Centre Operating Systems • Mesosphere • vRealize • SCVVM • Compute / Storage / Network no longer “separate” disciplines • integrated skills • still need experts but many skills will disappear 11
about Enterprise IT • Value derived from “preparing the platform” • analysing • No more knob twiddling • custom vendor features that don't really add “value” • “I could do this” or “implement this hack” • If you have to develop a software API to deploy a one- off trick ….. 12
using vendor-specific features …. • then products become less differentiated • Value shifts from knobby features to software integration & orchestration • Which brings me to …. standards & integration 13
Open source • Open Access • Open Standard • Open Process • Open API • Examples • Linux • OpenStack, Open Daylight • An “open box” must have only one open side to be useful 16
eg. Roman success of standardised weights & measures • standard railway gauges • Reliability - open tends to better • open standards are often more considered, better thought through. • Interoperability • reduces customer risk which creates demand • modular exchange of components • Open Markets are bigger than closed markets • less risk on investment • customers are more likely to buy (no “training the market”) 17
access to emergency services are multi-decade commitments • some create legal precedents and rules • But startups are driven to move fast or die • 5 to 10 years of standards process • do or die 18
• Have SDOs passed their “use-by” date ? • A question of relevance and NOT existence • Linux Foundation, Apache Foundation • ship first, ship fast, ship anything • Who sends delegates to Standards Bodies • Universities & Vendors • Which people are selected ? • hint: not always the best or brightest 19
strength of the project is 100% dependent on the interests, energy and capability of the developer community • Law of OpenStandards: importance, validity and timeliness of relevant specification is 100% dependent on interests, energy and compromises of the individuals who have been empowered to manage, organize and complete the work effort of the SDO 20 Reference: Open Standards, Open Source, Open Loop
does a modern employer offer ? • how much, what loyalty should you offer your employer ? • Career loyalty • will you have the same career all your life ? • Vendor Loyalty • who supports a sports team all their life.. • what the quid pro quo ? 26