New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Zend APIgility #13
Comments
My personal experience is that Zend does solid tooling around APIs, but for me they make their implementation and framework a little more complex than they need to be. They do what you need, but take more overhead to configure and customize. |
My experience shows that when a major player such as Zend enters such a field in a reasonable manor, it usually gains much traction. Since they are pledging for community support, I would suggest you take part of their project and that way the entire community may benefit from your experience and knowledge. Cheers, |
@tailorvj, IMHO, this is way too difficult for our target demographic—federal agencies for whom the prospect of putting together an API is technologically beyond their capabilities or funding. Zend lost me at this step:
That's a deal-breaker. Many of the people implementing this within agencies are not able to install software on a server (for reasons of permissions or limited experience) beyond simply uploading a directory via FTP. "Composer" does not appear to be SCAP validated, either, which makes it quite difficult for federal agencies to use it. (This is a process that I have no experience with, though.) Apigility might be really great, but I don't think it's feasible for Project Open Data's audience. |
Hi, what are your thoughts about Zend's DB to API library apigility?
https://github.com/zfcampus/zf-apigility-skeleton
The text was updated successfully, but these errors were encountered: