Infrastructure as code (IaC) delivers the promise of agility and speed to IT Ops teams as well as developers. Yet new terms seem to be blended or, worse, misused in the context of what value can be achieved.
Infrastructure as code (IaC) delivers the promise of agility and speed to IT Ops teams as well as developers. Yet new terms seem to be blended or, worse, misused in the context of what value can be achieved.
Topics: Application Composition, Application Templating, Component, Component as a Service, Component based software engineering, Component Software, Componentization, composable, composition, DevOps, Ecosystem, Enterprise Applications, Enterprise Architecture, innovation, IT configuration management, open source software, OpenSource, Service Oriented Architecture, software development, Software Engineering, source code management, Full Stack Deployment, DevOps Automation, Infrastructure Automation, Kubernetes
Topics: API, API Best Practices, Component as a Service, Component Software, CTO, CXO, Platform 3.0, Software Engineering
14 years ago I was running a group at TIBCO that was bringing TIBCO to the Internet. Yahoo!Finance was built on the TIBCO pubsub infrastructure. At the time Yahoo was the biggest cloud/internet company and the finance pages were the most popular pages on the companies web site other than search. The hits were astronomical even at the time. It was the fever time in the tech internet industry and everyone was following the stocks of the new internet players. Many people including myself had written programs that leveraged Yahoo's web site as an API to build applications for stock analytics, portfolio analysis and to embed in their own websites. I know that Yahoo was getting 100 million hits to the web site a day or more but probably few of those were really applications making calls. There weren't a lot of other APIs in the Internet at that time. I would guess that there were 10^9 a billion "pseudo-API calls"/month back then. This is the kind of traffic that a small startup would get today for its API. :)
Topics: API, API Economy, API Management, APIs, Application Composition, Cloud, Ecosystem PaaS, Megatrend, Mobile, Network Effect, PaaS, Platform 3.0, reuse, Social, Software Engineering
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
