Relaunching our Symfony case studies! Discover how Upply tackled tough tech decisions like sticking with PHP for scalability and performance with Florent Laval

The Symfony Blog provides updates, tutorials, and insights on Symfony, a popular PHP framework for building web applications. Covering topics such as framework features, best practices, and community updates, the blog offers resources for Symfony developers looking to enhance their skills and stay up-to-date with the latest developments in the Symfony ecosystem. Developers can learn how to leverage Symfony's powerful features and conventions to build robust and maintainable web applications that meet the demands of modern web development.

Symfony

Upply, a tech platform for freight transportation, faced a decision in 2022 on whether to keep using PHP for their backend or switch to Scala, Rust, or Go. They ultimately chose PHP due to its stability, developer productivity, and mature ecosystem. The post discusses the challenges of marketplace development, the architectural decisions, and the cost-benefit analysis of sticking with PHP versus migrating to another language.

Upply: The PHP advantage: How we resisted the switch to Scala, rust, or go (Symfony Blog)

Marketplace Challenges in a Fast-Evolving Environment

Performance, Scalability, and Reliability: What Our Architecture Demands

PHP: From Skepticism to Success in a Scalable System

Assessing the Migration Costs: PHP vs Scala, Rust, and Go

Why PHP Was the Right Call for Our Team and Marketplace

More often than not, an update to the latest language version and dependencies and/or a refactoring is more beneficial than switching to an entirely new language. Someone is more likely to make mistakes and write unoptimized code in a new language than the one he is familiar with.
“Re-inventing the wheel” is a thing to be avoided as it often leads to a worse product. There are scarce times when it’s the right thing to do, but it still needs very good scheduling and a fully understanding of all the ins and outs of the new workflow.

Fully agree with others. Do the math, check your market, check your team skills, check your needs. Ignore buzzwords and shiny new toys just because … Maybe if you invest 25% of what you plan to spend on moving, to improving, rewriting and optimising, you would get much better result