Interactive
Chris started the Phoenix project after working to build real-time events into his Ruby on Rails applications. As he started to implement the solution, he had a threading API called Event Machine and noticed that his threads would occasionally die. He then found himself implementing code to detect dead threads.
Over time, the whole architecture began to frustrate him. He was convinced that he could make it work, but he didn’t think he could ever make it beautiful or reliable.
If you’re building interactive applications on a traditional web stack, you’re probably working harder than you need to. There’s a reason for that. In the years before web programming was popular, client-server applications were simple. A client process or ...
Get Programming Phoenix now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
