Rails revolutionized the way we build web apps - but that was 10 years ago. These days, it's not uncommon to hear dramatic statements like, “Rails is dead” or even, “Ruby is dead”. Even though such conclusions are far-fetched, it’s a sign that some people have become tired of struggling with various problems that Rails doesn’t address. We’re starting to see people leave Ruby - should you do the same? Or is there a place in the Ruby world where we can still innovate and prove that Ruby is a viable technological choice? In this talk, I’ll introduce you to the growing ecosystem of modern Ruby libraries and frameworks. Let’s go beyond Rails and see that Ruby is doing just fine.

1. CAN WE STILL INNOVATE?
PIOTR SOLNICA RubyDay 2016, Florence

2. mojotech.com
rom-rb.org dry-rb.org

4. 2005 - 2010

6. CONVENTION
OVER
CONFIGURATION

8. COMPLEXITY
ᕕ(˵•̀෴•́˵)ᕗ

9. “FAT MODEL” WAS
AN AMBIGUOUS IDEA

10. EXPLORING NEW
APPROACHES…

11. DDD

12. DCI

13. SPFDL

14. (TOTALLY MADE
THIS UP)

15. SEPARATING PERSISTENCE
FROM DOMAIN LOGIC

16. MAYBE REPOSITORY
PATTERN?

17. MAYBE A FULL-BLOWN
DATAMAPPER PATTERN?

18. MEANWHILE…

19. NEW LIBRARIES
AND FRAMEWORKS!

23. RAILS.MERGE(MERB)
2008-2010

24. 2010+

26. NEW ABSTRACTIONS
▸ Form objects
▸ Value objects
▸ Service objects
▸ Query objects
▸ Policy objects
▸ View objects

27. SPFDL

28. DATAMAPPER 2

29. VIRTUS

31. ROM-RB.ORG

33. 2016

34. ROM-RB.ORG

36. ROM-RB INNOVATIONS
▸ Read/Write separation
▸ Relations as first-class citizens
▸ Data transformations instead of object mutations
▸ Explicit relation composition instead of ambiguous query
DSLs
▸ Command API for custom db-specific database operations
▸ Externalized data validations

37. cfg = ROM::Configuration.new(:sql, 'sqlite::memory')
cfg.gateways[:default].create_table(:users) do
primary_key :id
column :name, String, null: false
column :age, Integer, null: true
end
cfg.gateways[:default].create_table(:tasks) do
primary_key :id
foreign_key :user_id, :users, null: false, on_delete: :cascade
column :title, String, null: true
end

38. class Users < ROM::Relation[:sql]
schema(infer: true)
end
class Tasks < ROM::Relation[:sql]
schema(infer: true)
end
SETS UP RELATION
ATTRIBUTES BASED ON DATABASE
SCHEMA SCHEMA
INFERS TABLE NAME FROM CLASS
NAME

39. rom = ROM.container(cfg)
NO GLOBAL
POLLUTION

40. REPOSITORIES

41. class UserRepo < ROM::Repository[:users]
commands :create
end

42. user_repo = UserRepo.new(rom)
user_repo.create(name: 'Jane', age: 33)
# => #<ROM::Struct[User] id=3 name="Jane" age=33>

43. CHANGESETS

44. class UserRepo < ROM::Repository[:users]
commands :create, update: :by_pk
end

45. user_repo = UserRepo.new(rom)
user = user_repo.create(name: 'Jane', age: 33)
changeset = user_repo.changeset(user.id, name: 'Jane Doe')

46. changeset.diff
# => {:name=>"Jane Doe"}
user_repo.update(user.id, changeset)
# => #<ROM::Struct[User] id=1 name="Jane Doe" age=33>

47. AGGREGATES

48. class Users < ROM::Relation[:sql]
schema(infer: true) do
associations do
has_many :tasks
end
end
end

49. class UserRepo < ROM::Repository[:users]
relations :tasks
def create_with_tasks(user)
command(:create, aggregate(:tasks)).call(user)
end
end

