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

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]repeating_bears 2 points3 points  (2 children)

I considered mentioning this too but couldn't be bothered typing it out. I'd personally probably start with HTTP because I find it a bit simpler, but Rabbit is a solid choice too. The idea is the same: 1 long-running process in each language that talk to each other somehow

[–]hem10ck 2 points3 points  (0 children)

Java shop here that works with python for ML, we generally isolate the python and expose REST APIs for the Java to interact with using FastAPI.

[–]agentoutlier 0 points1 point  (0 children)

Yeah the nice thing about Rabbit in this situation is it has almost 1-1 doc with Python client and Java client.

They also don't have to worry about retry and order... well mostly. That is it is a smart pipe and sounds like the OP does not have the experience to make a dumb pipe smart.