@bsbodden and @hsgubert: I'm going to switch gears to some other things for a bit, but I wanted to get your thoughts on the following for when I get some time to come back to the topic of migrations in a few weeks.

It seems to me that this gem has three component parts:

• configuration and session management
• rails migrations
• query helpers

It also seems to me that every application (not just rails applications) needs the first problem solved.

What would y'all think about creating a separate cassandra-configuration gem that could be responsible for management of cassandra.yml and client/cluster/session management best practices?

Short term, cassandra_migrations could depend on and utilize the cassandra-configuration library. I think this simplifies maintenance of this library and benefits the community who are mostly baking their own solutions to the cassandra-configuration problems (that library would allow them to solve the problem in a lightweight and generic way).

Longer term, I think it would make sense to have something like

• cassandra-configuration
  • Standalone configuration and session management
  • Depends on cassandra-driver
• cassandra-migrations
  • Configurable versioned migration management and DSL
  • Depends on cassandra-configuration
• cassandra-migrations-rails
  • Rails generators, tasks, and helpers for cassandra migrations the Rails Way
  • Depends on cassandra-migrations and rails
• cassandra-queries
  • Query abstraction layer for Cassandra Ruby driver
  • Depends on cassandra-configuration

Thoughts?

cc: #52