The document discusses migrating a monolithic Rails application to a microservices architecture using Grape for the API and Angular for the frontend. It describes extracting the API into a separate Grape service to split the monolith into independent services for deployment, maintenance, and scaling benefits. Reasons for choosing Grape include its documentation, versioning, and parameter validation features. The process involved extracting models, jobs, and mailers from Rails to be used by the standalone Grape API.

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

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

15. WE DID NOT LIKE THAT PART OF RAILS

16. What has a normal structure?

17. There are many more choices

18. We chose

19. Late extractionEarly abstraction

20. CURRENT SITUATION
RailsAngular.js

22. Easy
I will just add respond_with to my controllers

23. But do we need Rails?

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

25. We chose

26. REASONS FOR CHOOSING GRAPE
Documentation
Versioning
Parameter validations

28. CURRENT SITUATION
Rails
Angular.js
Grape

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

30. EXTRACTING GRAPE FROM RAILS
Active record
Background jobs
Mailers

31. AT LAST
Angular Grape

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

33. Thank you!
ANY QUESTIONS?
dvisockas