In this blog, Ricky Severino, a recent computer science graduate from The American University, shares perspectives gained from his internship at Agile Stacks.
Topics: Cloud, Cloud Computing, Cloud Services, code collaboration, Automation, DevOps Automation, Machine Generated Code, AWS, Machine Learning, Higher Education, Infrastructure Automation, Kubernetes
|Join our Docker, Microservices, SOA, API workshop!|
I could talk about each of these components in isolation, for instance, Mobile and talk about the growth of it and changes it is fostering but you wouldn't get the big picture. The change we are seeing can only be understood by considering all these components together. They each affect each other and the widespread adoption and improvement in each drives the success of the other. Therefore, this article is intended to give you the context to understand the entire change we are undergoing rather than any particular element. By seeing that you see that adopting any one technology or doing any one thing will ultimately fail.
The idea of the virtuous circle is that each component of the circle has been critical to the success of the other parts of the circle. It is hard to imagine the success of any of these elements in isolation. The massive adoption of key aspects of the circle is clearly needed but each element of the circle has been key to the success and adoption of the other parts. The constant improvement in each aspect of the circle drives improvements in other parts of the circle driving more adoption and more innovation. The process feeds itself and grows faster as each element grows. It is impossible to say which element is less - critical so they have to be considered as one.
These components of the virtuous circle imply that to leverage the benefits of the circle you have to be using components of the circle in your processes. The more components you use the more benefit you gain from the circle and the faster the change you will experience. The combination of these technologies is being called Platform 3.0.
The benefits of each part of the virtuous circle
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
Recently I gave a talk on helping to select PaaS from among the many PaaS out there and understanding the taxonomy of PaaS or simply how to categorize them to put them in useful buckets. One person at the talk asked about use cases for PaaS. I realized I haven't blogged about the most common or interesting use cases for a PaaS's or ECOSYSTEM PAAS's.
If all the cloud terminology and cloud is confusing to you read this.
Topics: Accelerating Pace of Change, Agile, aPaaS, API, APIs, App Factory, AppFactory, Application Composition, Autoscaling, Chef, cio, Cloud, Cloud Computing, cloud security, Cloud Services, CloudFoundry, Component Software, cto, CTO, CXO, DevOps, Disruption, Ecosystem PaaS, Enterprise Application, Enterprise Applications, Enterprise Architecture, Enterprise Refactoring, Enterprise Renewal, Faster Time to Market, Hybrid, inner-source, InnerSource, innovation, Integration, Megatrend, OpenShift, Oracle, PaaS, PaaS Use Cases, Platform 3.0, Polyglot, Puppet, Reducing Costs of IT, Refactoring, Resource Sharing, REST, reuse, SaaS, Salesforce, SAP, SDLC, Software Engineering, Technology Adoption, TIBCO, Use Cases, WorkDay, WSO2, WSO2 Private PaaS