Question

I ve been using the following web development stack for a few years:

java/spring/hibernate/mysql/jetty/wicket/jquery

For certain requirements, I m considering switching to a NoSQL datastore with an AJAX frontend. I would probably build the frontend with jQuery and communicate with the web application middleware using JSON. I m leaning toward MongoDB because of more dynamic query capabilities, but am still considering CouchDB.

I m not sure what to use in the middle. Probably something RESTful? My preference is to stick with Java (or maybe Scala or Groovy) since I m using tools like Drools for rules and Shiro for security. But then again, I want to pick something that is quick an easy to work with, so I m open to other solutions.

If you are building ajax/json/nosql solutions, I d like to hear details about what tools you are using and any pros/cons you ve found to using them.

Answer 1

Pick whichever middleware you are most comfortable with.
CouchApp is very experimental at the moment. The main issue is being able to add security to your app without having a standard HTTP pop-up box. This is obviously a big issue for standard web apps.
Try and avoid parsing each DB request in the middleware and rebuilding the query for couchdb. You can make your middleware act like a proxy so most requests are forwarded on without modification. You can also add a security layer in the middlelayer on top of all requests that need authentication.
Pick a middleware/framework with good URL routing capabilities. For example you could route all requests that go to mydomain.com/db/ to couchdb.

Answer 2

If you go with CouchDB, you can use CouchApp which is a set of scripts for deploying an application directly to a CouchDB database. In essence, you skip the middleware and use CouchDB s views, lists, and show functions along with clientside JavaScript to implement the whole app. If your app works in this architecture, it s surprisingly refreshing, simple and cool.

Answer 3

Also if you like the idea of JSON/REST and sticking to JavaScript client to server, the newer generation of Persevere s core, Pintura is pure JS JSON/REST framework that is designed specifically to work well with NoSQL DBs.

Answer 4

I ve been tinkering with a few. Ultimately, I d like to move my controller layer of MVC to the jQuery/javascript frontend and use pure JSON/REST to talk with the backend. Though the backend will need strong security and, for my application some ability to do workflow, queries, and rules.

You also might want to look at:

1) Couldkit, which runs on Tokyo Cabinet. Supports JSONQuery and OAuth. Runs on Ruby/Rack may have enough functionality. Loks like a strong REST implementation. 2) Persevere, which is Java based and strongly supported in Dojo. It is REST-ish but also has some RPC type calls. Seems very powerful overall, with server-side java scripting, etc.

I wouldn t mind hearing how you re coming along.

Cheers, Alex

Answer 5

I wrote a gem called Rack::JSON for exactly this purpose, it acts as a basic REST interface to a MongoDB db. It was inspired by Cloudkit and supports JSONQuery and also runs on Ruby/Rack. It allows you to store and then access/query JSON documents.

友情链接