Introducing Juvet - Building Bots in Elixir

There is another massive shift happening with how we interact with companies through software. Users feel comfortable naturally talking with their applications through chat bots. Chat is the next generation of the user interface.

Elixir is the perfect language and ecosystem for building bots and for conversational interfaces. In this session, we will see how we can build scalable, realtime web applications (or “bots”) using a new library Juvet and the Slack API. We will see what a good bot architecture looks like and how we can integrate with existing artificial intelligence services to make our bots smarter.

Finally, we will learn how you can leverage metaprogramming in Elixir to build a router to help route requests from chat services to create a Phoenix-like experience for building chat apps.

Transcript

1. Elixir + CHATBOTS INTRODUCING JUVET
2. WELCOME WELCOME WELCOME
7. AND I AM A BOT BUILDER™
11. Tatsu
12. Tatsu
13. A Brief In tr o CHATBOTS
14. A COMPUTER PROGRAM DESIGNED TO SIMULATE A CONVERSATION WITH HUMAN USERS CHATBOT
15. USER PLATFORM APP OPS CHANNEL /HELP OPS CHANNEL HERE IS THE HELP YOU REQUESTED: { CHANNEL: ‘C1234’, USER: ‘U8324’, TEAM: ‘T4390’, MESSAGE: ‘/HELP’ } CHAT.POST_MESSAGE(‘HERE IS THE HELP YOU REQUESTED:’)
16. USER PLATFORM APP CLIENT SERVER
17. J os eph WEIZENBAUM
18. J os eph WEIZENBAUM
21. Alan TURING
22. ELIZA
23. SIRI 2 0 0 7
24. 2 0 0 1
27. RADIOHEAD IS ALWAYS AHEAD OF THEIR TIME™
28. imp or tant? CHATBOTS Why are
40. WHAT OCCURRED AT THAT BASKETBALL GAME?
42. FAMILIAR
44. FAMILIAR
45. FAMILIAR LESS BARRIERS
46. MESSAGES SLACK TEAMS FACEBOOK
47. BE WHERE YOUR USERS ARE
48. PLATFORM SPECIFIC FUN STUFF BUSINESS STUFF
49. MO’ MONEY
51. FUN DEV CODE RUN BEEP-BOOP
52. built today? CHATBOTS How are
53. HOW SLACK WORKS A P P D I R E C T O R Y
54. HOW SLACK WORKS O A U T H W / S L A C K
55. HOW SLACK WORKS S C O P E R E Q U E S T
56. HOW SLACK WORKS N E W B O T U S E R !
57. USER PLATFORM APP OPS CHANNEL /HELP HOW SLACK WORKS { CHANNEL: ‘C1234’, USER: ‘U8324’, TEAM: ‘T4390’, MESSAGE: ‘/HELP’ }
58. JAVASCRIPT LIBRARIES
59. JAVASCRIPT LIBRARIES
60. WORKER THREADS CPU PERFORMANCE SINGLE- THREADED EVENT LOOP UNHANDLED EXCEPTIONS NODE LIMITATIONS
62. Elixir? Why
63. PROCESSES PANACEA CURES WHAT ALES ‘YA SPEED HOT CODE RELOADING FAULT TOLERANCE
64. WHY ELIXIR? BUILT FOR COMMUNICATION
65. WHY ELIXIR? BUILT FOR COMMUNICATION 90%
66. WHY ELIXIR? BUILT FOR COMMUNICATION
67. FAST WHY ELIXIR?
68. WHY ELIXIR? https://github.com/mroth/phoenix-showdown/blob/master/README.md#benchmarking
69. STATEFUL PROCESSES WHY ELIXIR?
70. WHY ELIXIR? PROCESS PROCESS PROCESS SUPERVISOR
71. HOT CODE RELOADING WHY ELIXIR?
72. WHY ELIXIR? FAULT TOLERANT
73. WHY ELIXIR? PROCESS PROCESS SUPERVISOR PROCESS
74. be improved? CHATBOTS How can building
75. PLUG MIDDLEWARE CONTEXT ROUTER CONTROLLER TEMPLATES
77. JUVET/JUVET
83. NEXT.TATSU.IO
84. LEBOTSKI
86. LEBOTSKI DISPENSARIES BOWLING ALLEYS • COCKTAIL BARS •
87. LEBOWSKI COMMANDS / B E V E R A G E - H E R E - M A N
88. LEBOTSKI DISPENSARIES BOWLING ALLEYS • COCKTAIL BARS •
89. Aaron DRAPLIN
91. JWRIGHT/LEBOTSKI
92. DEMO DEMO DEMO
93. with Juvet? CHATBOTS Building
94. JUVET WALKTHROUGH A D D D E P E N D E N C Y
95. JUVET WALKTHROUGH A D D E X T R A A P P
96. JUVET WALKTHROUGH S U P E R V I S I O N T R E E
97. JUVET WALKTHROUGH S U P E R V I S I O N T R E E NEW LEBOWSKI APP FOR MY TEAM
98. JUVET WALKTHROUGH C O N F I G U R E
99. JUVET WALKTHROUGH B O T
100. JUVET WALKTHROUGH R O U T E R
101. JUVET WALKTHROUGH A D D P L U G
102. PLUG > LISTEN TO SPECIFIC ENDPOINTS > INTEGRATE INTO EXISTING APP
103. JUVET WALKTHROUGH A D D C O M M A N D R O U T E
104. ROUTER > DSL TO DEFINE ROUTES > FIND APPROPRIATE ROUTE > MIDDLEWARE
105. ROUTER F I N D I N G R O U T E S
106. ROUTER F I N D I N G R O U T E S
107. MIDDLEWARE > CHAIN RESPONSIBILITIES TOGETHER > EXTENSION POINTS > MODIFY CONTEXT > COMMON RUNTIME ON EACH REQUEST
108. MIDDLEWARE D E F I N I N G M I D D L E W A R E
109. JUVET WALKTHROUGH C U S T O M M I D D L E W A R E
110. CONTEXT > VARIABLES FOR USE IN CONTROLLER > ONLY UPDATED IN MIDDLEWARE
111. JUVET WALKTHROUGH R O U T E R
112. JUVET WALKTHROUGH C O N T R O L L E R
113. CONTROLLER > ACTION PER REQUEST > PREPARE + SEND RESPONSE(S)
114. JUVET WALKTHROUGH T E A M S C H E M A
115. JUVET WALKTHROUGH U S E R S C H E M A
116. JUVET WALKTHROUGH T E A M M AT E S C H E M A
117. JUVET WALKTHROUGH C O N T R O L L E R
118. T E M P L AT E
119. JUVET WALKTHROUGH S E N D I N G T E M P L AT E
120. TEMPLATES > PLATFORM INDEPENDENT > SENT BACK AS A RESPONSE > INTERLACE DATA
121. like MVC Apps CHATBOTS The tr adeo ff s on building
122. ROUTING A NICE BLACK BOX YOUR APP ROUTER CONTROLLERS TEMPLATES AUTHORIZATION LOW-LEVEL API PLATFORM LIBRARIES HIDE THE PLUMBING
123. FAMILIAR PATTERN MODEL VIEW CONTROLLER USER SEES USES MANIPULATES UPDATES
124. EVERYTHING HAS A PLACE TEMPLATES CONTROLLERS MODELS ROUTES > BUSINESS LOGIC > HANDLES PLATFORM REQUESTS > RUNS MIDDLEWARE > PASSES CONTEXT > CREATES CONTROLLER > RUNS ACTION > HANDLES REQUEST > PREPARES RESPONSE > RENDERS RESPONSE(S) > RETRIEVE DATA > UPDATE DATA > INTEGRATES DATA > PROVIDES RESPONSE
125. EXTENSION POINTS USER REQUEST PLATFORM APP ROUTER FINDS ROUTE MIDDLEWARE IS RUN CONTROLLER IS CREATED ACTION IS CALLED TEMPLATE IS RENDERED RESPONSE IS SENT USER RESPONSE
126. OVERKILL FOR SIMPLE BROADCAST PLATFORM GITHUB > CHAT.POSTMESSAGE
127. HARDER TO DEBUG > (PHOENIX.ROUTER.NOROUTEERROR) NO ROUTE FOUND FOR POST /SLACK/ACTIONS (TATSUWEB.ROUTER) > (TATSU 0.0.11) LIB/PHOENIX/ROUTER.EX:405: TATSUWEB.ROUTER.CALL/2 > (COWBOY 2.9.0) /TATSU_NEXT/DEPS/COWBOY/SRC/COWBOY_HANDLER.ERL:37: :COWBOY_HANDLER.EXECUTE/2 > (TATSU 0.0.11) LIB/TATSU_WEB/ENDPOINT.EX:1: TATSUWEB.ENDPOINT.PLUG_BUILDER_CALL/2 > … > … > … > … > … > … > … C A L L S T A C K
128. Future ENHANCEMENTS
129. DIALOGUE
130. DIALOGUE R U B Y
131. DIALOGUE TATSUIO/DIALOGUE
132. ADDITIONAL PLATFORMS TWILIO TEAMS DISCORD SLACK ALEXA #01 #02 #03 #04
133. BETTER TEMPLATING COMPONENTS PARTIALS SEPARATE PLATFORMS
134. IN-HOUSE AUTHENTICATION
135. GENERATORS
136. GENERATORS
137. BETTER ERROR MESSAGES > (PHOENIX.ROUTER.NOROUTEERROR) NO ROUTE FOUND FOR POST /SLACK/ACTIONS (TATSUWEB.ROUTER) > … >… > … > … > … > … > … > ??? 💀😅 C A L L S T A C K
138. RANDOM ACCESS MEMORY USER CAN YOU SCHEDULE A MEETING? APP I SURE CAN. WITH WHOM? USER WITH TIM. APP GOT IT. WHEN? USER TOMORROW AT 2. APP DONE. I SCHEDULED A MEETING WITH TIM TOMORROW AT 2.
139. RANDOM ACCESS MEMORY CAN YOU SCHEDULE A MEETING? USER CAN YOU SCHEDULE A MEETING WITH TIM TOMORROW AT 2? APP DONE. I SCHEDULED YOUR MEETING WITH TIM FOR TOMORROW AT 2. CAN YOU SCHEDULE A MEETING? USER ACTUALLY CAN YOU MAKE IT FOR 3? APP DONE. I RE-SCHEDULED IT FOR TOMORROW AT 3.
140. RANDOM ACCESS MEMORY DETECT PARAMETERS ALLOW CHANGE
141. DISCOVERABILITY T R A I N I N G W H E E L S ARE YOU READY FOR THE MEETING? YOU CAN REPLY WITH ‘Y’ES OR ’N’O. APP USER YES. MEETING SCHEDULED! DID YOU KNOW YOU CAN REQUEST A RESCHEDULE BY REPLYING ‘RE-SCHEDULE’? APP
142. VALIDATION ANDY WANTS TO MEET WITH YOU TODAY AT 2. APP ARE YOU AVAILABLE? USER BLERG.
143. VALIDATION I’M SORRY ‘BLERG’ IS NOT AN ANSWER. APP ACKNOWLEDGE THE RESPONSE 1. YOU CAN RESPOND ‘YES’ OR ‘NO’ APP PROVIDE CORRECT OPTIONS 2. ANDY WANTS TO MEET WITH YOU TODAY AT 2. APP ARE YOU AVAILABLE? RE-ASK THE QUESTION 3.
144. SELECTION WHERE DO YOU WANT TO MEET MACKENZIE TONIGHT? APP USER 1. 1. COFFEE SHOP 2. RESTAURANT 3. BAR APP O P T I O N R E D U C T I O N
145. SELECTION OK. WHICH COFFEE SHOP? APP O P T I O N R E D U C T I O N 1. CAFE JOE’S 2. STARBUCKS ON MAIN 3. PERKATORY APP
146. RESPONSE SAMPLING YES APP OK APP CORRECT APP WRONG APP NOPE APP LOOKS GOOD APP 👍 APP ✌ APP THAT’S WHAT SHE SAID APP COOL APP
147. GO FORTH + CREATE BOTS
148. JUVET/JUVET
149. NEXT.TATSU.IO
150. SPEAKERDECK.COM/JWRIGHT/ ELIXIRCONF2022
151. @JWRIGHT JWRIGHT JAMIE@BRILLIANTFANTASTIC.COM STANDUP.FM
152. Q+A
153. @JWRIGHT JWRIGHT JAMIE@BRILLIANTFANTASTIC.COM STANDUP.FM