
www.codesync.global/media/why-time-evil-distributed-systems-peter-van-roy
Preview meta tags from the www.codesync.global website.
Linked Hostnames
7- 13 links towww.codesync.global
- 5 links totwitter.com
- 2 links towww.facebook.com
- 2 links towww.linkedin.com
- 2 links towww.youtube.com
- 1 link towww.erlang-solutions.com
- 1 link towww.instagram.com
Thumbnail

Search Engine Appearance
Why time is evil in distributed systems
Building distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
Bing
Why time is evil in distributed systems
Building distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
DuckDuckGo

Why time is evil in distributed systems
Building distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
General Meta Tags
13- titleWhy time is evil in distributed systems
- theme-color#ff005f
- keywordsDistributed systems, Erlang, consistency performance, global state, Peter van Roy
- descriptionBuilding distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
- robotsindex, follow
Open Graph Meta Tags
7- og:site_nameCode Sync
- og:descriptionBuilding distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
- og:titleWhy time is evil in distributed systems
- og:typearticle
- og:urlhttp://www.codesync.global/media/why-time-evil-distributed-systems-peter-van-roy/
Twitter Meta Tags
5- twitter:cardsummary_large_image
- twitter:site@CodeBEAMio
- twitter:titleWhy time is evil in distributed systems
- twitter:descriptionBuilding distributed systems is hard, even using languages such as Erlang that support them well. There are many problems that have to be solved: partial failure, nondeterminism, observable delays, event ordering, global state, distributed consistency, performance (latency and throughput), and so on. Progress has been made in solving these problems, but often in isolation and without realizing how the solutions are related. In this talk I go to the heart of the matter and explain why almost all of these hard problems are avatars of one problem, namely real-world time. I explain how to avoid time when building distributed systems. There are some cases when time cannot be avoided, even in principle, and I will explain those as well. In both situations, using and avoiding time, I will try to present general solutions at a correct level of abstraction. All ideas will be illustrated by examples of real distributed systems from my experience (edge computing, consistent replication, etc.). I hope that this talk will give you a fresh outlook on distributed systems and help you design better ones.
- twitter:imagehttp://www.codesync.global/uploads/media/articles/0001/01/thumb_983_reference.jpg
Link Tags
4- icon/assets/img/favicon.93e85b1c.png
- manifest/manifest.json
- stylesheet/assets/global.73570f4b.css
- stylesheet/ckeditor/plugins/codesnippet/lib/highlight/styles/monokai.css
Emails
2- ?subject=Why time is evil in distributed systems&body=Take a look at this: http://www.codesync.global/media/why-time-evil-distributed-systems-peter-van-roy/
- [email protected]
Links
26- http://www.codesync.global/speaker/peter-van-roy
- https://twitter.com/CodeBEAMio
- https://twitter.com/CodeElixirIO
- https://twitter.com/CodeMeshio
- https://twitter.com/CodeSyncGlobal