The main use for Zend in my last client project was for an API Gateway that is used for alerting and monitoring.
Customization has supported changing project needs but user interface still needs more monitoring features
What is our primary use case?
What is most valuable?
Customization is one of the best features because the solution was not standard. I had to modify it according to the customer requirements, and it allowed me to modify various components.
Zend's debugging environment was sometimes used because I was working as a project manager, though I wasn't directly involved with the tool as there was an implementation guide that used that monitor.
Zend's testing frameworks were helpful in finding issues.
What needs improvement?
Zend can improve the customer screens to have more features.
Features for logging and monitoring could be enhanced, particularly those related to the development process.
For how long have I used the solution?
I remember providing a review for Zend PHP engine last year.
This year, I was working as a service manager for an end customer, which is why I didn't use Zend this year. I used it until October last year.
How are customer service and support?
I would rate Zend's support as seven or eight out of ten.
They provided good support and answered our queries promptly.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
What other advice do I have?
The product was not purchased through the AWS Marketplace because the customer is a government entity, and it was bought through a local contact in Peru.
I haven't used Zend's support for frameworks such as Laminas.
I didn't use the monitoring tools.
On a scale of one to ten, I rate Zend as eight out of ten.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
