> Is there a good reason why everyone seems to be using rabbitmq? it simply does work, has extensive language support (client packages), plenty of good documentation
having worked on & maintained & architected 5 different social backends and failed at 4 of them, here are my key take aways; data storage: * keep data structure as simple as possible, * do not go with the hypes, stick…
it is like NATO :)
it is like TL:DR for "Systems Performance" book :)
i had the same history with neo4j
if you plan to grow with it, i strongly advise you to battle-test it...
are you using it for production purposes or for your small projects? if it is for production, how is your read/write performance?
> Is there a good reason why everyone seems to be using rabbitmq? it simply does work, has extensive language support (client packages), plenty of good documentation
having worked on & maintained & architected 5 different social backends and failed at 4 of them, here are my key take aways; data storage: * keep data structure as simple as possible, * do not go with the hypes, stick…
it is like NATO :)
it is like TL:DR for "Systems Performance" book :)
i had the same history with neo4j
if you plan to grow with it, i strongly advise you to battle-test it...
are you using it for production purposes or for your small projects? if it is for production, how is your read/write performance?