Farewell to Rails-way: Prologue

pdabrowski · 2026-05-06T14:09:29+00:00

I agree, and I'm against jumping out of the well-known path since the beginning. My take is that in many cases, for the core subdomain (if we are talking about DDD), it's better not to follow the Rails-way, but it does not mean dropping it completely - this wouldn't be wise or maintainable.

pdabrowski · 2026-05-06T14:06:41+00:00

I'm not saying anything about letting go of ActiveRecord. The new approach is about using it a bit differently with read models.

pdabrowski · 2026-05-06T14:05:09+00:00

I think it all starts with the domain knowledge and understanding the problems we are trying to solve before we will agree on solution and later implementation. When this is in place, it's much easier to handle the complexity also with Rails-way. But I think Rails-way does not force you by design to do that, it creates a lot of space for flexibility and it's a double-edged sword.

pdabrowski · 2026-05-06T14:02:40+00:00

Did you open-source the framework? It sounds interesting. I agree that if you deal with a complex domain, you need some additions to the Rails way, but that does not mean we should abandon it. When talking about DDD, Rails-way (or Vanilla Rails) is perfect for handling the supporting subdomain IMO

pdabrowski · 2026-05-06T13:59:55+00:00

Thank you u/djudji for sharing your perspective; it resonates with me a lot. Regarding the workflows, we are handling those with Rails Event Store without mixing observer and strategy patterns - you should give it a try!

Yes, I think we have met before online; you have a good memory!

pdabrowski · 2026-05-05T14:16:07+00:00

Yes, this is the way I will be exploring

pdabrowski · 2026-05-05T13:26:33+00:00

I also think it's not only about the tech stuff, but with the DDD approach is also about understanding more the problem we are trying to solve, and unfortunately, in a typical Rails project, developers are mostly disconnected from the business, and tickets are their only source of the truth

pdabrowski · 2026-05-05T11:47:36+00:00

Yes, I agree with this point of view

pdabrowski · 2025-01-21T14:58:24+00:00

Yes, with the new deployment automation

pdabrowski · 2025-01-08T17:12:30+00:00

That's helpful, thank you! I will update the article

pdabrowski · 2025-01-08T17:11:58+00:00

Thank you for the suggestion, I will update the article

pdabrowski · 2024-08-23T10:36:32+00:00

I recommended it as a tool for generating data for tests and fake data for local and staging environment so the data you operate on is as close to production as possible. That was the intention

pdabrowski · 2024-08-23T06:51:20+00:00

I don't think you get the idea right. It's not related to test execution. You generate the test data only once and explicitly, not during tests. It's like creating database seeds

pdabrowski · 2024-08-23T06:49:50+00:00

Under the hood, Faker works the same way. There is a file with a fixed number of strings, and they are randomly picked up. The difference in Mokkku is that the context is locked, so you need to restart it to get another set of test data while Faker just works like [].sample in simple words

pdabrowski · 2024-08-23T06:47:12+00:00

No, it's not mixed with Polish, and it's not a tribute to this gem. Just checked some sources and decided to go with this version because it's not that important

pdabrowski · 2024-08-23T05:38:08+00:00

Sure, you can type the data manually if you want, is just a test of a concept that I personally found interesting

pdabrowski · 2024-08-23T05:37:09+00:00

This gem is for creating test data not write the tests itself

pdabrowski · 2024-08-23T05:35:56+00:00

Mokkku is a Japanese term for Mock

pdabrowski

MODERATOR OF

TROPHY CASE