Apache Kafka in 1 hour for C# Developers - Guilherme Ferreira - NDC London 2023
HTML-код
- Опубликовано: 6 окт 2024
- Are you curious about Apache Kafka? But you never had the time to dig into it?
No problem. In this session, we will dig into it. In under 60 minutes, we will learn basic concepts and write our first Kafka application using C# and KafkaFlow, an Open Source framework for .NET.
Even if you know nothing about it, you can expect to go home with the basics to start your Kafka journey.
Check out our new channel:
NDC Clips:
@ndcclips
Check out more of our featured speakers and talks at
ndcconferences...
ndclondon.com/
Great talk, my mind finally clicked what kafka is, thank you!
WOW! So happy with it! Glad it helped.
Great talk, following along was so easy. Loved the bookmark example.
That's really valuable feedback! Thank you, Karan 🙏
Thank you for a great talk!
Excellent, will definately be looking to use Kafkaflow.
Brilliant! Let me know if you need any help.
Great talk!
Thanks Gustavo!
I'll have to pop out some lovesongs then
Finally, some serious competition!
Thanks for all the information, It was very helpful..
I have multiple scenarios where I don't know if Kafka can solve...
1. how do you update services (that use internal cache on startup) to get updates when running in case you have multiple instances? (using groupId - you will need to manage those groupIds).
2. If I will use a topic to send messages out to my clients ( I want to make sure that my client will get them.. and he isn't offline) how can you ensure that (is there a peek and ack for bulk messages by ClientId or something- that will save the order of messages for each client?
Hi! Thanks 🙏
Regarding your questions:
1. Each service would need to be a consumer with a distinct group ID (like a GUID-generated one). However, I think it's worth considering using a shared cache like Redis.
2. You can have a client-specific topic. Then, you can use Retry Policies to ensure that they are delivered. KafkaFlow has an extension for that. Search for KafkaFlow.Retry.
Great talk! However I always get confused between Topic and Partition. My use case is, every hospital has multiple IOT devices. Every IOT device sends two sets of data points Vitals and Waveform and there are multiple devices in one hospital and there are multiple hospital. Should I creating 2 unique topic per IOT device ?
It's hard to have a strict rule to find topics and partitions. As an example, you can have a topic "vitals" and use one partition per hospital. Or, having a topic per hospital. So, topics are mostly about domain scope, while partitions are mostly about throughput.
Great, thanks! Do you have these projects on Github?
Thanks 🙏 No. They are in fact production code that powers my Patreon. However, most code regarding the Kafka connection is disclosed during the session.
So cool! Shall we connect?
Uhg, the only useful info I get from this talk is that kafkaflow is the good way to start. But as for Kafka itself - brokers, topics, groups etc - the talk does very little in explanation and showing how messages go through the system (it would be nice to see the actual Kafka log timeline breakdown for the demo app)
That’s superb! Let’s connect?
Where is github link?
Gorgeous! Let’s connect?
Legal ver um brasileiro voando.
Eu acho que ele é português
Ele diz que é português em 0:55
@@dbgmitre Confirmo 😉
@@carlinhos10002 os meus pais e o meu cartão de cidadão concordam 😉
Olá Sep! Não sou brasileiro, mas partilhamos o idioma. 🇵🇹 🇧🇷
Konrad Siuda is now famous 🤣
Extreme red shift makes this unwatchable for me.
😞 Sad to hear that. Is it because of the annotations?
Nice! Let’s be friends?