Migrating from Monolithic Rails

1. Yo! I AM DANIELIUS VISOCKAS dvisockas

2. I AM FROM LITHUANIA

3. MIGRATING FROM MONOLITHIC RAILS

4. “ "Good frameworks are extractions, not inventions" ◦ @dhh.

5. RAILS: THE GOOD PARTS Routing Models Persistence (migrations, schema) Mailers MVC

6. IT IS A MONOLITH And that is not a good thing, you know.

7. DEPLOYMENT MAINTAINING SCALING

8. WE HAD A RAILS APP And Sinatra for the API

9. SOMETHING LIKE THIS

10. WE NEED TO GO BACK

11. LEARN FROM THE HISTORY OF THE EARTH

12. Splitting into services CURE FROM MONOLITHS

13. Let’s talk lasers Or if you prefer I can call it frontend

14. WE DID NOT LIKE THAT PART OF RAILS

15. What has a normal structure?

16. There are many more choices

17. We chose

18. Late extractionEarly abstraction

19. CURRENT SITUATION RailsAngular.js

20. Easy I will just add respond_with to my controllers

21. But do we need Rails?

22. RUBY TOOLS FOR BUILDING API’S Sinatra Grape RailsAPI

23. We chose

24. REASONS FOR CHOOSING GRAPE Documentation Versioning Parameter validations

25. CURRENT SITUATION Rails Angular.js Grape

26. Thats how we did it And you can try it too!

27. EXTRACTING GRAPE FROM RAILS Active record Background jobs Mailers

28. AT LAST Angular Grape

29. THE GOOD PARTS Small steps People can focus on one side Habit forming Faster

30. Thank you! ANY QUESTIONS? dvisockas

Eche un vistazo a continuación