{"repo":"mookid8000/Topos","free":true,"listed":false,"github":"https://github.com/mookid8000/Topos","clone":"git clone https://github.com/mookid8000/Topos.git","description":":cyclone: .NET Event Processing library","language":"C#","stars":25,"topics":["kafka","azure-event-hubs","azure-eventhub","kafka-consumer","kafka-producer","event-driven","log-broker"],"license":"MIT","category":"data-pipelines","readme_excerpt":"Topos It's something with topics. Producing messages Could e.g. be Apache Kafka, where we send a JSON-serialized message: Let's go through the different configuration parts: Consuming messages Let's also use Kafka to consume messages... the configuration is probably not that surprising to you, it's just Configure. and then let the fluent API guide you. Check this out - here we set up a corresponding consumer that just prints out the contents from the received messages: Let's go through the configuration again:","default_branch":null,"files":null,"tree":[],"storefront":"/r/mookid8000","claimed":false,"request_supported":{"post":"https://gitbuyer.com/r/mookid8000/Topos/request-supported","requests":0},"note":"indexed from public GitHub; nothing is for sale on this page. Clone it from GitHub. Paid listings live at /search."}