Php frameworks why use

The paragraph on MVC was the weakest part of the entire post, which gave a good picture, but lacked serious research. That's not exactly true. Drupal is a framework more than anything else. Drupal is one of the most powerful platforms for web development, you can essentially build any web application on it and that's why we Drupal developers love it so much.

Give it a try! Good article. I am starting at PHP and it was really hard to understand why I would need to use the framework, but now it is getting easy to me. Thanks to this kind of articles. Cake doesn't require command line, its just an added feature.

I've been using cake for a while and never touched the command line other than curiosity one time. CI is pretty sweet too, can't go wrong either way!

Personally, if I'm building something highly customised from scratch, I prefer Zend Framework but almost anything is also possible with Joomla. Great read! My favorite from the list would have to be CodeIgniter mainly for its excellent performance. Frameworks are good for learning and for fast development and iterations, but your readers should be aware that using any framework even codeigniter gives you a noticeable performance hit compared to straight php.

Not sure which framework you're using, but they're not all quite like that I use Yii - my first framework. It's easy to learn, has great support, and has speed comparable to CodeIgniter with more features and PHP 5. Very well written article, I personally use CakePHP however I think too many people use theses frameworks for the wrong reasons.

As a shortcut to learning PHP. I can gurantee you a large portion of users that are implementing these frameworks couldn't even write a basic database class. I support CodeIgniter. It's lean, its fast and doesnt require command line access like cake. CI - FTW! I've done a lot of apps with the Yii framework, and I must admit that it's one of the better frameworks.

I've also used Zend Framework and Code Igniter, but they are definetely not in the same league as the Yii framework. More information can be found on. Codeigniter, 2.

KohanaPHP, 3. Zend Framework. I use all them not for one application of course. I'd like to put to your attention also Sapphire framework. Coming also with the CMS Silverstripe. The documentation is quite good and there is also a helpful community of people around.

I think symfony is a very good framework next to Zend probably. I just the hope the speed issues gets resolved immediately. I am using it and loving it! Good point. When I was evaluating frameworks well over a year ago the documentation advantage of symfony sealed the deal for me.

While I work with other frameworks I've continued to be impressed by the quality of the examples in symfony. The speed issue is something that is being addressed in Symfony 2. Originally a fork of CodeIgniter so it's lean, mean and incredibly fast unlike the other bloated frameworks. It's also based on PHP v5. Kohana code changes wayyyyyyyyyy to much it would be a great framework if the people there would get things organized From our "agency perspective", we've used CakePHP since 0.

Drupal isn't even an application framework, so I'm not sure how it could be more flexible than any of the other solutions mentioned the article. Your post makes me realize you have no clue how to develop with CakePHP. If you expect to see the same stuff you saw on Rails, stay with Rails. Further yet, new versions increase the performance even further, putting it at the top of its kind.

I've been using Zend Framework since it's very early betas a few years back. It's a great framework but it's never-ending development process is both a blessing and a curse.

We're almost to version 2. I have used and love PHPonTrax great framework. Better than any the others I've used and I've tried em all. Unlike other frameworks, it allows you to develop sophisticated web sites and web applications easily and intuitively in a single language, PHP. Another good framework that's currently being developed is Recess.

Keeping a good watch on this one and looks really interesting. Symfony is not slow as mentioned above. Comparing fastness by hello world is not fair to the framework for people building serious high traffic applications. I believe you have that backwards. If the majority of developers all used a small selection of frameworks you'd have a commodity. Lightweight custom code is the very opposite. All clients are unique. To approach it otherwise is to create a commodity web. While I respect your opinion, I have to disagree entirely.

I think it's great using it with ZF collection of useful classes. Nice article, however CakePHP and Codelgniter are horrible to develop with from a modular perspective. From an agency perspective Drupal has been our preferred framework and far superior IMO. Having a Rails background before getting to know Cake, made it very obvious to me that Cake was trying hard to be a Rails clone.

Cake and Rails have gone their separate ways, but there are still many times that it reminds me of Rails 1. Cake is absolutely horrible by comparison to Rails. Aside from being a lackluster framework, please google some benchmarks. Cake has abysmal performance. I have used Symfony and I liked it much more than Cake. If you are looking for great frameworks please consider frameworks that are not PHP centric such as Rails or Django. It's easy to install, configure and port to other platforms.

There's a JavaScript port so you can have the same paradigm on both client and server! I have used both Cake and CodeIgniter, they are very similar in my opinion but more importantly they are very popular. This allows me outstanding documentation and I don't have to worry about another programmer taking over, because they really should be familiar with these two. For those who don't know, Kohana is a spin-off of CodeIgniter and is maintained by the open-source community unlike CodeIgniter, which is controlled by the company that developed it--which is not necessarily a bad thing, especially if like the idea of having a support team to contact.

