All Chat Applications
Elixir is a powerful tool. In just 15 minutes you can have an acceptable chat application. Here endeth the blog post, but wait you have more questions.
How do you deploy your application? Is Docker necessary, or even useful? What about service discovery, secrets, load balancing and other cloud flavoured issues.
Let's take that chat application and make it scalable, fault-tolerant and available. Using concrete examples I will provide solutions to all these questions and maybe even more.
Outline/Structure of the Talk
30 minute talk with slides followed by some demonstrations and questions
Learning Outcome
Provide guidance on working with Elixir applications in today's larger technology ecosystem. Introduce tools and processes that attendees can work with immediately. Highlight best practices that are different when working with Elixir compared to other languages.
Target Audience
Anyone who has discovered a joy for Elixir but so far been unable to use it in real projects.
Prerequisites for Attendees
Attendees should have a basic grasp of Elixir's key features and be comfortable looking at a few code snippets
Video
Links
I have also presented a live coding session where I walk through creating the chat application discussed in this talk. Slides and video are available
http://crowdhailer.me/talks/2017-10-31/live-coded-chat-app-in-45-minutes/
schedule Submitted 5 years ago
People who liked this proposal, also liked:
-
keyboard_arrow_down
Bryan Hunter - Poka yoke: Mistake-proofing via Functional Programming
45 Mins
Talk
Beginner
"Poka yoke” (po-kah yo-kay) is a term from Japanese manufacturing that means "mistake proofing". It is a powerful concept (equally powerful in software) in which the design of a system shapes usage so that human error is prevented or corrected before it can cause real harm. In this session we will explore how and why FP maps so well onto the poka yoke concept. We will discuss the merits of mistake proofing over diligence, and rethink our approaches to craft and quality. You will leave with a new lens to evaluate languages, tools, and your own code. Examples in Elixir, Elm, F#, and Idris.
-
Call for Proposals CLOSED
Ended on Jul 24 '17 05:29 AM IST
All proposals will be public. Registered user of the submission system will be able to comment on your proposal. You are required to reply to those comments to provide clarifications, explain revisions and respond to questions. The program team will look at how well you've responded to comments and updated your proposal to incorporate public suggestions. Ultimately the decision to accept a session resides with the program team.
Your proposal stands the best chance to be selected, if it's unique, fully flushed, ready-to-go. Please ensure you've read:
To encourage early submissions and iterative improvement of proposals, we'll start accepting proposals as soon as we find them a good fit. As time passes by, the competition gets tougher. So don't wait till the last date to submit your proposal.
Naresh Jain
Dhaval Dalal
Francesco Cesarini
Debasish Ghosh
Shad Amez
