as software engineer , I am still on my first job and have been working as full stack developer for 8 months now. 70% of our job are based on the backend with springboot and java . 30% on the UI I really really like this video. I just went over our design docs for all the services and now understand why some services are sometimes affected but others no. thanks what are your best tips and tricks for someone starting out his career as self taught developer. I really love backend than frontend because It really challenges me . thanks anyway
Hi Yogita, the way you explain the topic is awesome 😎. Do you have plan to talk about the Clean Architecture which quite common now a days. I just want your thoughts on it and anticipated the way you will explain would be unique. Thanks.
Helo mam, I am a bca student I want to do omscs program from Georgia Tech, But my I have 3 years bachelors degree and Georgia Tech wants 4 years, so how can I pursue that program, if you have any suggestion for me please suggest me mam. Please reply
I am working with Spring Boot to develop microservices. We want to asynchronously integrate the services so they are decoupled and we can add new services in the future. However, we are struggling with dealing with error cases. Are there any libraries in the Spring ecosytem that help with this? We are specifically struggling with event ordering, idempotent event handlers, and retrying failed event and eventually putting them into a DLQ.
This is an old question. I am going through video and do have some experience working on microservices. A lot more detail is required to accurately answer the question. But here are my high level thoughts. Challenges: 1. Error Cases : Note down different scenarios of what can go wrong. Now group them into where you want to handle those, so retires and jitters. And those that are service level faults where you can either drop that request or allow client to retry later like pushing the message into DLQ as you have suggested. 2. Your requirement for the systems are : - decoupled - you need event ordering - idempotent event handlers - retries - eventually putting off into DLQ to be handled later. This is a common use case for async system integration. In AWS ecosystem you can use FIFO Queues with their handlers implemented in idempotent way. This will give you ordering, you can add idempotency using either the queue message id or adding it to your handler with id generation and storage. hint : java UUID with key value store. You can add retries in your handlers. Also it gives good integration with DLQ. You can define like visibility time for the message, number of retires.
as software engineer , I am still on my first job and have been working as full stack developer for 8 months now.
70% of our job are based on the backend with springboot and java .
30% on the UI
I really really like this video.
I just went over our design docs for all the services and now understand why some services are sometimes affected but others no.
thanks
what are your best tips and tricks for someone starting out his career as self taught developer.
I really love backend than frontend because It really challenges me .
thanks anyway
Thanks to explain what is Microservice in very simple language.
Thanks for the explanation, looking forward to see more such videos about microservice. thanks again
A very Great High-Level Explanation. Thanks very much, ma'am.
Nice job you helping engineer and student for sharing knowledge
Great video for freshers
Hi Yogita, the way you explain the topic is awesome 😎. Do you have plan to talk about the Clean Architecture which quite common now a days. I just want your thoughts on it and anticipated the way you will explain would be unique. Thanks.
💕💕💕💕 Love Love Love from core of my heart mam. Very Nice explanation with clear presentation
Thanks so much I'm waiting this in your channel
Excellent explanation.
Please keep continuing microservices concept completely
Yogita well explanied thanks alot for the amazing time u investemented to share with us👍🏻waiting for the next video👍🏻
Waiting for next part to get deep into communications between Microservices
Thank you very much
I did not find the link to the book "Domain Driven Design". Can you please share the link?
Hello Yogita mam. Please create one video for cracking the technical interview on Microservices and Spring with AWS Architecture.
Valuable content, thanks!
Beautifully explained as always!
👍👍 Good day greetings
Yogita nice job
Thanks
Helo mam,
I am a bca student
I want to do omscs program from Georgia Tech,
But my I have 3 years bachelors degree and Georgia Tech wants 4 years, so how can I pursue that program, if you have any suggestion for me please suggest me mam.
Please reply
How to solve distribution database problem?
Please complete others parts asap
Make more videos on microservices
I am working with Spring Boot to develop microservices. We want to asynchronously integrate the services so they are decoupled and we can add new services in the future. However, we are struggling with dealing with error cases. Are there any libraries in the Spring ecosytem that help with this? We are specifically struggling with event ordering, idempotent event handlers, and retrying failed event and eventually putting them into a DLQ.
This is an old question. I am going through video and do have some experience working on microservices. A lot more detail is required to accurately answer the question. But here are my high level thoughts.
Challenges:
1. Error Cases : Note down different scenarios of what can go wrong. Now group them into where you want to handle those, so retires and jitters. And those that are service level faults where you can either drop that request or allow client to retry later like pushing the message into DLQ as you have suggested.
2. Your requirement for the systems are :
- decoupled
- you need event ordering
- idempotent event handlers
- retries
- eventually putting off into DLQ to be handled later.
This is a common use case for async system integration. In AWS ecosystem you can use FIFO Queues with their handlers implemented in idempotent way. This will give you ordering, you can add idempotency using either the queue message id or adding it to your handler with id generation and storage. hint : java UUID with key value store. You can add retries in your handlers. Also it gives good integration with DLQ. You can define like visibility time for the message, number of retires.
Waiting for your 1Lakh subs 🙂
👏
Want to see Bilal Abbas and Sehar khan together in a drama.
A poorly structured material
just create your youtube and help others
you should be thanksful for people who spent time creating things to help others completely for free
Toh tu jaake bana apna material! Aur khud ka profile pic tak nahin hai aur bada aaya idhar bhaunkne
Create your own stuff and then complain
Are yıu hindu