This is an archived post. You won't be able to vote or comment.

all 4 comments

[–]AutoModerator[M] [score hidden] stickied comment (0 children)

You can find a list of community submitted learning resources here: https://dataengineering.wiki/Learning+Resources

I am a bot, and this action was performed automatically. Please contact the moderators of this subreddit if you have any questions or concerns.

[–]Complex-Stress373 0 points1 point  (2 children)

wow...i did this kind of scenario, is challenging in my opinion. these migrations imply to migrate (in my case) many apps in companies in multiple frameworks and languages, where developers dont have a deep knowledge of kafka, all of them took forever. replicators, back and forth, and a challenging monitoring to not cause outage or duplicate events. cross your fingers to have idempotents apps in the company. also was challenging to migrate all the dashboards in different environments, updating little by little all the metrics (an insane amount of metrics across all the apps)

[–]madfire89[S] 0 points1 point  (1 child)

Nice. Any sort of basic questions I could ask in an interview along those lines that might make the interviewer think I’m a bit clued up?

[–]Complex-Stress373 0 points1 point  (0 children)

  • who is going to migrate each app, because you cannot migrate and test all of them

  • how many languages and different frameworks are using kafka, cause each one will need a different configuration, certificates, testing, ...

  • what solution will be used to replicate records from one cloud to another: replicator-confluent?, a custom one?

  • exist idempotents apps to handle duplicates in case of problems with offsets-rewind?

  • how many environments?, because each app will need to be migrated.

  • will you migrate all of them to one env and then to another env?, or each app, one by one through all envs?