Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Migrating from Monolithic Rails

A story about how we migrated from using just Ruby on Rails, through a journey to Microservice arcitecture, using grape, angular.js and other services.

  • Be the first to comment

  • Be the first to like this

Migrating from Monolithic Rails

  1. 1. Yo! I AM DANIELIUS VISOCKAS dvisockas
  2. 2. I AM FROM LITHUANIA
  3. 3. MIGRATING FROM MONOLITHIC RAILS
  4. 4. “ "Good frameworks are extractions, not inventions" ◦ @dhh.
  5. 5. RAILS: THE GOOD PARTS Routing Models Persistence (migrations, schema) Mailers MVC
  6. 6. IT IS A MONOLITH And that is not a good thing, you know.
  7. 7. DEPLOYMENT MAINTAINING SCALING
  8. 8. WE HAD A RAILS APP And Sinatra for the API
  9. 9. SOMETHING LIKE THIS
  10. 10. WE NEED TO GO BACK
  11. 11. LEARN FROM THE HISTORY OF THE EARTH
  12. 12. Splitting into services CURE FROM MONOLITHS
  13. 13. Let’s talk lasers Or if you prefer I can call it frontend
  14. 14. WE DID NOT LIKE THAT PART OF RAILS
  15. 15. What has a normal structure?
  16. 16. There are many more choices
  17. 17. We chose
  18. 18. Late extractionEarly abstraction
  19. 19. CURRENT SITUATION RailsAngular.js
  20. 20. Easy I will just add respond_with to my controllers
  21. 21. But do we need Rails?
  22. 22. RUBY TOOLS FOR BUILDING API’S Sinatra Grape RailsAPI
  23. 23. We chose
  24. 24. REASONS FOR CHOOSING GRAPE Documentation Versioning Parameter validations
  25. 25. CURRENT SITUATION Rails Angular.js Grape
  26. 26. Thats how we did it And you can try it too!
  27. 27. EXTRACTING GRAPE FROM RAILS Active record Background jobs Mailers
  28. 28. AT LAST Angular Grape
  29. 29. THE GOOD PARTS Small steps People can focus on one side Habit forming Faster
  30. 30. Thank you! ANY QUESTIONS? dvisockas

×