Topics: Accelerating Pace of Change, Agile, API, API Management, App, Big Data, BigData, cio, CIO, Cloud, Cloud Services, Collaboration, contributions, corporate IT, cto, CTO, CXO, DevOps, Ecosystem, Enterprise Software, Faster Time to Market, History, InnerSource OpenSource Megatrend SDLC Enterprise R, IOT, IT, Megatrend, megatrend, Mobile, Network Effect, Open Source, open source software, PaaS, Platform 3.0, Social
It is my contention that 90% of costs are being eliminated from the traditional software development process and the time to market reduced dramatically by leveraging the reuse capable today via open source, APIs, fast deployment and resource sharing with PaaS. The cost of Enterprise Software was magnified by an order of magnitude by the lack of reuse prevalent in the old paradigm of software development. This is apparent as we see how fast we are able to build technology today. This is a major reason for the massive adoption of disruptive technologies of open source and APIs we see today.
Topics: Accelerating Pace of Change, Agile, API, App, Big Data, BigData, bigdata, Business Connectivity, cio, Cloud, Cloud Middleware, Cloud Services, Collaboration, collaboration, communities, contributions, corporate IT, cto, CTO, CXO, Ecosystem, Enterprise Architecture, Enterprise Renewal, Enterprise Software, Faster Time to Market, gamification, Git, inner-source, inner-sourcing, InnerSource, innovation, Integration, Internet of Things, IOT, iPaaS, IT, IT organizations, MDM, Megatrend, megatrend, Meritocratic, metadata, middleware, Mobile, Network Effect, Open Source, open source community, open source software, OpenSource, PaaS, reuse, Social, Tesla, WSO2
It all started about 15 years ago Apple introduced the iPhone.... It seems like this anyway. The date was actually in 2007, a mere 6 years ago + a few months. Since then the world changed so dramatically it is almost impossible to imagine a world before that and to realize that it was a mere 6 years ago that life was so different.
Topics: API, API Management, API Store, App, BigData, CIO, Cloud, Cloud Security, collaboration, Component Software, CTO, Enterprise Application, Enterprise Architecture, Enterprise Mobile Management, Enterprise Refactoring, Enterprise Store, InnerSource, Integration, MAM, MDM, Megatrend, Mobile, Mobile App, Mobile App Store, Mobile Application Management, Reduce Costs, REST, reuse, SOA, Social, Social Business, Software Engineering
A complaint I heard from a CIO recently was that when talking to the high flying technologists at his firm he said: "they talked in strange names, Kafka this, docker that. Names of open source projects, APIs and languages that make him wonder if these people can program or just piece together technology and names? It's very easy to toss around a lot of names and convince somebody you know what you are talking about, but the real question: If you assume that you can do things like this; Is this the way we should be building software these days? Talk to developers today and a lot are doing something different than what we did just a few years ago. Today developers may use languages such as Ruby or Scala, PHP or Clojure or combinations of these things in a single project, they may use google APIs and back end as a service APIs, Salesforce APIs and APIs for doing pattern discovery, blob storage. They may use Storm or Kafka, App Factory, CEP, Stratos, docker, node.js or cassandra or an open source Identity Management. They may develop on IntelliJ or CodeEnvy in the cloud. They may build their technology with dependency injection, aspect oriented techniques, test using Chaos Monkey, appium and numerous other web services that in general allow them to have very high productivity. It is very likely they will complain bitterly if you don't have Git, Maven or Jenkins, Chef or Puppet and numerous other open source tools for them to use that they are familiar with. It's a new world that has evolved very rapidly. This cacophony of names is scary for some. I love this diagram that Kinvey came up with some time ago that illustrates some of the complexity of just the APIs for backend as a service in the new paradigm:
Topics: API, API Management, APIs, App, Application Composition, BigData, bigdata, Chaos Monkey, CIO, Cloud, Collaboration, Component Software, CTO, CXO, Enterprise Application, Enterprise Architecture, InnerSource, Integration, IOT, Megatrend, Middleware, Mobile, Open Source, Resilient, reuse, Social, software development, Software Engineering