Hi all,
I couldn't find a forum so I am using this list to ask some pretty noob
questions.
I am in the process of deciding the technology to be used in a startup and
I will give you the specs:
Social web app with mobile extensions.
Rest backend.
NoSQL(neo4j probably)
I am trying to decide to use either grizzly or jetty, finding grizzly much
more easy to embed.
I build a prototype using the jersey examples with a grizzly server that
doesn't use servlets. I do not need them, I can filter queries through
jersey filters (and use authentication filters I guess?).
I am wondering, does grizzly use a separate thread for each incoming
request? Are there any tricks for managing connections to the db or each
thread should have its own connection? Do you think in this form grizzly
could function as a server for a large scale application or should I use
the servlet version?
Does the fact that it uses NIO make it any different since my application
is only using the db ? Maybe I can have grizzly also serve the static
content instead of using apache too.
thank you and any insights are welcome.
Best Regards,
Aris Giachnis