How to keep up with the evolution of the PHP Framework?

Question

So, I'm going to start a great property management system for the cloud. This system already exists in VB.net technologies, and now we are transferring the entire system to the Internet.

We are trying to decide between ASP.net or PHP, we are thinking about PHP because ASP.net will cost too much on licensing and servers. So there are Laravel, Symphony, CodeIgniter, Zend, etc.

The fact is that this project should live for many years. But we feel that we are getting a restriction using the PHP framework, because every time the environment is updated, we need to update our entire system. For example .. now Laravel has been updated from version 4 to 5. And the entire folder structure has changed. I can’t imagine that our large system needed to be updated and kept up with each update of the Laravel version. How do you deal with this?

Besides what happens if Laravel disappears, his fashionable fashion is now. But we see that the PHP frameworks come and go.

Would it be wiser not to use any php infrastructure and build everything from scratch in order to have more control over it?

Answer 1

You should first notice that using the framework is primarily designed to solve two problems:

• Force encoding to a specific "format". Working together on code, you can create “hacked” solutions or unsupported code. A frame can be a force that helps keep these things under control.
• The framework has a certain kernel code that handles, for example, database abstraction, routing, etc., which can save you a lot of time to develop yourself.

Additional Information; when introducing new features, there is a chance that someone built it earlier and, perhaps, even better than you expected.

Saving a structure should not be too complicated if you adhere to the principles of coding a structure. With larger frameworks in new releases (or after they are once generated), we took into account how to transfer your previous version to the new version format.

The choice of structure to use is a question that is based on opinions and is not suitable for discussion here, but keep in mind that you choose your structure according to your needs. Also check how large the community is and how many third-party plugins / code exist (the more, the longer the infrastructure will work).

Good luck

Answer 2

You can see the framework as the basis for a start. Remember that you get all the code! Look at the code. Do you like this? Does this fit your requirements? Using structure gives you a huge advantage over how to do everything yourself from scratch.

But do you need to upgrade? Are you constantly updating your own code? Perhaps this is not always necessary. Of course, if there is a security issue, you should do something about it, but viewing each update as important is simply pointless.

I create projects aimed at specific versions of frameworks and libraries. I try to use flexibility, so I can change the framework and libraries and versions, but often find that I stick to what works.

Some people may not like this, and argue that you should always be in the latest version, but I think this is completely impractical.