Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]


Groups > comp.lang.java.programmer > #33449

Re: Java distributed architecture

From Arne Vajhøj <arne@vajhoej.dk>
Newsgroups comp.lang.java.programmer
Subject Re: Java distributed architecture
Date 2016-01-07 19:03 -0500
Organization Aioe.org NNTP Server
Message-ID <n6muc7$ejn$1@gioia.aioe.org> (permalink)
References <fd758782-c4f0-43be-8fda-4f88046dfa79@googlegroups.com>

Show all headers | View raw


On 1/7/2016 1:05 PM, Philipp Kraus wrote:
> I need some ideas for choosing a component of a distributed Java
> architecture. I have got a three tier architecture (client, database
> server, application server), the client can be a normal browser (HTML
> 5), a Android application (or iOS) and a native Java client, the
> database server should be a NoSQL system like Redis, Couch- or
> MongoDB but I need an idea for the application server component. I'm
> thinking about a Tomcat application or Glassfish. Which kind of
> system can I use? It should be a small fast system (a little bite
> like Node.JS). I'm new within this context, so I would like to get
> some basic information.

I think you have at least 3 options:
A) Java SE application with embedded web/servlet container like Jetty
B) Java EE web/servlet container out of the box like Tomcat
C) Java EE full application server like Glassfish or WildFly (JBoss)

#A is a bit in fashion right now. But I can not see what that solution
provides compared to #B except the need to write more code yourself.

The choice between #B and #C depends on your need. If you need a
transaction manager or message queues or connecting to legacy systems
using non-web protocols, then #C comes with built-in stuff that you can
utilize.

But given your suggested databases and the references to node.js, then
I have a strong feeling that #B will be sufficient for your
requirements.

Code wise I think it is a given that you should have the
application tier expose JSON/HTTP services via JAX-RS.

I am a bit puzzled by your suggested databases. They are
not that common in the Java world.

But they are accessible from Java. And you can even access
them via JPA if you would like to (but if these are the most
natural databases for the problems, then I have feeling that
you are not looking for JPA).

Arne

Back to comp.lang.java.programmer | Previous | Next — Previous in thread | Next in thread | Find similar | Unroll thread


Thread

Java distributed architecture Philipp Kraus <philipp.kraus.flashpixx@gmail.com> - 2016-01-07 10:05 -0800
  Re: Java distributed architecture Arne Vajhøj <arne@vajhoej.dk> - 2016-01-07 19:03 -0500
    Re: Java distributed architecture Philipp Kraus <philipp.kraus.flashpixx@gmail.com> - 2016-01-08 14:07 -0800
      Re: Java distributed architecture Arne Vajhøj <arne@vajhoej.dk> - 2016-01-09 21:02 -0500

csiph-web