Go back to the blog

Code Architecture

Learn how to architecture your (Ruby on Rails) applications with this series of practical articles!

We have experience with both — do microservices only when you have dedicated teams for each of them, and they have a clear separation of data, responsibilities, and stacks.

Read full article

As a self-made convention we recommend a following signature of the cache (key):

Read full article

Start with basic responsive HTML and then move to RJS (the JS response rendered on the server) — too many people jump on the hype wagon of React and Vue only to end up hating on rails later once they limited its usefulness enough to use the amazing built-in features.

Read full article

Imagine that you want to have some objects that are soft deleted, some clean-up provided data, and some return calculated properties like total price with tax, etc. They share identical functionality, and sometimes it's easier to have the specific logic built-in — for that we have concerns!

Read full article

Organizing a large and busy application is a non-trivial task. Over the years we started applying the following strategies:

Read full article