Release v0.3.0

[alvin-reyes]

What's Changed

• reverted code to use direct FindInBatches call by @jlogelin in reverted code to use direct FindInBatches call #745
• use debug level for logging this message by @snissn in use debug level for logging this message #748
• refactor to use nsq and websocket by @en0ma in refactor to use nsq and websocket #744
• dont silent pin dequeue errors by @en0ma in dont silent pin dequeue errors #749
• Refactor pin estuary native: part 1 by @anjor in Refactor pin estuary native: part 1 #746
• make sanity check more deterministic by @en0ma in make sanity check more deterministic #750
• Bump github.com/ipfs/go-bitswap from 0.10.2 to 0.11.0 by @dependabot in Bump github.com/ipfs/go-bitswap from 0.10.2 to 0.11.0 #751
• Prevent duplicating last batch in each batched append pattern by @neelvirdy in Prevent duplicating last batch in each batched append pattern #754

Full Changelog: v0.2.5...v0.3.0

---

This discussion was created from the release v0.3.0.

[alvin-reyes]

This is the first release that we will provide an option for estuary app owners to use a QUEUE instead of an RPC communication protocol between the API and Shuttle nodes. For more information about the difference, you can read up the following article here: https://particular.net/blog/rpc-vs-messaging-which-is-faster#threads-and-memory

Add the following flags on the API and Shuttle node

--queue-eng-enabled --queue-eng-host=ip:4150 --queue-eng-consumers=1

Current estuary configuration:

--queue-eng-enabled --queue-eng-host=<queue IP>:4150 --queue-eng-consumers=3

[MatiasDiazDamian]

Hi. Sorry for the mistake but I haven't texted you. El jue, 29 dic 2022 a las 11:04, Sergio Corzo ***@***.***>) escribió:

…

Hi. You texted me. I'm interested. — Reply to this email directly, view it on GitHub <#755 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AWM3LWGFOTMNB6WVH3NLKNDWPWK7RANCNFSM6AAAAAAS4HUNC4> . You are receiving this because you were mentioned.Message ID: ***@***.*** .com>