Articles on Microservices

Andrew Hao

Andrew Hao

Evented Rails: Decoupling complex domains in Rails with Domain Events

Raphael Koh In our last Domain-Driven Design discussion, we learned how to group similar business components into application Bounded Contexts, which were separated folders in our Rails apps. This segregated cohesive groups of application code into separate folder structures (bounded contexts), and gave us a jumping-off point to drawing more explicit boundaries between domains in

Stripes
Andrew Hao

Andrew Hao

Bring clarity to your monolith with Bounded Contexts

Check out the video of this talk from ElixirConf 2017 below Monolithic applications are great when you start building your company, but as time progresses, they become difficult to maintain. These codebases, as they grow, easily become Big Balls of Mud. When building large applications in frameworks like Rails, the very convention-over-configuration design principles that made

Rudy Jahchan

Rudy Jahchan

Services and Serverless – Carbon Five LA Talk Night August 17th

The micro-services push is on with developers writing simpler applications that interact with each other. But how do you deploy these services? Manage versions and discoverability? Learn two approaches from our August 17th Talk Night speakers as they cover using Docker or going completely server-less with Amazon Web Services’ Lambda! First we’ll have Samuel Chow,

Andrew Hao

Andrew Hao

Rails, meet Phoenix: add Phoenix to your Rails ecosystem with session sharing

You’ve resolved to build your company’s Next Big Thing in Phoenix and Elixir. That’s great! You’re facing a problem though – all user authentication and access concerns are performed on your Rails system, and the work to reimplement this in Phoenix is significant. Fortunately for you, there is a great Phoenix plug to share session

Lights
Erin Swenson-Healey

Erin Swenson-Healey

An Incremental Migration from Rails Monolithic to Microservices

Your Rails application has become a monolith. Your test suite takes 30 minutes to run, your models grow to several hundred (or thousand!) lines, and feature development slows to a crawl. New members of your team must read through massive amounts of code before they can feel confident making changes. You’ve watched Uncle Bob’s Architecture

What can we help you with?

Tell us a bit about your project, or just shoot us an email.

Interested in a Career at Carbon Five? Check out our job openings.