FatFractal customer forums

Servlets and Ruby => Servlets/Ruby Questions and Answers => Topic started by: jonnycools on February 13, 2014, 08:12:35 PM

Title: Java Servlet Vs. NoServer
Post by: jonnycools on February 13, 2014, 08:12:35 PM
Whats the main differences between the servlet and NoServer?

If I choose to use the servlet to augment my NoServer would I have to implement my own solutions for user authentication, permissions, native SDK, queries, grab bags, server code and such.

It looks like i'd be responsible for managing my own SQL databases? Would that mean I would have to forgo the Grabbag and BackReferences in favor of my own SQL.

Is it a modular approach where I can pick and choose which components I want to use. Like event handlers or client side deserializer?

Where could I find more documentation about this?
Title: Re: Java Servlet Vs. NoServer
Post by: gkc on February 14, 2014, 05:31:08 PM
Hi there,

So our PaaS service allows you to deploy standard Java apps (there's a list of our supported JSRs which Mic can provide) - and yes you are free to choose and build whatever server-side stuff you like. (Our PaaS is superb value compared to any of the competition though)

And yes you would be forgoing the NoServer framework. However it would be very easy to run a PaaS app alongside a NoServer app - basically using the PaaS app to augment or complement the NoServer app.

What is it you're looking to do?
Title: Re: Java Servlet Vs. NoServer
Post by: mholst on February 16, 2014, 11:40:52 AM
Hi there,

The Servlet container currently does not give you direct access to any NoServer functionality. You can finesse it by backing or fronting with a NoServer app.

Our Servlet container is a very lightweight 2.5 container that has JSP and JNDI support and you interface with the persistence natively (i.e., JDBC).

We will be releasing build pack support for PaaS apps very soon that will allow you to choose the stack (i.e., Jetty, Node. Thin, etc.) and services (i.e., Postgres, Mysql, Cassandra, etc.) you want.

NoServer has some very power features that would be very interesting in a PaaS context and I need to discuss this with Gary (the NoServer creator) to see what's doable.

Hope this helps.


Title: Re: Java Servlet Vs. NoServer
Post by: jonnycools on February 21, 2014, 08:05:18 AM
I know learning all about the java servlet. It's a bit too raw for my tastes. There's just too much functionality I would I loose. Perhaps later when I get a handle things I'll revisit the use of a servlet to augment the function of NoServer.

Thanks again for responding