50. user_repo.aggregate(:tasks)
# [#<ROM::Struct[User] id=3 name="Jane" age=33
tasks=[#<ROM::Struct[Task] id=5 user_id=3 title="Jane task 1">,
#<ROM::Struct[Task] id=6 user_id=3 title="Jane task 2">]>>

51. CUSTOM OBJECTS

52. require 'dry-struct'
class Task < Dry::Struct
attribute :title, Types::Strict::String
end
class User < Dry::Struct
attribute :name, Types::Strict::String
attribute :age, Types::Strict::Int
attribute :tasks, Types::Strict::Array.member(Task)
end

53. user_repo.aggregate(:tasks).as(User).to_a
# => [#<User name="Jane" age=33 tasks=[#<Task title="Jane
task 1">, #<Task title="Jane task 2">]>, #<User
name="John" age=32 tasks=[#<Task title="John task 1">,
#<Task title="John task 2">]>]

54. DRY-RB.ORG

56. DRY-RB INNOVATIONS
▸ Advanced data validation
▸ Flexible type system with coercions and constraints
▸ Composable transactions with error handling based on
monads
▸ Simple yet powerful Dependency Injection
▸ Application state management with component lifecycles

57. DRY-STRUCT

58. class User < Dry::Struct
attribute :name, Types::Strict::String
attribute :age, Types::Strict::Int
end

59. module Types
include Dry::Types.module
Age = Types::Strict::Int.constrained(gt: 18)
end
class User < Dry::Struct
attribute :name, Types::Strict::String
attribute :age, Types::Age
end

60. User.new(name: 'John', age: 17)
# [User.new] 17 (Fixnum) has invalid type for :age
(Dry::Struct::Error)

61. DRY-VALIDATION

62. VALIDATION
SCHEMAS

63. UserSchema = Dry::Validation.Schema do
required(:login).value(:str?, size?: 2..64)
required(:age).maybe(:int?, gt?: 18)
end
IS IT A STRING WITH A SIZE
BETWEEN 2 AND 64 CHARS?
CAN BE NIL BUT
IF IT’S NOT THEN IS IT AN
INTEGER AND IS IT GREATER
THAN 18?

64. UserSchema.(login: "j", age: 19).errors
# {:login=>["length must be within 2 - 64"]}
UserSchema.(login: "jane", age: nil).errors
# {}
SHORTCUT FOR `#CALL` :)

65. COMPOSING
SCHEMAS

66. AddressSchema = Dry::Validation.Schema do
required(:street).value(:str?)
required(:city).filled(:str?)
required(:zipcode).filled(:int?)
end
UserSchema = Dry::Validation.Schema do
required(:login).value(:str?, size?: 2..64)
required(:age).maybe(:int?, gt?: 18)
required(:address).schema(AddressSchema)
end

67. VALIDATION HINTS

68. UserSchema.(login: 'jane', age: 'oops').errors
# {:age=>["must be an integer"]}

69. UserSchema.(login: 'jane', age: 'oops').hints
# {:age=>["must be greater than 18"]}

70. DRY-SYSTEM

71. MANAGING STATE

72. require 'dry/system/container'
class Application < Dry::System::Container
configure do |config|
config.root = Pathname.new('./my/app')
end
end
# now you can register a logger
require 'logger'
Application.register('utils.logger', Logger.new($stdout))
# and access it
Application['utils.logger']

73. AUTO-
REGISTRATION

74. require 'dry/system/container'
class Application < Dry::System::Container
configure do |config|
config.root = '/my/app'
config.auto_register = 'lib'
end
load_paths!('lib')
end

75. # under /my/app/lib/logger.rb we put
class Logger
# some neat logger implementation
end
# we can finalize the container which triggers auto-registration
Application.finalize!
# the logger becomes available
Application[‘logger']

76. BOOTING
COMPONENTS

77. # system/boot/persistence.rb
Application.finalize(:persistence) do
init do
require '3rd-party/database'
end
start do
container.register('database') do
3rdParty::Database.new
end
end
stop do
container['database'].disconnect
end
end

78. class Application < Dry::Component::Container
configure do |config|
config.root = '/my/app'
end
end
# requires needed files and boots your persistence component
Application.boot!(:persistence)
# and now `database` becomes available
Application['database']

79. # lib/worker.rb
require ‘application/import'
class Worker
include Import['database']
def do_stuff
users = database.read('select * from users')
# ..
end
end
THIS WILL INJECT “DATABASE”
OBJECT AND MAKE IT AVAILABLE

80. 2016…

81. LET’S CONTINUE
EXPLORING & INNOVATING

82. ᕦʕ ՞ ౪ ՞ ʔᕤ

83. THANK YOU <3