• Open Menu Close Menu
  • Apple
  • Shopping Bag
  • Apple
  • Mac
  • iPad
  • iPhone
  • Watch
  • TV
  • Music
  • Support
  • Search apple.com
  • Shopping Bag

Lists

Open Menu Close Menu
  • Terms and Conditions
  • Lists hosted on this site
  • Email the Postmaster
  • Tips for posting to public mailing lists
Re: RESTful EOAdaptor for key-value stores
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: RESTful EOAdaptor for key-value stores


  • Subject: Re: RESTful EOAdaptor for key-value stores
  • From: Mike Schrag <email@hidden>
  • Date: Thu, 12 Nov 2009 12:20:41 -0500

The trickiest problem with these stores is relationships ... They typically have very strange (relative to relational) methods of modeling relationships, and many of them also allow dynamic schemas (and often per-instance), which makes it sort of weird to use as an eomodel backing store. You can do all of this, i suspect, but you'll probably have to perform some trickery to really make it generic. To fit it into EO, you'll probably have to enforce some more static, relational kind of restrictions on your data to play nicely. This is actually very similar to the kind of problems the JNDI adaptor has.

JavaRESTAdaptor is kind of crazy. If you're going to write a custom adaptor, I would probably look at the new work quinton did it ERMemoryAdaptor. It's a very simple way to look at the bare minimum you have to implement to make a custom adaptor. JavaRESTAdaptor might be the 2nd one to look at. It wasn't written to be a good example, it was written to be a little crazy :)

If I were you, I would probably not get hung up on integrating this into EOF. I suspect you'll spin your wheels trying to fit square pegs into round holes and end up sacrificing some of the features that make those datastores desirable in the first place. If you do come up with a good mapping, though, it would certainly be cool.

ms

On Nov 12, 2009, at 12:01 PM, Brook, James wrote:

I am thinking about making use of a distributed key-value store for
something I am working on. Perhaps CouchDB, Reddit or Tokyo Cabinet. I
am wondering what the best approach for talking to the database will
be. I am thinking along the lines of an EOAdaptor. I see that Project
Wonder provides an experimental JavaRESTAdaptor (read only). Does
anyone have any experience with this sort of integration? Would my
best approach be to start with javaRESTAdaptor and build a new adaptor
that can handle writes and deletes as well?

It seems that these types of data stores have a lot of potential for
data that is not particularly hierarchical because they are fast and
easily distributed.

Any thoughts would be welcome.

--
James

_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


_______________________________________________
Do not post admin requests to the list. They will be ignored.
Webobjects-dev mailing list      (email@hidden)
Help/Unsubscribe/Update your Subscription:
This email sent to email@hidden


References: 
 >RESTful EOAdaptor for key-value stores (From: "Brook, James" <email@hidden>)

  • Prev by Date: Re: Firefox adding "Pr" to a hidden field?!
  • Next by Date: Re: Postponed validation possible?
  • Previous by thread: RE: RESTful EOAdaptor for key-value stores
  • Next by thread: Re: Firefox adding "Pr" to a hidden field?!
  • Index(es):
    • Date
    • Thread