The document discusses migrating a Rails monolith application to Elixir and Phoenix. It describes the initial Rails application as handling many services and having slow response times of around 6 seconds. It then considers reasons for moving to Elixir, including improved app speed and productivity. The process of migrating the team, infrastructure, and application is examined, including challenges like poor tooling and differences between OOP and FP paradigms. Ultimately, the outcome is a much faster application that is easier to refactor and has faster tests, leaving both users and developers happy.

1. Ruby to Elixir
One App Story*
*non technical too much

2. ALEXANDER TSIREL

3. HELLO FROM HIVETEC

4. HELLO FROM HIVETEC
YES WE HIRE

5. YES WE HIRE

6. STORY TIME

7. RAILS MONOLITH

8. Front End
Scrapers
Parsers
Background jobs
Analytics
ChatBots
…
Other suspicious and questionable services
RAILS MONOLITH

9. ALL-IN-ONE

10. RAILS MONOLITH

11. Ruby + Rails
Nodejs
C++
RAILS MONOLITH - STACK

12. RAILS MONOLITH
~6 sec resp ~80 jobs per sec

13. Any reason to move from
Ruby to Elixir?

14. MAYBE

15. MAYBE

16. PRODUCTIVITY
OBSCURE

17. APP SPEED IS
WIN

18. Elixir + Phoenix
Nodejs
DESIRED STACK

19. Reasons behind
Team onboarding
Infrastructure changes
…
Outcome?
Pain
Outcome?
COMMON STEPS

21. POOR
TOOLING

22. POOR
TOOLING
=
WRITE OWN

23. PREPARE TO REINVENT

24. PREPARE TO EXPLAIN

25. PREPARE TO CONVINCE

26. Onboarding
Team is new to Elixir

27. Test the water
Video casts like Elixir Sip
Pairing
Small and fun pet-projects like chatbot
(everyone likes chatbots!)
Happiness
TEAM ONBOARDING STEPS

28. Elixir Crash Course
Fun in IEX
Pain in IEX
Docs
Pairing
Frustration
REAL ONBOARDING STEPS

29. Infrastructure
Elixir is not Ruby

30. Less server units
More CPU
Deploy Process change (eDeliver)
INFRASTRUCTURE CHANGES

31. Everyday Elixir
Dark/Bright sides

32. FP > OOP

33. FP > OOP
STOP think in OOP

34. TOP Mind Blowing Twists
ActiveRecord vs Ecto
Async Tasks
App as package

35. TOP Mind Blowing Twists
ActiveRecord vs Ecto
Async Tasks
App as package
PATTERN MATCHING

36. Confusing docs. Phoenix latest docs are
misleading.
Side package can slowdown whole app
i18n is a joke
Lack of style guides & conventions
DARK SIDE

37. RULES AS A MUST

38. Blazing FAST app
Easy refactoring. MUCH EASY
Fast tests
Productivity goes up. *slowly
BRIGHT SIDE

39. Outcome
FFFFFFFinally

40. Blazing FAST app
Easy refactoring. MUCH EASY
Fast tests
Productivity goes up. *slowly
WHAT WE HAVE NOW

41. HAPPY ENDING?

42. USERS ARE HAPPY!

43. DEVS ARE HAPPY!

44. QUESTIONS?
Alexander Tsirel
twitter:
github:
HiveTec is hiring!
HiveTec is hiring!
HiveTec is hiring!
HiveTec is hiring!
HiveTec is hiring!
HiveTec is hiring!
HiveTec is hiring!
@noma4i