3 ms·
Well if that's what they did, then then using NATS over HTTP in that scenario is just switching a single point of failure for two single points of failure with
by tinco 3y ago
Well if that's what they did, then then using NATS over HTTP in that scenario is just switching a single point of failure for two single points of failure with no feedback on the second point, did they just pick it for the convenience of the NATS interface and only later realize their mistake?
- emmanueloga_ 3y agoI’m guessing they realized late that core nats is a message broker without features like durability and at least once delivery. Jetstream was released less than a year ago (in nats 2.2) so perhaps by the time they made the switch it was not an option.
- caleblloyd 3y agoNATS 2.2 with initial JetStream support was actually released 3 years ago.