You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm honestly really like this project as it's fast and simple. But I'm still a bit reluctant in using it as the replacement for my current Redis pub/sub setup. It'll be quite helpful if there is a perf comparison with Redis pub/sub.
One more issue is that, as I'm planning to use it on production, I'm a bit afraid of this project being abandoned.
The text was updated successfully, but these errors were encountered:
Hi!
I successfully replaced Redis for RPC purpose, it's in production since 2019, works quite stable.
ijson is not designed for PUB/SUB initially (though it can do it), so redis/rabbit is faster in bunch mode for PUB/SUB (when a few events are sent as one network package) when ijson works via http and every event are sent as separate network package.
But if your communication is not "bunch-oriented" (e.g. many prodicers/many consumers or RPC mode) or if you make manuall bunching, then ijson will be faster. I'm not going to make new benchmarks for now due to limited to time.
being abandoned
any project has such risk, but ijson has one advatage - it's small, so it's easier to fix or start mantaining.
Thanks for your detailed explanation. As I'm using redis pub/sub for broadcasting messages among websocket servers then I think I will still have to stick with Redis. It would be nice if ijson considers optimizing the pub/sub mechanism in the future.
I'm honestly really like this project as it's fast and simple. But I'm still a bit reluctant in using it as the replacement for my current Redis pub/sub setup. It'll be quite helpful if there is a perf comparison with Redis pub/sub.
One more issue is that, as I'm planning to use it on production, I'm a bit afraid of this project being abandoned.
The text was updated successfully, but these errors were encountered: