Talks
Speakers
Events
Topics
Sign in
Home
Talks
Speakers
Events
Topics
Leaderboard
Use
Analytics
Sign in
Suggest modification to this talk
Title
Description
GORUCO 2018: Evented Autonomous Services in Ruby by Scott Bellware
Date
Summarized using AI?
If this talk's summary was generated by AI, please check this box. A "Summarized using AI" badge will be displayed in the summary tab to indicate that the summary was generated using AI.
Show "Summarized using AI" badge on summary page
Summary
Markdown supported
In this presentation at GoRuCo 2018, Scott Bellware discusses the concept of evented autonomous services in Ruby, emphasizing their importance within the context of microservices and service-oriented architecture. ### Key Points: - **Definition of Services**: Bellware clarifies what he means by services in this context, differentiating them from service objects, operating system processes, applications, and APIs. He insists that services should be cohesive, enabling productivity through decoupling and focused design. - **Benefits of Using Ruby for Services**: He discusses the skills developers gain from working with Ruby and the investment in legacy code, highlighting that Ruby should be a natural choice for building services. - **Career Trajectory**: Bellware identifies a prevalent issue among Ruby developers where the path from junior to senior roles in Rails can lead to burnout. He proposes that there are alternative growth paths that involve working with autonomous services without needing to switch away from Ruby. - **Understanding Microservices**: Bellware mentions Martin Fowler's concept of 'smart pipes and dumb endpoints' and critiques traditional service transport methods, advocating for clearer message delivery mechanisms. - **Message Delivery Challenges**: He outlines the complexities surrounding guaranteed message delivery in microservices and the potential problems posed by reprocessing commands. - **Event Sourcing and Streams**: The distinction between queues and event streams is explored, with a focus on how streams are a superior method for managing data flow in services. He provides an example involving bank account transactions to illustrate event sourcing, where commands lead to recorded events that influence the state of services.
Suggest modifications
Cancel