How BILLION-Scale Microservices Actually Talk: REST vs Async Messaging

Regular viewer of ur channel bro🔥🔥🔥

Suggestion, place make a video how cloud actually works, from the basic hardware level to giving console to the consumer.

Again, full of information and amazingly described. Thank you.

Just wrapped up working with sockets — now diving into the asynchronous side, and it's really sparked my curiosity!

Great work keep it up. Really helped in understanding system design.

What is the RabbitMQ equivalent to sharding/partitioning?

Pushing the algorithm ❤

bump for algo <3 no other channel teaches like you do

Make video on how nse stock exchange architecture their system fast and high changes of availability

Make architecture video on stock broker also how they process and how fastest

In few service designs, where the number of requests go upto 2-5 millions per service per hour, the event broker services have been found to be straining to keep up. Now, I'm talking about Azure based services, not Kafka specifically.

I want to ask, how do you handle such systems when broker services strain under their limitations?

Great video !! This was exactly asked for VP position interview

Make a video on how to handle 100000+ requests per second with ngnix and roadrunner for php

Great video like always! I am a developer with around 1 year of experience and such content is helping me gain an edge of around 2-3 years. I could scale my current salary by 150% all thanks to the stuff I have learnt from your channel. Thank you so much.

thanks for this high quality content

Transactional Outbox pattern question-
createOrder event->Order Service

OderService->transaction(update db, publich event for downstreams)

Lets say the transaction failed, the application state is safe and order did not get created.

But the createOrder event is now lost, as due to user facing respond early , user thinks order is already created. How do we handle such cases?

One think comes to mind is having a dead letter queue and storing messages which were not processed successfully there. But the issue still remains the user is still under the impression order got created. Now when user comes back he sees that order is not there. So respond early did not value addition. Instead the user should be seeing a transient state of "Order being placed, please check back after some time for updated status" so that user is not misled.

But here the issue is in transactions which involves payment and other background flows the user will not be happy with a transient state. How do we solve this?

magnificent...

Great videos but I think you lack engaging voice. Engaging voice will make the videos even better.

All technology is created in response to problems that cannot be handled by existing systems. That's why it's important to have at least some knowledge—you can learn more when problems arise. Nowadays, you can easily find strategies using AI models.
But the way of presentation is good

thanks

please more video about spring