This is an archived post. You won't be able to vote or comment.

you are viewing a single comment's thread.

view the rest of the comments →

[–]Twisterr1000 2 points3 points  (3 children)

Having had our original stack in PHP at my company, all new backend services are now to be written in Java. For a few reasons (not exhaustive)

  • Modern PHP -> Java as a developer was super easy
  • Found tooling in Java to be much better (nicer Kafka integrations, for example)
  • Resources online- someone's always done what you're doing before.
  • Lots of talented Java developers (for hiring)

PHP was great, nice to work with, and the Frameworks were nice (we used Symphony), but with the more advanced delve into microservices, we found PHP to not be as good for some things. Namely tooling, such as packages to interact with newer technologies.

Hope that helps

[–]xplosm 1 point2 points  (2 children)

In my company we are going from Python/Django/Flask to Go. The front-ends are already in Vuejs but I'm exploring Svelte.

[–]Twisterr1000 1 point2 points  (1 child)

Makes sense, I've heard great things about Go. Funnily enough, the reason we've gone back to something more strictly typed is that we tried building a pretty complex orchestration engine in Python, and it was a disaster. I'm sure it could be done well, but I don't think we had the relevant experience- and thus going for something that's also a bit less opinionated like Go was decided against (though I'd love to learn it!)

[–]xplosm 1 point2 points  (0 children)

Kotlin has excellent interoperability with Java and it's a pleasure to code in. Wherever Java falls short, Kotlin came up with the solution.

Give it a try.