Closed wulonghui closed 10 years ago
NATS does not implement persistence, and is not in the design of the system. After 20+ yrs of building messaging systems, I think persistence and transactions lead to anti-patterns. In that regard, NATS is a fire and forget system only. If you believe persistence is required, an enterprise messaging system like TIBCO's EMS, or RabbitMQ may be better suited for you.
On Mon, Aug 4, 2014 at 12:57 AM, Tim Wu notifications@github.com wrote:
Does gnatsd support messaging persistence, if not, how can I implement it.
— Reply to this email directly or view it on GitHub https://github.com/apcera/gnatsd/issues/38.
Thanks very much.
@derekcollison can you please point me to some documentation about it? I would like to know if that is suitable for my use case and how persistence could land in bad design in your experience. Thanks.
@mastrolinux Documentation regarding which portion? Persistence?
no, about: "I think persistence and transactions lead to anti-patterns". How did you get this idea? I am curious and want to know more info on why there is the risk you mentioned.
Short answer is 20+yrs of building messaging systems and distributed systems relying on a messaging backplane. Many times too much emphasis is placed on the transactional or persistent nature of said systems when they could have been either avoided all together at much higher performance and lower cost, or they could have been designed better at the endpoints, etc to better fit the business requirement.
Thanks a lot for your help. This is a plus for gnatsd in our product comparison to choose the right technology for our usescase.
Does gnatsd support messaging persistence, if not, how can I implement it.