Some things may not be obvious at first but there are a lot of great books out there that cover it check out the APress series.

It's really robust and has tons of useful components that have been developed in a highly professional manner, and the fact that some of the greatest PHP experts out there use it for their largest projects is definitely a good recommendation. My impression from a long history of programming in PHP and trying out various frameworks is that Zend is a good recommendation for anyone other than an absolute beginner--it's just that you may need a book to help you along if you're not real familiar with object-oriented programming.

In the past, I shied away from Zend Framework because I heard it was complicated and difficult to learn, but I realized upon using it that it makes a lot of sense and you can get the hang of it pretty quickly.

I think the only reason some people find it very difficult to understand is that it is so highly object-oriented, but if you want to take your programming to the next level I think that's something you should learn thoroughly anyway. Yii is, by far, the best PHP framework I've ever worked with. Do it. It's awesome. You guys should check out Python. They are all pretty solid. It's orms like SqlAlchemy and template languages like Mako that get the big players using python. Very nice review of some of the options available, this is the first time I've even heard about seagull.

I will offer my opinion: In most cases a php framework is flat out over kill. While you have written that things like cakephp are "easy" to use and "fast" to develop with, I have an opposite opinion: I think they are heavy weight and add another level of complexity that in most cases just isn't needed.

Every client is always unique, and an experienced programmer will always end up with a leaner meaner solution when its built from the ground up. I tried cakephp and it sucks in terms of developing web 2. Also the way it produces query pattern sucks like anything. Requesting your view of PHP on Trax. Is it alternative for RoR developers??? We do a similar thing with our projects.

CodeIgniter gets the job done quickly for smaller projects, but we've developed an internal framework based off Zend Framework for our big projects. I think Symfony is more than the author said. For example, it has the better documantation of all frameworks above. Is it just me or is this a terribly inaccurate article? Didn't get past the third paragraph so can't comment on the rest of it but your understanding of frameworks and MVC is seriously flawed.!

This sentence makes no sense. The frameworks you've listed employ the MVC design pattern - it is by no means the "workings" of a framework. No one ever said a framework had to follow MVC principles. No, no no! The Model contains business logic, rules and methods for manipulating data - not "data". The controller is for routing ONLY, it should contain as little business logic as possible. Look up thin controllers, fat models. Please research your topics more thoroughly before posting.

I prefer to use CodeIgniter as a beginning level and the Zend Framework for the advanced level. Actually I use both of them because CodeIgniter helps me to start with a short-time project and Zend helps with a long-time project as their no. So you the guys can also try it out with your project types. This article might be useful because it contains links to some popular PHP frameworks, but there is much inaccuracy in the article itself.

For example, Zend Framework has not been around since V3 it's focused on pure PHP 5 support - which is also something to take into account, because CodeIgniter e. I stopped reading about there but spotted some more inaccuracies in scanning, so I would recommend people to not attach too much value to this article.

I'm surprised you did not mention Joomla. It was the first MVC framework I worked with, and it was delightful to use.

It has a big community of developers and follows a good set of standards. Yii has a steep learning curve, making it somewhat harder for beginners to get started. It also requires greater attention during development as one mistake in code can cause issues in the entire application. Zend is a complete object-oriented framework, using features like inheritance and interfaces that make it highly extensible.

It is open-source, easy to use and an excellent choice for building feature-rich enterprise-level web applications. Zend is highly customizable and follows PHP best-practices. Zend is now transitioning to the Laminas Project. Migration to Laminas is highly recommended since Zend is no longer updated.

There can be a steep learning curve for mobile app developers using Zend. Zend plugins can also come at high cost, making it more expensive and not suitable for projects on a tight budget. It is delivered as a web server extension written in C no knowledge of C is required to use it.

Phalcon rolls out updates and patches to fix bugs somewhat infrequently, which may not work for applications that need high levels of security. It supports the MVC design pattern and also has its own version - hierarchical model view controller HMVC , which adds another layer between the Controller and the View. With HMVC, duplication is content is not required to show on multiple pages, saving time and memory. Since FuelPHP is relatively new, it offers less support and may have a steeper learning curve compared to other frameworks.

Slim is a popular micro PHP framework that helps developers quickly create simple yet powerful web applications. Built-in ways to authenticate and authorize users , which is also a great reason to choose the Laravel framework. Lots of available extensions. Today there are almost 10, of them. Ease of learning. No integrated interface templates. The framework has a sonorous, easy-to-remember name, which is far from its only advantage.

