cassandra-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Gaurav Sharma <gaurav.gs.sha...@gmail.com>
Subject Re: Exposing Cassandra as a Web Service
Date Mon, 17 Jan 2011 06:26:21 GMT
If you have good stories for such an abstraction, then, it can live atop
thrift and extend Tom White's TServlet which is now a part of thrift:
http://svn.apache.org/viewvc/thrift/branches/0.6.x/lib/java/src/org/apache/thrift/server/TServlet.java
http://www.lexemetech.com/2007/09/java-servlet-for-thrift.html (brief
explanation)

Maybe others feel differently but imo, an http ws-client does not have to be
bundled with Cassandra (data-store). Also, Thrift is really fast by itself.
Please see if you want to plug into TServlet; let me know if you want to
pair up and quickly crank out a simple ws client.

-gshx

On Sun, Jan 16, 2011 at 11:18 PM, indika kumara <indika.kuma@gmail.com>wrote:

> Gaurav - I thought of enabling a WS-client to call Cassandra server nodes
> directly.  For that, there should be a web-service engine to process the
> WS-requests in the server-side. A client can be any WS-client that can call
> a service using the service's WSDL. A client can use different protocol
> such
> as TCP, HTTP/S, JMS, etc. Accessing the resources in the Cassandra in a
> RESTFUL manner may also be possible.
>
> Thanks,
>
> Indika
>
> On Mon, Jan 17, 2011 at 4:04 AM, Gaurav Sharma
> <gaurav.gs.sharma@gmail.com>wrote:
>
> > Indika - what use cases do you have in mind for the ws-clients connecting
> > directly to Cassandra especially since you mention connections from
> clients
> > using ws-security? Are you suggesting remote connections over https
> > directly
> > to the data-store between non-colocated client and server nodes? The
> client
> > in such a scenario will also likely have the server-side business logic.
> > right - is that what you have in mind?
> >
> > Currently, there's already an excellent java client library Hector (
> > https://github.com/rantav/hector) and a Thrift API (allows
> cross-language
> > rpc kind of like a web-service mediator/engine). So, there are good
> > client-integration options with 'almost' minimal external lib
> dependencies.
> > Especially with java, imho, additional binary dependencies that result in
> > the jar-hell phenomenon is quite irksome for most users. Axis has a few
> lib
> > dependencies of its own, too.
> >
> > -gshx
> >
> > On Sun, Jan 16, 2011 at 11:50 AM, indika kumara <indika@apache.org>
> wrote:
> >
> > > Hi All,
> > >
> > > What would you think about the idea of exposing the Cassandra as a Web
> > > Service so that any web service client can connect to the Cassandra
> > server?
> > >
> > > This would require embedding a web service engine in the server side,
> > > providing WSDL(s) for Cassandra’s services such as management, data
> > access,
> > > etc.
> > >
> > > If this task can be done, it is possible to connect to the Cassandra
> > > through
> > > different languages, different transports such as TCP, HTTP, JMS, etc.
> > > Moreover, the connection between clients and the Cassandra can be
> secure
> > > (WS-Security), and reliable.
> > >
> > > If this task is worth, I may be able to contribute for implementing it.
> I
> > > am
> > > familiar with the Axis2 web service engine [1], and an Apache
> committer.
> > >
> > > Your suggestions are welcome!
> > >
> > > Thanks,
> > >
> > > Indika
> > >
> > > [1] http://axis.apache.org/axis2/java/core/
> > >
> >
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message