As mentioned throughout the early chapters of this book, Cloud Foundry technology is exceptionally fast moving. Any review of the architecture is just a snapshot in time, and any future view of the technology is subject to refinement. However, keeping one eye on the Cloud Foundry roadmap helps to provide a perspective on the emerging trends that are shaping the IT industry. This chapter explores, at a high level, some of the recent and soon to emerge features, and some speculation as to where the architecture might evolve further.
There is a wiki dedicated to roadmap topics. Roadmaps are generally reflected in public Pivotal Tracker projects, with each core component having its own dedicated project.
The third incarnation of the Cloud Foundry API (known as the v3 API) provides a richer set of building blocks with which you can orchestrate diverse and complex workflows.
With the v2 API, a user (be it a developer or a CI/CD pipeline) can deploy a single droplet per app, as illustrated in Figure 17-1. There is a direct correlation of one app name and one app GUID being associated with one droplet.
For each app, a user can request several running instances. Each app instance will use the same droplet and will be tagged by the same app GUID. A user can ...