It is flexible in structure and takes a modular approach to development. Symfony-based websites and web applications are really efficient. That's why the framework in question is targeted at large projects such as high-load e-commerce platforms. Symphony has taken its rightful place in the list of PHP frameworks, but it is useless to people with no programming experience.

Convenient localization of resources. That is, you won't have a problem creating a multilingual website. A powerful community of experienced developers many of whom are ready to help newbies.

SEO features , or rather, a specially optimized routing system. Code reuse with a set of plugin-like features , which will be useful if you need to create several similar projects. The speed of work. Development experts consider it one of the fastest solutions among popular PHP frameworks.

Lots of plugins available. And they are very easy to install. High-quality documentation , which allows you to understand the work of Simfony in the shortest possible time. Easy customization : in other words, you can easily give your project the look and format you want.

Symphony is a bad option if you are a beginner developer. Moreover, even experienced experts will have to take the time to sort out all the proposed tools. By the way, Symfony influenced the creation of the Laravel framework discussed above. Although, of course, it all depends on your goals. CodeIgniter is especially great if you're aiming for a quick start. It is easy to learn and provides elegant, clean, simple code. But most importantly, there are no strict coding rules.

As a result, you can create and launch your project in no time. Among other things, it doesn't have built-in authentication. So developers will have to write some of the code themselves if they want to extend the functionality of the resource.

Comprehensive and detailed documentation. So you always have access to official and reliable sources. Strong expert community. Even if you're new to programming, you'll be able to find someone in order to request assistance.

Good performance. CodeIgniter is a powerful PHP Framework, which allows you to build high-performance web applications. The small size of the framework. A small amount of code makes development easier and faster. No complicated setup. Almost no configuration has a positive effect on working with the framework too. MVC architecture. Support for third-party solutions.

You can connect third-party plugins and libraries or write them yourself if you don't find them among the pre-installed ones. The rarity of updates. However, the problem is almost solved. Reduced functionality , as we said earlier. But you can write them yourself or connect third-party solutions. We recommend choosing CodeIgniter if you need a small and scalable web application.

CakePHP has been in existence since And all these years are marked by active development, which made the framework a strong player and a real leader.

The solution is renowned for its lightweight and elegant code and considered an easy-to-learn environment. It is undoubtedly worth your attention. The framework's division into basic elements. And each of these components is independent in its use. Easy scaling of projects , which is achieved due to the flexible architecture of the framework.

The opportunity to create cool designs. In CakePHP, themes are turned into plugins, which greatly expands the development possibilities High level of information protection.

Easy installation and setup. The bottom line is simple: CakePHP is pretty easy to use. The constant release of updates. That's why CakePHP belongs to the most used frameworks. These kinds of tools can be a huge boon towards understanding how all parts work together, and they can simplify and give structure to your testing strategy.

However, they also tie you directly to your framework, at a very fundamental level. To decouple HTTP request lifecycles from a framework, look for other ways you can test. This can be used regardless of the framework — though it may require custom scaffolding to work with an application. It can also be used in any application that uses that standard. To perform framework-independent integration or functional testing, another option is to use external, black-box behavior-testing systems such as Codeception or Selenium.

With these tools, you can create tests that define the client conditions and actions, and assert against what they receive in response. If you have a handful of users, and they all understand what is being done is computationally expensive, your requirements will be quite different than a website that supports hundreds of thousands of customers daily.

They can provide metrics that show how fast the framework can return a response. However, the numbers can be misleading. As your application grows, its bootstrapping costs will typically increase, adding to response times. The complexity or simplicity of your PHP deployment will be determined by system complexity. For example, how many systems — such as databases, caching services, and log aggregators — are involved?

Will you be scaling horizontally? Using frameworks adds more questions and potentially, complexity. For example, some frameworks will require you to pre-compile certain pieces of the application before you deploy.

Depending on your configuration, you may also need to ensure certain environmental variables are set and present on the target system. Some frameworks provide tools that help prepare your application for development, including Platform-as-a-Service PaaS solutions. PHP provides many security tools and the number and quality increase with each minor release. Many PHP applications support mission-critical websites and web services. Being able to contact a certified PHP expert 24x7x may be important to you.

If so, check if the framework has support options. The offering also includes consultative guidance for using Laminas as well as ready-to-go adapters for commercial PHP applications. Matthew began developing on Zend Framework ZF before its first public release, and led the project for Zend from through What is a PHP framework? Deciding which one is best for you is easier when you compare how each framework addresses the following 12 capabilities in relation to your requirements: HTTP negotiation Controllers, request handlers, and dependency injection Templates and dynamic content Error handling Rapid application development tooling Data storage Extensibility and framework coupling Maintainability Performance Deployment Security Support The first four capabilities listed are the most critical.

Creates and returns responses to requests.