Kafka Crash Course in One Video | Kafka in Microservices | Spring Boot | Producer | Consumer
Vložit
- čas přidán 13. 01. 2023
- Kafka Crash Course in One Video | Kafka in Microservices | Spring Boot | Producer | Consumer |EnggAdda |@enggadda
#apachekafka #kafka #kafkabasic #kafkatutorial #kafkaforbeginner #springboot
GitHub Link for Publisher :-github.com/EnggAdda/KafkaPubl...
GitHub Link for Consumer :-github.com/EnggAdda/KafkaCons...
please make a video on how to produce json string and consume it how we can use object mapper and persist it in db using jpa methods
Sure,will cover that
please a video about kafka dealing with data, that's what i'm looking for, for a while
Sure ,looking for that
Sir ActiveMQ, RabbitMQ crash course waiting...
Sure will do
Start angular tutorial with project
I am not sure now but will see in coming months
Sir if u don't mind I wanted to know what is ur reefeereence to make the videos . text book or other course or video references?
Mainly uses online reference like popular sites ,blogs ,books and videos
Junit mockito crash course please
sure will cover that in future
Suppose I have a spring boot application which is having multiple instances running (lets say 3 instances are running), and I have a scheduler which is suppose generating a report after every 1 hour, so now my scheduler will start generating the same report for every instance of my application (so it will generate 3 report in total) and which is a wrong thing, so how can we handle such scenario. How to make our scheduler generate only 1 report even if 3 instances are running.
Today an interviewer asked this question to me and I was clueless about it. Pls help.
One way to handle this scenario is to use a distributed lock mechanism, such as using a distributed lock service like Zookeeper or Redis. This will ensure that only one instance of the application can acquire the lock and execute the scheduled task, while the other instances will skip the task until the lock is released.
Another way to handle this is to use a load balancer to direct all requests to a single instance of the application, so only one instance will execute the scheduled task.
Alternatively, you can use a database to track the execution of the scheduler, if the task is already running on one instance, other instances can check the status and skip the execution.
Sir please provide git hub link of every video
Mentioned that in description, please check out .