Designing and architecting for scalability with Erlang/OTP
You need to implement a fault-tolerant, scalable, soft, real-time system with requirements for high availability. It has to be event driven and react to external stimulus, load, and failure. It must always be responsive. Francesco Cesarini outlines the Erlang/OTP approach to architecting a distributed system, breaking down the task into 10 steps that can be applied in other languages as well.
| Talk Title | Designing and architecting for scalability with Erlang/OTP |
| Speakers | Francesco Cesarini (Erlang Solutions Ltd) |
| Conference | O’Reilly Open Source Convention |
| Conf Tag | |
| Location | Austin, Texas |
| Date | May 16-19, 2016 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
You need to implement a fault-tolerant, scalable, soft, real-time system with requirements for high availability. It has to be event driven and react to external stimulus, load, and failure. It must always be responsive. You have heard many success stories that suggest Erlang is the right tool for the job. And indeed it is—but while Erlang is a powerful programming language, on its own, it’s not enough to group these features together and build complex reactive systems. To get the job done correctly, quickly, and efficiently, you also need middleware, reusable libraries, tools, design principles, and a programming model that tells you how to architect and distribute your system. Francesco Cesarini describes the principles you need to architect your system, breaking down the task into 10 easy steps. Topics include:
