Answer the question
In order to leave comments, you need to log in
Highly loaded php project without frameworks?
Good afternoon!
How realistic and logical is it to create high-load projects (portals, forums, etc.) without using php frameworks, using procedural style? Would this be the correct approach? What difficulties may arise in this case?
Thank you.
Answer the question
In order to leave comments, you need to log in
Absolutely impossible.
You will still write your framework as you work, only you will have problems with it that you wouldn’t have with existing ones (some of which can be solved by spending a lot of time and money).
using procedural style?It will take a lot more time and money.
If the problem is that you do not want to completely depend on the implementation of the framework, then you can use, for example, Symfony components. In addition, they are used in other frameworks.
unrealistic, therefore illogical.
the wrong approach, as the probability of errors in this style is higher.
I worked for iMesh Inc. (60 million active clients) - everything was on procedural PHP4, but it was in 2009-2010, now I don't know how it is.
Without PHP frameworks - it is quite possible, there are frameworks in Python, Ruby, Java. In a procedural style, it's not a problem, but in the end it will work slower, because it will be cheaper to make changes to the application with a normal OOP than with a procedural one, and the money saved can be invested in hardware.
No need to neglect competent architecture and ready-made libraries. Well, procedurally writing a stupidly serious project. Better buy www.ozon.ru/context/detail/id/33506422 , study it, then go to github.com or https://packagist.org/ , take ready-made libraries and build your project based on them. 90% of bicycles have already been written and tested by professionals, you just need to understand the principle of building high-load system architectures, as well as OOP / Patterns)
It is quite possible and even SHOULD try to create, because. there are no normally working "bicycles" now.
Plus, you will be able to step on the same "rake" as everyone who developed their "dizhok" from scratch, pump your level of knowledge.
1. Organization of the application model and structure: abstraction layers © (router, service, ACL, template, session, validator, storage (database, file structure, third-party web service), etc.) with on the one hand and the MVC model on the other.
2. Preventing the use of duplicate logic or code within the entire application. Thus, by solving this problem: development time and memory usage will decrease.
Didn't find what you were looking for?
Ask your questionAsk a Question
731 491 924 answers to any question