Data Lake Strategy via Data Mesh Architecture at JPMorgan Chase; Data Mesh Learning Meetup

Поделиться
HTML-код
  • Опубликовано: 26 дек 2024

Комментарии • 10

  • @NavaShanker
    @NavaShanker Год назад +1

    Where common data which is shared across multiple domains will be stored in data mesh architecture?

  • @ravindranagvekar1667
    @ravindranagvekar1667 2 года назад

    Mesh need to show multiple domains(Data Products) connecting to central hub?

  • @harold3167
    @harold3167 3 года назад

    Hi Arup, is the, or should the, Data Ingestor, be centralized or federated when it comes to ingesting the data [or products] from the various producers? Similar question in regard to the Router? - Thanks

    • @datameshlearning
      @datameshlearning  3 года назад

      They talk more about this around minute 59 that might help you understand it further.

  • @ziadirida
    @ziadirida 2 года назад +1

    Not very convincing. But a lot of good ideas. Hope it works for you. Let us know

  • @jairamram9225
    @jairamram9225 3 года назад +2

    I hope Zhamak does not watch this. This is completely the opposite of what she is suggesting.

    • @zielxxc
      @zielxxc 3 года назад +2

      The presented approach is not necessarily wrong, it is just very AWS centric as it relies on AWS for data catalog and access control to satisfy the data mesh principle of Federated Computational Governance. A more complex hybrid multi-cloud environment will need a more generic solution.

    • @mmcwalter
      @mmcwalter 2 года назад +1

      This is actually 100% aligned with Zhamaks vision.

    • @datameshlearning
      @datameshlearning  2 года назад

      I have no idea where you are getting that...

    • @datameshlearning
      @datameshlearning  2 года назад

      @@zielxxc yes, they came out with an AWS offering from JPMC. JPMC also cannot talk about any other vendors they are using. If you notice the way they talk about AWS Glue, it is clear it is not the actual data catalog they use for most of their use case but JPMC has weird communications rules :(