New service: code from scratch or php framework?

Question

PHP

It is planned to create a service, among the tasks of which, the main ones will be: creation and processing of simple forms, image processing, collection of visitor statistics, affiliate system. The issue of data caching and the speed of their loading is also relevant.
Should I bother and make such a service based on any php framework? And if so, which one?

Answer 1

It all depends on the developer. If he is well acquainted with any framework, then, of course, it is better and faster to use a ready-made solution. If not, and you need a "quick start" without bothering about the problems of support, extensibility and "irreplaceable people", then of course it's better "from scratch". Moreover, almost any programmer has developments from which he will quickly assemble a simple system for you.
Although in the end, if you are counting on any serious and long-term development of the project, any popular framework will be the best choice. In fact, anyone, since the speed of work ultimately depends on the hands and not on the tool. The reasons are as follows:
- Existing documentation and community. Get rid of the problem of "indispensability" in case of turnover in the team.
- Test coverage. All popular frameworks are covered by unit tests and support automatic testing for modules.
- A much smaller number of "hidden rakes". These are extensibility problems and all sorts of unpleasant bugs in the “core” of the system. In popular frameworks, they are either solved or quickly fixed. In the "self-written" code, these problems will greatly slow down the development of the actual functionality.

Answer 2

One of the most ideal questions for breeding a meaningless holivar, from which the author still does not learn anything new.

Answer 3

I think writing code from scratch without using a framework is worth it only if you write a framework. And that is not always the case.

Answer 4

Use the framework, leave the self-written noodles for experiments;)

Answer 5

It seems to me that the approach to coding still has the greatest influence here.
I personally do not like to use someone else's code and prefer to make bikes - I just enjoy writing native code. for a small service, I would prefer to do without a framework, even realizing what problems may arise in the future when expanding the functionality of
my friend - on the contrary, he drags himself from different technologies and ready-made solutions
, he could make a small project quickly and beautifully on a good framework - and this process brought him would be no less fun
so, IMHO, more depends on the person

Answer 6

If speed is important, then there is no better Yii .
It has excellent documentation in Russian: yiiframework.ru/

Answer 7

With your versatile functionality, there will not be much difference in efficiency between the framework or self-written code. And here and there you have to add something.
If I allow knowledge, I advise you to write from scratch, otherwise use frameworks.

Answer 8

Just writing from scratch is trouble :)

Answer 9

Do you want to use CMS?

Answer 10

If you need the speed of the scripts, then of course write it yourself, if you need the speed of development, then the framework.
About frameworks it is written on Habré here
habrahabr.ru/blogs/php/50341/

Answer 11

Agree with. From myself, I would also advise the Zend Framework, the possibilities are wide and there are plenty of materials on it

Answer 12

I advise you to consider the third option:
choose not a full stack framework, but solutions to specific typical tasks: they do not dictate how to do a project, but they allow you not to step on a typical rake that has already been polished by the foreheads of thousands of developers.
For example, ORM is one of the areas in which bicycles are least justified: choose from ready-made ones (I advise Doctrine) - it works without a framework.
And so, according to the list, you can try to identify and close the maximum of typical needs, for example,
unit testing - PHPUnit, SimpeTest, Lime,
mail - Zend mailer, Swift,
UI: server-side MVC - one set of options, use SOFEA - much easier with the server (no requirements), more difficult with the client - I advise you to study the list insixrevisions.com/javascript/promising_javascript_frameworks/ ,
etc.
As a result, you will get at least options for standalone solutions, and even ready-made frameworks / CMS can be evaluated for compatibility with these options.