I am trying to wrestle through the relationship between eventual consistency and data integrity (as we protect in cyber security). I have this niggling feeling that "eventual consistency" would need *more* than "eventual integrity". (And availability, at least if it is more than recovery from downtime, sounds even more annoying.)
Ah, one of the leading advocates of good old microservices...The horrendous fad that has been the scourge of the internet! This is the worst technical concept I have ever seen in my 35 plus years on the internet. Here is a very partial list of problems associated with microservices. By the way, if you are considering doing microservices with your app-DON'T!: -Compromised security-Greater attack surface -Data inconsistency -Increased complexity -Distributed system challenges -Need for extremely technical software like Kubernetes to manage the pile of hot garbage that was created from the microservice architecture. -Network overhead with gRPC calls that are costly!! -Monitoring complexity
I am a simple man - I see Martin Fowler - I click
I’m currently reading Designing Data-Intensive Applications. It’s a good one.
What were the books you discussed on organizing message systems? I believe the name bobby was mentioned.
Adding Martin Fowler to my very short list of "dudes that can pull off an ascot". Great stuff. Thanks, gentleman.
I AM actually building a key-value database as a project which will have HA at some point. Hence this video :)
First I misread the title as "Patterns Of Disturbed Systems" 😆Enjoyed this episode a lot, as usual, great topic. Looking forward to that book!
I am trying to wrestle through the relationship between eventual consistency and data integrity (as we protect in cyber security). I have this niggling feeling that "eventual consistency" would need *more* than "eventual integrity". (And availability, at least if it is more than recovery from downtime, sounds even more annoying.)
I humbled by these 2 gaints
Thankss!!
0:16 Autotune: ON 🤣
Ah, one of the leading advocates of good old microservices...The horrendous fad that has been the scourge of the internet! This is the worst technical concept I have ever seen in my 35 plus years on the internet. Here
is a very partial list of problems associated with microservices. By the way, if you are considering doing microservices with your app-DON'T!:
-Compromised security-Greater attack surface
-Data inconsistency
-Increased complexity
-Distributed system challenges
-Need for extremely technical software like Kubernetes to manage the pile of hot garbage that was created from the microservice architecture.
-Network overhead with gRPC calls that are costly!!
-Monitoring complexity
Avoid distributed systems.... monolith!? 🧐
A very "theoretical debate" regarding an elevated "ivory tower" problem, related to a "very real issue" with "no content". 😞
Sorry, I don’t understand your complaint. What questions would you want to ask to improve the content?