[ 
https://issues.apache.org/jira/browse/CAMEL-4878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Raul Kripalani updated CAMEL-4878:
----------------------------------

    Description: 
As you know, NoSQL technology is evolving at an impressive rate and the 
adoption is increasing tremendously. 

One of the most popular databases in this area is definitely MongoDB, a 
highly-performant, scalable, schema-less database which stores information as 
flexible documents (meaning JSON payloads, not Office, PDF, etc. or binary 
formats). 

Unfortunately, the only support I have found for MongoDB is an Idempotent 
Repository implementation backed up by Mongo 
(https://github.com/catify/camel-mongodb). 

My proposal is to create a Camel component to support CRUD operations on 
MongoDB databases. In most cases it will be a producer (create, read, update, 
delete), but it could also act like a consumer performing scheduled polls 
(read-only) to fetch information from a collection. MapReduce support can also 
be provided for complex queries. 

When it comes to licensing there should be no restriction since the Java driver 
is licensed under the Apache license 
(http://www.mongodb.org/display/DOCS/Licensing). 

For more info see 
http://camel.465427.n5.nabble.com/DISCUSS-Camel-and-MongoDB-td5117168.html

  was:
As you know, NoSQL technology is evolving at an impressive rate and the 
adopting is increasing tremendously. 

One of the most popular databases in this area is definitely MongoDB, a 
highly-performant, scalable, schema-less database which stores information 
as flexible documents (meaning JSON payloads, not Office, PDF, etc. or 
binary formats). 

Unfortunately, the only support I have found for MongoDB is an Idempotent 
Repository implementation backed up by Mongo ( 
https://github.com/catify/camel-mongodb). 

My proposal is to create a Camel component to support CRUD operations on 
MongoDB databases. In most cases it will be a producer (create, read, 
update, delete), but it could also act like a consumer performing scheduled 
polls (read-only) to fetch information from a collection. MapReduce support 
can also be provided for complex queries. 

When it comes to licensing there should be no restriction since the Java 
driver is licensed under the Apache license ( 
http://www.mongodb.org/display/DOCS/Licensing). 

For more info see 
http://camel.465427.n5.nabble.com/DISCUSS-Camel-and-MongoDB-td5117168.html

    
> Create a Camel component for MongoDB
> ------------------------------------
>
>                 Key: CAMEL-4878
>                 URL: https://issues.apache.org/jira/browse/CAMEL-4878
>             Project: Camel
>          Issue Type: New Feature
>            Reporter: Raul Kripalani
>            Assignee: Raul Kripalani
>
> As you know, NoSQL technology is evolving at an impressive rate and the 
> adoption is increasing tremendously. 
> One of the most popular databases in this area is definitely MongoDB, a 
> highly-performant, scalable, schema-less database which stores information as 
> flexible documents (meaning JSON payloads, not Office, PDF, etc. or binary 
> formats). 
> Unfortunately, the only support I have found for MongoDB is an Idempotent 
> Repository implementation backed up by Mongo 
> (https://github.com/catify/camel-mongodb). 
> My proposal is to create a Camel component to support CRUD operations on 
> MongoDB databases. In most cases it will be a producer (create, read, update, 
> delete), but it could also act like a consumer performing scheduled polls 
> (read-only) to fetch information from a collection. MapReduce support can 
> also be provided for complex queries. 
> When it comes to licensing there should be no restriction since the Java 
> driver is licensed under the Apache license 
> (http://www.mongodb.org/display/DOCS/Licensing). 
> For more info see 
> http://camel.465427.n5.nabble.com/DISCUSS-Camel-and-MongoDB-td5117168.html

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: 
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to