Published 1 week ago by thebigk
I'm curious to know what do devs actually mean when they say that 'maintaining' an app would be a serious consideration while choosing a framework.
What are the things do you do when it comes to maintenance? For me, all it boils down to fixing bugs and adding functionality. Is there more to it?
Scaling is also an important factor. Your app might work just fine with the 50 or so clients you have right now, but how's it gonna behave a few years down the line when you have 5000? This falls somewhere between bug fixing and adding functionality.
Another thing to consider is how easy you will be to replace. Suppose you decide to leave your company, you'll likely be required to train a replacement who can maintain your apps. How easy is it to find someone who already knows the framework you're using so you don't have to teach them how to use it along with how your apps are set up? On the flip side, how much of a hassle will it be for your employer to replace you with someone cheaper if you don't train your replacement?
@36864 - Interesting insight. I agree about the scaling part. I've began facing with scaling issues in my existing framework and that's one of the top reasons I'm looking at Laravel. Need something that can be understood and maintained by the new developers who'll take over.
I think scaling issues are rarely to do with the framework*. In most cases it's application code that creates bottlenecks.
Maintainability is a different concern. Again, it's primarily application code that's the problem, but a framework like Laravel can help with tools like the queue system, etc. Laravel is a very modern framework, and it tends to nudge you in good directions without forcing you to do things a certain way.
* Okay, if you are Visa, you probably don't run your transaction processing off a PHP framework.
What about the last line in your reply?
"VisaNet handles an average of 150 million transactions every day and is capable of handling more than 24,000 transactions per second." -- Visa website
Now that's a project that requires scale. It is probably not compatible with the inefficiencies of PHP (an interpreted language) and Laravel (an additional overhead).
Everyone seems to think their project needs to "scale big", but most people are kidding themselves. You are not Visa.
What are the scaling issues you have had difficulty with?