September 9, 2019
Related Articles (880)
The thing about agile development is that for all intents and purposes an application is never done. Successive waves of updates to an application means that development teams have to come to terms with the simple fact that the care and feeding of any given application is a continuous process that takes place over many years.
As the Web API space heats up, it's becoming more difficult to differentiate yourself and attract developers. And so it's crucial that your API can perform well. Performance isn’t just about processing requests and delivering responses quickly. As Netflix experienced this year, understanding how users makes calls, why they make the calls they do, and what should be contained in your API payload is critical.
Google Cloud Platform is positioning itself as a major player to help mobile developers get off the block fast. While the platform was complete in terms of its Compute Engine (IaaS), App Engine (PaaS) and cloud services (Storage, Big Query, etc), developers still had to do the work of connecting the pieces. If you were a mobile developer who wanted a quick starter application in the Google cloud, you had to figure out the pieces. Similarly, if you were looking to expose your app engine applications as a bunch of REST-based services that would scale to heavy loads and work across multiple mobile devices, you had to work on your application to do so.