how we can give digining answers
Answers
Explanation:
sorry i think you typed wrong the question must be like
how can we give designing answer ?
the answer is
1. Practice with colleagues
Although it is possible to study system design independently, colleagues can make your prep much easier.
Colleagues often read different articles and handle different systems. As design is a subjective topic, a different perspective really opens your mind to a variety of solutions and pitfalls.
Your best bet are the seniors. Don’t tell them you are moving though.
2. Prepare from the best
Interviewer: “We want high consistency.”
Candidate: “I could use consistent hashing.”
Interviewer: "That doesn't guarantee consistency."
Candidate: “…”
Too many candidates read 3 articles before heading straight to the interview. This means they have very little space to work with when under pressure.
Companies post tons of stuff about their software’s architecture. Check out the links at the end of the answer. Stuff like Kafka and Cassandra are both examples of great engineering, and abstractions you can use later.
Also, use standard shapes while drawing.
3. Be flexible to changing requirements
Interviewer: “How will you reduce the latency?”
Candidate: “I could scale horizontally.”
Interviewer: “Wouldn’t that make the system more complicated?”
Candidate: “...Could I scale vertically then?”
Interviews often start somewhere and pivot dramatically. This is a good test of the candidates flexibility to changing requirements. A lot of people get stuck here.
Of course, the ideal situation would be to prepare so well that everything moves smoothly. But if you are in a corner, don’t go gently into the night. Roll with the punches.
4. Abstract components
Draw the block diagram of the overall system with the important components abstracted. They change as the interview progresses, so leave some space around them.
Use abstractions like message queues, load balancers, distributed consensus etc… to express yourself quickly and precisely. This saves time and looks impressive.
As long as you don’t mistake consistency for consistent hashing…
5. Focus on features
Make sure you are heading somewhere with your change. Consistency and availability don’t mean a thing if your user leaves. So ask yourself every time you add a component: Will this help me in the long run?
Engineers like scalable systems. They love their jobs even more.
———————————————————————————————————
hope you gotcha
purple you armies
✌❤
Answer:
Your answer is in above picture
see the above picture and follow these steps
Hope it help you ✌✌✌
Explanation:
❤Happy 6th day of navratri❤
☺जय स्कंदमाता☺
❤जय मां कुष्मांडा❤
❤Jai mata di ❤
❤jai maa durga❤
❤jai maa kali❤
❤jai maa Laxshmi❤
❤jai maa Sarwasti❤
☺जय सकंद माता☺
Once again ❤HAPPY 6th day of navratri❤
