Apigility is an API Engine which speaks HAL. HAL is Hypertext Application Language. Such a huge word! How big is Hypertext? And to build an API language which speaks Hypertext? This will become the common dialect of APIs.
The first question ZendCon asked was, “Where’s the Doctrine integration?” Soliant stepped forward and said, “We’ll build that.” And we did.
Help came in from the community for ODM support. I hadn’t considered the need for ODM but it’s core Doctrine support so we built ORM and ODM together. Some pieces of code work for both and other code is specific to one or the other. The integration of both is handled well.
At Soliant we used the new library to create an API with three separate databases and a connection to Mongo through ODM. One of these APIs accepts a Doctrine JSON schema then, with it, creates the entity, the table it defines, and creates an API to serve the data for that table. This kind of functionality would have taken months of resources and wouldn't be as good as what Apigility enabled us to accomplish.
This project was not built with Test Driven Development. At the beginning of the project we could see no end solution as it was too far away. So unit tests were not added until the project was functionally complete. There arose a problem of the Admin requiring the Server and the Server requiring the Admin for testing that Travis could not compose, so the two libraries were merged. Thanks to their common ancestor git was able to merge them with little hassle.
The project has now been moved from Soliant Consulting to ZF Campus: Download it here. This was the plan all along and it's satisfying to have made the hand-off.