You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Jun 18, 2024. It is now read-only.
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.
@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:
At this point, you need to use Composer to install dependencies. Assuming you already have Composer:
composer.phar install
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.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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: