vsavkin

Building Rich Domain Models in Rails.

Part 1. Decoupling Persistence.

Abstract

Domain model is an effective tool for software development. It can be used to express really complex business logic, and to verify and validate the understanding of the domain among stakeholders. Building rich domain models in Rails is hard. Primarily, because of Active Record, which doesn't play well with the domain model approach.

One way to deal with this problem is to use an ORM implementing the data mapper pattern. Unfortunately, there is no production ready ORM doing that for Ruby. DataMapper 2 is going to be the first one.

Another way is to use Active Record just as a persistence mechanism and build a rich domain model on top of it. That's what I'm going to talk about in this article.

gaearon

// ------------
// counterStore.js
// ------------

import {
  INCREMENT_COUNTER,
  DECREMENT_COUNTER
} from '../constants/ActionTypes';

const initialState = { counter: 0 };

equivalent

This gist was writen in 2012 and it was solving specific problem in Rails & SimpleForm. Some fellow developers were pointing out this may be out dated concept. That's why I advise everyone to read comment section bellow to have a full grasp of alternative solutions

other sources that may be helpful to understand why this may not be best idea:

• Why Ruby doesn’t have a Boolean class

briandoll

To toast:

• Make sure you have ImageMagick installed (brew install imagemagick)
• Change line 7 of toast.rb to the repository name you're working with
• toast!

$ bundle install
$ ./get_token [user] [pass]
$ export GHUSER=[myuser]

viola

-- model
some sort of constant hash: 
HASH_NAME = {
 0 => "Choose:",
1 => "On-Campus Recruiting - CSO",·
2 => "CSO Staff Referral",
3 => "Faculty Contact",·
4 => "Career Day",·
5 => "CSO Summer Job Listing",·
6 => "Alumni Contact",·

defunkt

# If your workers are inactive for a long period of time, they'll lose
# their MySQL connection.
#
# This hack ensures we re-connect whenever a connection is
# lost. Because, really. why not?
#
# Stick this in RAILS_ROOT/config/initializers/connection_fix.rb (or somewhere similar)
#
# From:
#   http://coderrr.wordpress.com/2009/01/08/activerecord-threading-issues-and-resolutions/

abinavseelan

import React, { Component } from 'react';
import { render } from 'react-dom';
import InputTrigger from 'react-input-trigger';

class App extends Component {
  constructor() {
    this.state = {
      top: null,
      left: null,
      showSuggestor: false,

gvarela

# A sample Gemfile
source "http://rubygems.org"

 gem "redis"
 gem 'eventmachine', :git => 'git://github.com/eventmachine/eventmachine.git'
 gem "em-hiredis"
 # gem "em-synchrony"
 gem "em-websocket"

jnx

# Update, upgrade and install development tools:
apt-get update
apt-get -y upgrade
apt-get -y install build-essential
apt-get -y install git-core

# Install rbenv
git clone git://github.com/sstephenson/rbenv.git /usr/local/rbenv

# Add rbenv to the path:

garybernhardt

This document has moved!

It's now here, in The Programmer's Compendium. The content is the same as before, but being part of the compendium means that it's actively maintained.