The Rise of Hybrid PHP: Blending PHP with Go and Rust
yekdeveloper.com
The Rise of Hybrid PHP: Blending PHP with Go and Rust
1–10 of 158 posts
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#2Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#3I bit the bullet rewriting my app from PHP to Go and it paid off for my company, we're talking 20K lines of PHP code, reduced to 4K lines of Go and with the added efficiency gains with it.
I think some orgs just need to take the jump and plan a rewrite, add tests (easier with Go) and just do this if they are a PHP shop, I would say it's worth it.
Instead of blending Rust/PHP or Go together and having an unmaintainable mess of a codebase.
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#4It turned out that dlopen was the "microservice" architecture we needed all along.
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#5> In short, the modern PHP ecosystem gives us the best of both worlds: the ability to build quickly and confidently in PHP, while still having powerful options (C, Rust, Go) for performance-critical parts. This hybrid approach lets us stay productive without sacrificing speed where it matters most.
I understand this for a large codebase where rewriting is not feasible.
But if that wasn't the case, a C# APIs achieves both speed of development and execution in my experience. You'll rarely need to reach for C++ or Rust.
PHP is great but the language still doesn't allow things like typed arrays. It will happily accept string in a array of dates, for example.
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#6I bit the bullet rewriting my app from PHP to Go and it paid off for my company, we're talking 20K lines of PHP code, reduced to 4K lines of Go and with the added efficiency gains with it. I think some orgs just need to take the jump and plan a rewrite, add tests (easier with Go) and just do this if they are a PHP shop, I would say it's worth it. Instead of blending Rust/PHP or Go together and having an unmaintainabl…
But the question always is: was the rewrite the reason for the gained efficiency, or the new language?
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#7> In short, the modern PHP ecosystem gives us the best of both worlds: the ability to build quickly and confidently in PHP, while still having powerful options (C, Rust, Go) for performance-critical parts. This hybrid approach lets us stay productive without sacrificing speed where it matters most. I understand this for a large codebase where rewriting is not feasible. But if that wasn't the case, a C# APIs achieves…
> It will happily accept string in a array of dates, for example
While completely true, you are using static analyzer anyway which won’t let you do this.
The generics support will likely come in the near future, there has been momentum in it again: https://thephp.foundation/blog/2025/08/05/compile-generics/
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#8Good to see PHP still trucking.
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#9> In short, the modern PHP ecosystem gives us the best of both worlds: the ability to build quickly and confidently in PHP, while still having powerful options (C, Rust, Go) for performance-critical parts. This hybrid approach lets us stay productive without sacrificing speed where it matters most. I understand this for a large codebase where rewriting is not feasible. But if that wasn't the case, a C# APIs achieves…
> It will happily accept string in a array of dates, for example While completely true, you are using static analyzer anyway which won’t let you do this. The generics support will likely come in the near future, there has been momentum in it again: https://thephp.foundation/blog/2025/08/05/compile-generics/
I'm working in PHP for about 15 years by now, and for about 10 of them I was promised generics. In favor of your health, don't hold your breath.
Re: The Rise of Hybrid PHP: Blending PHP with Go and Rust
#10I bit the bullet rewriting my app from PHP to Go and it paid off for my company, we're talking 20K lines of PHP code, reduced to 4K lines of Go and with the added efficiency gains with it. I think some orgs just need to take the jump and plan a rewrite, add tests (easier with Go) and just do this if they are a PHP shop, I would say it's worth it. Instead of blending Rust/PHP or Go together and having an unmaintainabl…
But the question always is: was the rewrite the reason for the gained efficiency, or the new language?
Both.
Go made this worth it and it also was easy to hand over to another experienced developer.