API v2 (and legacy v1)
Time for an issue to discuss the legacy v1 and the new v2 of the API.
To make the development of the API easier and more logical, it would really be great to start implementing Slim for this, as routing can be made very easily. Also, authentication via an API token can be easily added as a layer.
How will the new API be communicated to app developers and other API consumers though?
To keep the old API running for the moment, the easiest would be to have a view in the DB that still has all the "old" fields, mapped to the new ones. Alternatively, there could be a second "pods" table which has the exact same structure, that gets updated from the new table periodically. The main advantage of this second approach, is that the new database structure can be changed without affecting the old API and at any given time when the v1 API goes offline, it can just be removed easily.
As we have a clean slate to work on here, let's come up with some nice ideas to populate this