ES as primary data store

[xinuc]

Is it possible right now to use this gem to create rails model using only ES?

e.g:

class Article
  include Elasticsearch::Model
  mappings do
    indexes :title
    indexes :body
  end

end

a = Article.new title: "hello", body: "hello body"
a.save

If so, is there any documentation about this?

Thanks.

[karmi]

I've started work on the "persistence" layer for this, it's not yet finished, ETA in couple of weeks. There's a discussion in #4.

[xinuc]

Great!

[karmi]

The working version of the repository pattern implementation added in #71.

[xinuc]

Great work there!

A question though, what is the use case for each pattern?
Should I use the Repository pattern? (the API doesn't quite feel right for me),
or should I wait for the ActiveRecord pattern?

I really wish the DSL mimics something like mongoid's.

[karmi]

The notation you have originally described is indeed typical for the ActiveRecord-like patterns. That is not yet implemented, so if you want to do that, you have to wait for it to be coded (should be released in couple of weeks).

[xinuc]

Thanks.

Is the ActiveRecord pattern implemented on top of the Repository Pattern?

I still don't understand the use case of the Repository Pattern.

[xinuc]

Ah, one more thing.

Will the AR like pattern use ActiveModel and works seamlessly with form helper etc?

Thanks.

[karmi]

Yes, that's the main motivation, to be a drop-in replacement for ActiveRecord::Base based models.

[pepe]

This look really nice, thank you!

[karmi]

Closing this, let's centralize the discussion in #78.