Beam Stack under my umbrella

An Elixir Umbrella application decoupled architecture that runs on a Beam Stack (Elixir, CouchDB, RabbitMQ).

Transcript

1. Beam @emota7 umbrella Stack under my
2. @emota7 Emanuel Mota emanuel@digisensei.com (ex rubyist)
3. @emota7 Quick Elixir story
5. Beam Stack i. CouchDB ii. Umbrella Application iii. RabbitMQ @emota7
6. @emota7 CouchDB is a NoSQL database, developed in Erlang, that stores JSON documents and exposes its functionalities through an HTTP API.
7. @emota7 Quick Demo FAUXTON
8. @emota7 why Couch • Document Store • Master to Master replication • Changes Feed
9. @emota7 document store
11. @emota7 Master to Master replication
12. @emota7 •Cloudant Sync - mobile •PouchDB - web Allows for an offline first approach Client Implementations
13. @emota7 • Decoupled architecture • Micro-services that react to document changes Changes Feed
14. @emota7 No Elixir client for Couch A. build your own client ? B. use an existing erlang client ?
15. CouchDB HTTP API
16. https://github.com/benoitc/couchbeam
17. @emota7 Code Time
18. Couchbeam doc representation
19. @emota7 using Ecto embedded schemas Option 1
20. @emota7 we get changesets for free
21. @emota7 Elixir PROTOCOLS Option 2
22. @emota7 Every schema implements its own struct Option 2
23. @emota7 CouchDB Chalenges • Setup (serialising, deserialising) • MapReduce for querying is hard even though it sounds cool • Setup testing
24. i. CouchDB ii. Umbrella Application iii. RabbitMQ @emota7 Beam Stack
25. @emota7 why an Umbrella • Make project manageable as it grows • Organise it in a way that it is easy to split / replace / delete code • Strong boundaries
26. @emota7 Umbrella structure Plug App Elixir App Elixir App Phoenix App Elixir App Plug App Elixir App
27. @emota7 4000 4009 4007 wss:// https:// https://
28. @emota7 If deploying an umbrella to Heroku (or no load balancer) Based on a gist shared by @wojtekmach https://github.com/wojtekmach/acme_bank/tree/master/apps/master_proxy
29. @emota7
30. @emota7 Umbrella Challenges • Internal API’s • Designing supervision trees • “Let it Crash !”
31. @emota7 Show me more…?
32. i. CouchDB ii. Umbrella Application iii. RabbitMQ @emota7 Beam Stack
33. @emota7 why RabbitMQ • Messaging is asynchronous • Connect applications to each other as components • Decoupling • Scaling
34. @emota7
35. @emota7
36. @emota7 • Tracking errors across queues • Planing Consumers/ Publishers • Rabbit is not a data storage • Can become complex Rabbit Chalenges
37. A rubyist conclusion • Elixir completely different beast from Ruby • OTP is full of treasures • The need to think in processes and supervision trees
38. Thank You!
39. @emota7 Emanuel Mota emanuel@digisensei.com Questions?