Applications are built to solve real-life problems encountered by business. More often than not, a single application is delivered to solve multiple problems. It's time to learn how to organize the solutions to create readable and coherent software. Let’s learn about bounded contexts.
Domain-Driven Design's core interest lays in the domain - the expression of purpose, behavior and goals. In this article, I will show you how to free your domain from the ever-present ORM-driven development.
There is a ton of materials on Domain-Driven Design. There are books, lectures, videos. But how to put all those concepts in code? Take a look if you'd like to see an example DDD application in Ruby on Rails.
Aggregate - in Domain-Driven Design means much more than just a collection. It's a guardian of the state and a validator of rules. It's the key element to any domain model. We are taking a deep dive into DDD aggregates in the context of Ruby on Rails framework.
A quick and precise explanation of how to rescue transactions in Ruby on Rails to stop them from being committed into your database. We describe a common mistake - make sure you don't do the same in your code.
It's Domain-Driven Design exercise. We take the knowledge from articles about Value Objects and Entities and design an entity, as a piece of a domain model.
Entities are omnipresent. They are the backbone and the substance of most applications. We will take a deep dive into the concept of an entity from the Domain-Driven Design's perspective.
Value Objects are one of the building blocks of tactical Domain-Driven Design. They can be used to introduce consistency, testability and readability to our code. The article explains the pattern, shows how to use it with Ruby and guides through the built-in support within the Ruby on Rails framework.
An introduction into the world of Domain-Driven Design in the scope of Ruby on Rails framework.
Afraid to run data migrations in production? Don't be. There are a few easy tricks which can help you feel secure.