I've successfully used DRF to integrate with Elasticsearch, and plan to use it in a similar fashion for a Neo4j backend. Two approaches:
1. Build a "formal" b/e, using ModelSerializer as a template, with "under the hood" retrieve, create, update, delete. This approach worked for me with ES because it looks more/less like a flat database. (I used a ES integration package called Bungiesearch, which I customized a bit, esp for index retrievals.) 2. Code up "ad hoc" integration inheriting from the Serializer class. I expect I'll take this approach for Neo, as the query and result model are generally different than table based; my queries will likely be on paths, not nodes. I hope to write some of this up with code detail later this year, but the project is in mid-dev atm. Short answer: yes, I would definitely use DRF to handle much of the "plumbing", e.g., auth/access, url/resource routing, etc. On Tuesday, September 6, 2016 at 3:59:49 PM UTC-7, Rajan Chauhan wrote: > > I want to inquire whether djangorestframework can be used with neo4js > database as backend. I don't have any idea whether Serializers methods > avaliable will work with graph database as backend. > -- You received this message because you are subscribed to the Google Groups "Django REST framework" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/d/optout.
