Lmst

Khóa học 60 bài học thực hành thiết kế hệ thống với Java Spring Boot:

- Xây dựng hệ thống lên lịch tác vụ phân tán phức tạp.
- Sử dụng Java Spring Boot.
- Dành cho kỹ sư phần mềm, kiến trúc sư, SRE, DevOps, Data Engineers, Product Manager.
- Thiết kế hệ thống, thực tế, chuyên sâu các khái niệm phân tán, tập trung vào khả năng quan sát và độ tin cậy.

#java #springboot #coursedesign #distributedSystem #javatsc #lập_trình #hệ_thống_phân_tán #thiết_kế_hệ_thống #khóa_học

https://www.reddit.com/r/p

⚙️ Building resilience in distributed systems just got easier.

Our latest blog explores durable computing—a powerful approach to managing state, failure recovery and consistency in the cloud-native world.

🔗 Read more: https://ter.li/xfw1oa

#Tech #AI #DistributedSystem #DistributedComputing

In a Distributed System, achieving ACID is hard due to many challenges

Read more 👉 https://lttr.ai/ATj5U

#java #Microservices #Transactions #DistributedSystem #RelationalDatabaseSystems #CloselyTied

- Divulged into the conception and making of a visual book on software architecture in this episode: https://ter.li/ooqott

- Learned about new approaches and techniques to successfully run through a distributed system in this episode: https://ter.li/nza3zq

2/2

#DistributedSystem #SoftwareArchitecture #SoftwareDevelopment

Great workshop with GLACIATION consortium under #HorizonEurope! Discussed synergies for Braine software, including #edge #security, #distributedsystem for #dataprivacy, #datasovereignty & #energyefficient #microdatacentre for #bigdata & #AI.

Thanks @AidanOMahony &
#Dell ! 💻🚀

Just found out I have no #introduction post yet. So :

I'm a techie that likes to tinker with stuff. I'm interested in #opensource, #AI, #ML, #computersystem, and #distributedsystem topics. Sometimes I write blogs about them.

I've signed up and have been using this little website sporadically since 2017. I thought it was a really cool idea that lacked users.

But recently it proved its value by accepting people who want to be free.

Hope to see you guys here more in the future!

I wonder if #EventModeling or #Eventsourcing provides a methodic approach or something similar to describe failure #scenarios for a #distributedsystem. I made already a mapping of the #k8s based #distributedsystem to #12factor and the #reactive principles as described in the #reactivemanifesto.
I also collected all possible failure events that came to my mind with a mindmap.
So, now I search for a good way to describe the failure scenarios.

Ideas and hints very welcome.

People are sometimes afraid of #p2p’s complexity because it’s a #distributedsystem.

But client-server is a many-to-one relationship, so servers are naturally bottlenecks. Scaling them quickly becomes a distributed system of shared state with complexity equal to or greater than any p2p design.

Funny observation: the design of #ActivityPub is very close to X.500 (ITU-T directory standard first published 1988).

#DistributedSystem: if it looks like a 🦆 , talks like a 🦆 , ...

My favorite distributed systems essay, Fred Hebert's "Queues Don't Fix Overload": https://ferd.ca/queues-don-t-fix-overload.html When working on a #DistributedSystem team, I usually link this a couple of times week. The key ideas:

1. Your system has a bottleneck somewhere.
2. Putting queues in front of the bottleneck means you crash less often, but harder.
3. The bottleneck needs to be able slow down system input. "Back-pressure" and load shedding are your friends!

Find that bottleneck.

Consistent Hashing
{ by @yt_tr1x@twitter.com } from @hashnode@twitter.com

#hashing #server #distributedsystem #binarysearch-algorithm https://tr1x.hashnode.dev/consistent-hashing

#distributedsystem

Client Info