I am developing the topic of microblogging service with it's dependency on CouchDB as backend. I become little discouraged by
http://lethain.com/full-text-search-in-couchdb-using-couchdb/
explaining that really it is not good idea. I agree that "use good tools" is something important, reinveting the wheel costs time and effort that could be spend in better way. I really want to have it possible to search through my entries looking for things. Because my CouchDB provider (cloudant.com) has it's Lucene capabilities I felt maybe use it..? But it would be vendor lock-in as it is not CouchDB standard. So why not to choose Lucene by itself. All the plans are pretty expensive but let's try it to build kind of proof of concept..
Then I understood how good it is that my frontend is not directlky talking to couch.. Now I am free to leave some features directly connecting itself to couch while other dispatch to search engine. And everything on one nicely put API endpoint! How pretty
Brak komentarzy:
Prześlij komentarz