Nearly every ambitious person I know who has dived into AI is working harder than ever, and longer hours than ever.
Fascinating dynamic tbh.
I have NEVER worked this hard, nor had this much fun with work.
NATS 2.12 is here! Love seeing how NATS keeps pushing the boundaries of messaging.
Atomic batch publish + delayed scheduling are game-changers for real-world apps.
Congrats to the team! πππ
π NATS Server 2.12 is officially here!
More performance. More resilience. More possibilities.
β¨ Atomic batch publish - no more partial commits
β° Delayed message scheduling - schedule messages for later consumption
π’ Distributed counters with unlimited size (https://t.co/QgbcnqmwkY support!)
π― Prioritized pull consumer policy for fast failover
π Mirror promotion for disaster recovery
π‘οΈ Offline asset protection during downgrades
Ever wondered how to extend NATS clusters across different networks or edge locations? With NATS Leaf Nodes - a powerful way to bridge local and remote NATS systems! Let's dive in π§΅ #natsio
Had the same experience so far:
- It's burning reasoning tokens for even small code changes
- It's feels generally slower than Claude (due to long thinking)
- Sure, it's cheaper, but the results are not "life changing" as often described
- Will stick with Claude Max for sure
Had the same experience so far:
- It's burning reasoning tokens for even small code changes
- It's feels generally slower than Claude (due to long thinking)
- Sure, it's cheaper, but the results are not "life changing" as often described
- Will stick with Claude Max for sure
π£ New blog post: NATS 2.11 introduces consumer pausing! βΈοΈ
Temporarily halt message processing for maintenance or bug fixes without losing state. Link to the blog post down below β¬οΈ
#nats#natsio#jetstream