Happy Learning 👍

Happy learning 👍

👍

It should have worked for multipart as well... Need to see the code to be able to see the issue.... For multiple filters there is ordering among filter, by default some order gets applied, to customise this @order annotation can be used

@@codefarm0 it didn't work for multipart, it kept telling me that some of the data that was in the form was lost so it never made it to the controller. I was using multiple filters and both were making a copy of the request, however, in some instances the response was lost and never made it to the client. Can we debug on the weekend or when are you available. I'm open to buying coffee of it works.

👍

GitHub Code please

Yup... Will be covering in next videos

Restarted the ide?

Hi, thanks for taking out time to put this, really appreciate that.... By the way why do you think it's not design but concept?

@@codefarm0 I thought you would be designing it, like we do in System Design interviews. Having Redis, how you store the counters and some pseudo code. I would suggest you to create one more video on that. 1) Design Concepts/Considerations for Rate Limiter 2) Designing/Implemeting Rate Limiter using Redis/Or Whatever

Okk.. now I see that. Thanks ..will be covering those in upcoming weeks.

Sure Srikanth...thanks ❤️

the producer is typically not directly aware of whether a consumer has successfully processed a message. Kafka's design decouples producers and consumers, allowing them to operate independently.

@@codefarm0 I did some more reading. The consumer sends a failure event which makes the producer resend the message ( retry functionality ). Its still half baked knowledge in my head, the learning is still on. Thanks anyway. Nice content.

that retry mechanism is there on producer side, Kafka broker sends acknowledgements to the producer, that's how producer is sure that message has been sent to Kafka Topic. But once kafka has ackowledged the receiving of the message then its upto consumer to process the message correctly, at consumer end also retry mechanism is implemented, if all retries gets exhausted, the message is sent to DLQ for later processing.

In case if you interested there is one video i had created a while back on kafka producer/consumer- kzbin.info/www/bejne/emfNm6mqnbWpZ6Msi=Wq61lKTei8NnoCCm

@@codefarm0 Thanks will go through it

You can add that in request and response objects...that will be passed on

@@codefarm0 thanks it works when I add it to the request and response wrapper's headers. Can I also add something to the input stream/req body?

Yea that can be done too. have you tried something around it?

@@codefarm0 yep, so I coverted the stream to json depending on the uri and then wrote to it and reconverted it back to stream. Afterwards I set the value or I set the byteArray then back to ServleInput stream. Finally passed it to the filter chain, Is that correct?

@ianwanjala8621 as long as it's working correctly should be fine...but changes in streams should be done carefully and well tested before putting to prod

Glad it helped. Check this one too which is latest on the same topic - kzbin.info/www/bejne/ipSWm39qorNsoac

Thank much Srikanth 🙂

Sure Srikanth.. many videos are scheduled from today in this series

Glad you like them!

Let me take a look..will respond as soon as I able to replicate this

Please check this video, i think you should get the answer kzbin.info/www/bejne/iZPYgYGOjduHgKMsi=Ubuozr84GYF9XcL3 If not please let me know

Difficult to tell without looking at code.Can u pls share the test code

can you share more details?

lets connect over linkedin

Let's connect at www.linkedin.com/in/arvind-kumar-108a4b2b/

Happy to hear that. Thanks @maan9011

Thanks Abhinav for checking out. What resources?? Can u please be specific