mikhailshilkov / mikhailio-hugo

Sources of https://mikhail.io migrated to Hugo
MIT License
12 stars 8 forks source link

Comments to "A Practical Approach to Temporal Architecture" #46

Open mikhailshilkov opened 3 years ago

mikhailshilkov commented 3 years ago

Add your comment to A Practical Approach to Temporal Architecture.

The comments will be displayed directly on the page. I may edit or merge your comments in a non-significant way to make sure they are displayed properly on the website.

jcorremo commented 3 years ago

Hi friend, Thanks for your explanation, now i have an idea of the temporal architecture. I have seen in the temparal docs the posibility that use apache kafka, maybe you know which are the capacity thats enable?. how its interact or how its match with your explanion?.

mikhailshilkov commented 3 years ago

Great question. I haven't dived into this deeply, but I believe Kafka is used as a messaging layer to copy data to ElasticSearch for what Temporal calls "visibility" features - searching for workflows, basically. ElasticSearch and Kafka are optional components and the dependency on Kafka may be removed later on.

mfateev commented 3 years ago

As of Q1 of 2021, the Kafka dependency is fully eliminated from Temporal.

jpza commented 2 years ago

Out of curiosity, what did you use for the illustrations?

hongbo-miao commented 1 year ago

Thanks Mikhail @mikhailshilkov !

After I deploy the temporalio/helm-charts, it has a temporal-admintools

image

I am wondering where it would be sit in the architecture chart.

Where would temporal-admintools be at these among following places?

  1. part of "temporal service" (temporal-frontend, temporal-history, temporal-matching)
  2. outside "temporal service" like temporal-web
  3. somewhere else?
image

Thanks! 😃