Extend your NATS Cluster with Leaf Nodes | Rethink Connectivity Episode 7

Поділитися
Вставка
  • Опубліковано 19 лис 2024

КОМЕНТАРІ • 16

  • @michaelgrauvogl689
    @michaelgrauvogl689 2 роки тому +1

    great examples from practice. Thanks!

  • @NaveenSiddareddy
    @NaveenSiddareddy Рік тому +1

    read replica only? can the leaf write?

  • @LM-hc3ty
    @LM-hc3ty Рік тому +1

    Thanks for the demo. In the beginning of the video your diagram showed key-value stores being replicated to the leaf nodes, but you did not cover this in your presentation. It seems replicating KVs is not as straight forward as regular streams - is it even possible? We were hoping to use leaf-nodes and KVs and have leaf-nodes update values in KVs that would then be updated in the cluster. Hoping you can shed some light on this.

    • @SynadiaCommunications
      @SynadiaCommunications  Рік тому +3

      Hey! It is possible to do but a bit cumbersome. We have some features coming in NATS server 2.10 that will make this much easier to do

    • @__hz__6983
      @__hz__6983 2 місяці тому +1

      @@SynadiaCommunications I'm interested in this too, is there a recent example with v2.10 features you mention?

  • @jaysistar2711
    @jaysistar2711 Рік тому

    I want to understand JetStream domains better. Let's say that I have images generated by a disconnected leaf (like a car). When the leaf regains connectivity, I'd like the images to be copied to the cluster in the cloud, which is used by a global website. However, I also have local apps in the car that will want fast access. How would this setup be configured?

  • @МаксимПоляков-ъ3г

    Looks great.
    Would be nice to show example with strict security when leafnode cannot query all subjects with global js-domain. Only specific. Or maybe it is show in some other videos.

  • @BZValoche
    @BZValoche 10 місяців тому

    Trying to connect a leaf node between 2 cluster. Both in operator mode. Cluster A is source, cluster B is leaf. The remote nodes declaration require an account nkey in order to establish the leaf connection.
    The nkey is verified in cluster A, but unknown in cluster B.
    If a configure the cluster B's nkey, then verification failed in cluster A. WTF ?

    • @BZValoche
      @BZValoche 10 місяців тому

      Ok found it. Requiring the account key does not imply that I don't need to provide credentials ^^

  • @paularmand4703
    @paularmand4703 9 місяців тому

    bRrrrUp ... sync back up to the cloud. I like that.

  • @enochabassey2786
    @enochabassey2786 2 роки тому

    Super powers

  • @ahmedadly
    @ahmedadly 2 роки тому

    leaf nodes are automagically