Laminas Project vs. Laravel PHP Framework

Zend Framework is well suited for large (or potentially large) software projects. It has the tools and structures for organizing and maintaining millions of lines of code by providing different scaffolding and service management capabilities. Obviously, it works well in environments that prefer a traditional PHP-based MVC stack as that is how it's designed. For smaller or less experienced teams, it might be faster to build something using a simpler framework such as Laravel or Symfony because the learning curve is a bit less steep. The routing system of Zend Framework is incredibly powerful but also very hard to get right, for example. Overall, however, being skilled with Zend Framework 2 will be very advantageous.

Incentivized

This framework's pros are more than cons. It can be used for many purposes; building e-commerce is one of them.

1. Code is clean and simple because of its routing.

2. Connection to database and query optimizing.

3. The amazing automatic memory to remember past queries is a big plus.

4. Migrations is the most crucial feature of this framework.

5. Supporting unit tests out of the box.

6. Artisan to use command line.

7. Large community to support your queries.

Incentivized

• The Zend Framework excels at productivity. It's lightweight, loosely-coupled enough to provide 90% of the functionality that everyone needs out of the door, but also customizeable enough to meet the remaining 10% should your business need it.
• Because the Zend Framework is functionality focused (also supported by the actual PHP developers) - it is light enough to hit the ground running with. Having no configuration files to get rolling is also a huge plus.
• The documentation of the Zend Framework is reliable, updated & succint. I have not encountered an issue that I could not easily troubleshoot from looking at the documentation.

Incentivized

• Many libraries available which simplify integration of SaaS APIs within your application (eg, MailChimp, Mandrill, Stripe, Authorize.net)
• Pre-packaged tools to facilitate common tasks when building applications (eg, User Authentication and Authorization, Background Jobs, Queues, etc)
• Support for a broad set of technologies out of the box (eg, PostgreSQL, MySQL/MariaDB, MemcacheD, BeanstalkD, Redis, etc)

Incentivized

• The routing configuration is very painful to use. Seems like it was thrown together.
• The framework is very heavy, and sometimes confusing with how abstracted everything is.

Incentivized

• There isn't a whole lot to dislike about the framework, honestly. If I am forced to say something is that sometimes the authors change the directory layout and it's not always easy to deal with. That being said, I've never not been able to upgrade within a few hours.
• Sometimes using the artisan CLI - it requires additional tweaking to get it running on non-standard application rollouts.

Incentivized

I absolutely love Zend Framework. However we are using Zend Framework 1 and when we get to the point that we need to go Zend Framework 2 (for PHP namespacing) I may explore other frameworks. When we chose Zend it was the best option for us. I'd like to see if maybe there's a better fit that doesn't have the same complicated overhead of Zend Framework

Incentivized

Zend is very usable once you learn how to use it. I've had moments where I thought what I want to do isn't possible but I've learned I haven't looked in the correct place yet. Zend is a Catch-22. It's very usable once you know how to use it. But I strongly feel it's worth learning

Incentivized

Zend Framework has the best (paid) support and ecosystem I've ever seen in a PHP framework. The company has developed many products, including Zend Server, Zend Debugger, and an Eclipse-based IDE that extends the framework to create an entire development platform that can improve developer productivity and software quality while maintaining the clean architecture that characterizes the framework.

Incentivized

It isn't the fastest but is one of the faster available. It's the only one currently supported actively by the PHP team itself. You might find more classes in Symfony for instance, but in the end, most of the core files will be supported above Zend classes either by extension or by encapsulation. The only con that I see is the learning curve required to adopt this framework, and the amount of additional work you will have to do to build PHP based apps with it.

Incentivized

Originally, it was a decision between Zend, CodeIgniter, and CakePHP for me. I chose CakePHP and used it as my main PHP framework for at least a couple of years before noticing and giving Laravel a fair try. Ultimately I selected Laravel because I felt it fit with my preferred development style, it utilized many of the modern best-practices I wanted to follow, and I felt that it allowed me to build better things in less time that seemed more maintainable. I have used, and still do use, Symfony directly for certain things, but I think of it (and use it) more as a code library than as a full application framework. When I'm building a web application, I tend to prefer Laravel.

Incentivized

• It has had zero cost of maintenance over the last 10 years and counting.
• No version upgrade has introduced a single issue in 10 years.
• Systems didn't have to be re-implemented and they aren't in debt either.

Incentivized

• Positive: Our delivery time for PHP application is faster than usual.
• Positive: Developers are happy and they write better code with their usual development tools. No tool-upgrade necessary.
• Negative: Initial delivery took 6 months extra and had to rewrite project several times.

Incentivized