Data Consistency | Eventual Consistency | Strong Consistency | Database Pattern for Microservices
Vložit
- čas přidán 4. 09. 2020
- 👉What is Data Consistency?
👉 Data Consistency Models: Eventual Consistency and Strong Consistency
👉 Eventual vs Strong Consistency
Complete video playlist - • Microservices Architec...
Github page for course plan & Other supporting Docs - github.com/greenlearner01/Mic...
To get the notification of every upload on the channel hit the subscribe button and if you found the videos useful press like and share the video with your friends.
---------------------------------------------
Other Videos on the channel that you may like
---------------------------------------------
WireMock - EndToEnd API Testing - • WireMock || WireMock T...
Spring Boot Internals tutorial - • Spring Boot Internals ...
Serialization In Java tutorial - • Serialization In Java ...
RestApi Validation tutorial - • REST API Validation ||...
Redis Cache + SpringBoot tutorial - • Redis Cache With Sprin...
Ehcache + SpringBoot tutorial - • Ehcache with SpringBoo...
Spring Boot Cache tutorial - • Spring Boot Caching ||...
JSON tutorial - • JSON || JavaScript Obj...
Spring Cloud Netflix Ribbon - • Load Balancing In Micr...
Yaml and properties - • Yaml & Properties
Service registry and discovery - • Microservice Registry ...
Distributed log tracing - • Request/Distributed lo...
Communication among microservices using RestTemplate - • Spring RestTemplate
Spring cloud config server - • Spring cloud config
Spring cloud gateway - • API Gateway in microse...
Spring cloud OpenFeign - • Spring Cloud OpenFeign
Hystrix circuit breaker - • Circuit Breaker In Mic...
Resilience4j Circuit breaker - • Resilience4j - Fault t...
Spring Data JPA - • Spring Data JPA
Spring Boot actuators - • Spring boot actuators
-----------------------------------------------------------
Join Us on Social Media -
Facebook - / greenlearner
LinkedIn - / arvind-kumar-108a4b2b
Twitter - / arvind4gl
Quora - www.quora.com/profile/Arvind-...
Instagram - / arvind4greenlearner
Medium - / arvind4greenlearner
#DataConsistency #DatabasePatternsForMicroservices #MicroservicesArchitecture #Microservices #DistributedSystems #MicroservicesInterviews
#MicroservicesGuide #DemystifyingMicroservices #BreakingMicroservices #MicroservicesConcepts #AllAboutMicroservices
Cheers!!
Happy Coding!! - Věda a technologie
Complete Course Plan - github.com/greenlearner01/Microservices-Architecture
Playlist - czcams.com/play/PLq3uEqRnr_2EDsuxPboP9_WtVRR_TaMrF.html
Really amazing stuff. Please upgrade your mic. The sound is of inferior quality which makes video experience a little irritating and hard to understand sometimes. Thanks.
Very good content. Congratulations!
Really a good explanation, only thing the audio could be better.
Anyways, thanks alott
Brother your presentation is very good but please use some good mic next time. It has too much noise in the videos.
In strong consistency even there is possibility if node-3 and Node-5 are down. So what happens in this scenario ? Second question is acknowledge from 2 to 1 and 3 to 2 and so on happens immedately OR first 1 to 2 , 2 to 3 , 3 to 4, 4 to 5 movement happens and then finally 5 to 4 , 4 to 3 and so on... acknowledge happens
Ans#1 - It depends if the node going down is write only node or read only node. If it's read only then shouldn't be much issue other read only nodes can take care of that. But if that node is write only then there is problem and this node is directly connected with the client then those write calls will be failed and there should be some mechanism to handle this.
Ans #2 - It doesn't have to be in sequence it can happen randomly with all the nodes. You should read about "Gossip Protocol" to understand more about this
Hope it helps.
good content ..but audio was not so clear..
The eventual consistacy model you describe is wrong, node 1 can inform all other nodes at the same time, so it is not a chain effect. Meaning all nodes that are up do have said data. When the failing nodes come back up can then be notified of said change and then update. Also your strong consistancy is also wrong as it is still eventual consistancy as other updates can happen whilst that update is happening.
Great explanation, audio is little distrub. Thank you.
Hi Samir, Thanks for the feedback.
What do u mean by audio is disturb? Is it slow or too high??
@@codefarm0 Sometime the voice was breaking in between. It was not smooth thru out.
Thanks Dipti for the feedback. Will double check it for the next videos
@@codefarm0 ok no problem 👍