{"href":"https://api.simplecast.com/oembed?url=https%3A%2F%2Fstartupengineering.co%2Fepisodes%2Fhow-to-synchronise-a-distributed-pubsub-system-c9WQrOxQ","width":444,"version":"1.0","type":"rich","title":"How to synchronise a distributed pubsub system","thumbnail_width":300,"thumbnail_url":"https://image.simplecastcdn.com/images/747a61d1-f61d-406e-bebf-a509b902266e/3ca0befa-054c-4f23-a13c-e9a24fc5d3f3/podcast-alt-name-v-2.jpg","thumbnail_height":300,"provider_url":"https://simplecast.com","provider_name":"Simplecast","html":"<iframe src=\"https://player.simplecast.com/d7184d71-a32d-4024-b1ab-e606d2515085\" height=\"200\" width=\"100%\" title=\"How to synchronise a distributed pubsub system\" frameborder=\"0\" scrolling=\"no\"></iframe>","height":200,"description":"Building a fully distributed system is really hard. But a few compromises can go a long way. Hear how Paddy CTO and Co-Founder of Ably, would white board out complex problems and where needed centralise small pieces in a single region. It might seem simple or small but trade offs like this can go along way and still meets the requirement of a pier to pier region relationship where any region can fail and come back online at anytime. \n\nWhat trade offs are hidden in your architecture that would simplify your stack?"}