Find the One Thing All Your Replicas Share
Three replicas at 99% promise 31 seconds of downtime a year. One shared dependency at 99.9% turns that into 8.8 hours. Here are the five questions that find it on your diagram this afternoon.
Hi, I'm Rowland. I build highly scalable, resilient systems and design elegant architectures. I love making complex things simple, both in open and closed source.
I like building modern UI's and scalable SPA with HTML, CSS, JavaScript and React
I also like working in the server side, with technologies like Node.js, SQL and NoSQL
I have worked with some great JamStack architecture for better performance, faster development & SEO Optimization
Cross platform mobile development for iOS and Android phones using React Native
Three replicas at 99% promise 31 seconds of downtime a year. One shared dependency at 99.9% turns that into 8.8 hours. Here are the five questions that find it on your diagram this afternoon.
A second server can show the old text while another server has already moved on. Nothing errors. It stays stale until it can name the sequence it is missing and read that sequence from Postgres.
A daily total closes when the watermark passes the window end plus the allowed lateness. A row that arrives after that line keeps its event time and does not change the number that already shipped.