Porting to a new language is not necessarily a risky thing. If your existing python system communicates with a standard database then you’re in luck. You can pr

Porting to a new language is not necessarily a risky thing. If your existing python system communicates with a standard database then you’re in luck. You can probably get away with running the old system and the new one in parallel. Port bits over piecemeal. I would recommend using a managed language like C# because it is a great all rounder. It is very modern and productive and you will find developers easily. This means the software is cheaper and safer to develop. C# is extremely fast these days and works on Mac, Windows and Linux equally well. Async and channels are easy and a no-brainier to use. Web apis are straight forward to build out. It also scales well when you throw loads of developers and man years at it. I would avoid micro services if your python app doesn’t use them. Building a monolith is cheaper, lower latency and you spend more of your time actually building business logic instead of serialising messages and multi-server dependency chain error nightmares. A 32 core server can do an insane amount work. Especially when compared to running something using python.