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
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.
API management is a term that has been used in the API economy for several years and has existed without acquiring an exact, universal definition. While most protagonists in the API community agree on the core themes of API management and why the subject is important, the specifics are frequently defined by the capabilities of commercial “API management” solutions. Read more
If an API is implemented correctly, the number of users utilizing a service can be staggering. Millions of users and devices connect to the internet every day, utilizing APIs to perform calculations, convert media, and even help cure cancer.
The API developer’s dream come true, however, can also be a nightmare. Read more
In the first part of this series, we introduced Play framework, a web development framework for Java and Scala developers, and we showed how it enabled one to expose a basic REST API with minimal effort. In this second part, we explore some of the features of Play and use real code to illustrate its capabilities. Read more