Keyspace isn't meant to be globally configured; each Keyspace instance can have a connection pool, which is lazily created if the configuration specifies a pool size. Otherwise, it just lazy-initializes a single instance variable, leaving it up to the user to make sure keyspaces are being used in a thread-safe way.
…k with sidekiq
When creating a default_scope, we don't want to make a connection to Cassandra, because we may later fork, in which case the connection will be shared between processes, to bad effect. Instead, lazily initialize the connection the first time we need to make a call to Cassandra.