"The dreams of developers working on monolithic Rails applications are frequently filled with sugar plums and service-oriented architectures--but like any kind of software design, SOA can easily become a tangled mess. Many of the same principles that guide our software design can guide our architecture design. We apply SOLID principles to applications to keep them loosely coupled, we design interfaces so we can send logical messages to our domain objects. We hide our databases behind abstractions because how we access our data shouldn't matter to how we consume it. Rarely, though, do we see the same practices applied to our services and APIs, leaving us with tightly coupled and difficult to extend service-oriented architectures. If you are facing the monorail to SOA challenge, consider looking at your services as objects and your APIs as messages. Service-oriented applications are complex, and the best way to fend off complexity is though object-oriented design."

Speaker:
railsberry.com/speakers#chris

Slides:
speakerdeck.com/railsberry/object-oriented-lessons-for-a-service-oriented-world-by-chris-kelly

Railsberry:
railsberry.com/
twitter.com/railsberry

Loading more stuff…

Hmm…it looks like things are taking a while to load. Try again?

Loading videos…