The world of API architecture and development is tricky in many ways. Unfortunately, there is no such thing as a “perfect” solution, and with every new implementation or solution, new problems are bound to crop up.
It is important to remember, then, that even the most positive, powerful decisions in API architecture could have significant issues in the long run that, if not recognized in the hazy glow of post-adoption euphoria, could easily interfere with the success of an API or collection of APIs. Read more
We’re excited to announce that we’ve released a new eBook! We’ve compiled our last 10+ articles on the subject of DevOps into a handy compendium. Grab a copy of API-Driven DevOps for free HERE, or name your price on LeanPub. Read more
The advent of cloud computing has changed the way applications are being built, deployed and hosted. One important development in recent years has been the emergence of DevOps — a discipline at the crossroads between application development and system administration.
Empowered developers have been given a wide new set of tools to enable:
- Application lifecycle management with continuous integration software like Jenkins, Travis CI, CircleCI, and CodeShip;
- Server provisioning with software and metadata using configuration management tools like Chef, Puppet, Salt, and Ansible;
- Hosting applications in the cloud, whether they use an IaaS provider like Amazon Web Services, Google Compute Engine, or Digital Ocean, or a PaaS solution like Heroku, Google App Engine, or any technology-specific offering.
Unlike diamonds, information systems (IS) are not forever. As a company evolves, its IS evolves too. This evolution is induced by a company’s business and organizational transformations, regulation modifications and/or technical revolutions. In this Lego computing age, evolving an information system often means aggregating existing brick products instead of building them to create value. Read more