[jboss-user] [Beginner's Corner] - Java EE Application Structure for 'always on' data gathering

[Matthew Bellinger]

Matthew Bellinger [https://community.jboss.org/people/mbelling] created the discussion

"Java EE Application Structure for 'always on' data gathering"

To view the discussion, visit: https://community.jboss.org/message/789347#789347

--------------------------------------------------------------
One of the projects I am working on will be receiving data from an external source, and constantly processing that data.  The plan is to build on top of Java EE/JBoss that application, and an application for accessing th

[Josiah Haswell]

Josiah Haswell [https://community.jboss.org/people/haswellj] created the discussion

"Re: Java EE Application Structure for 'always on' data gathering"

To view the discussion, visit: https://community.jboss.org/message/789971#789971

--------------------------------------------------------------
Hi Matt,

I'm not really sure I fully understand the question, but I suspect the answer is "it depends."  What sort of data are you gathering? How are you gathering it?  By "always on" do you mean you have some service that you *need* hard guarantees as to its availability?  I would probably begin by identifying what your application needs to do exactly, then posing questions about the specifics as you encounter difficulties in implementing it.  You might look into SOA or ROA and the relevant Java technologies (e.g. Switchyard) to see if those address your needs.

Best!


Joe
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/789971#789971]

Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075]

[Matthew Bellinger]

Matthew Bellinger [https://community.jboss.org/people/mbelling] created the discussion

"Re: Java EE Application Structure for 'always on' data gathering"

To view the discussion, visit: https://community.jboss.org/message/790536#790536

--------------------------------------------------------------
Hi Joe,

To add more detail: I will be receiving seperate xml data types over several JMS connections.  By always on, I mean that I will constantly be connected to and listening on the JMS connections for messages. Those messages will get distibuted to different modules for processing, and the results from each module will be cached/stored and updates will be sent to connected clients.  The cache/storage will be there for any new client that connects, which will need the full 'state'.

I am an experienced Java developer, but up to this point I have only been doing JSVC and Apache Felix OSGi processes.  I am unfamiliar with Java EE, and am not even sure if my 'problem' fits in the Java EE solution set.  I was given this task and told that I have 'free reign' to look in to new technologies that would facilitate high data load, clustering, high availability, etc.  Hence my questions here. :)

Thank you for any insight you may provide,
~Matt
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/790536#790536]

Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075]

[Josiah Haswell]

Josiah Haswell [https://community.jboss.org/people/haswellj] created the discussion

"Re: Java EE Application Structure for 'always on' data gathering"

To view the discussion, visit: https://community.jboss.org/message/792210#792210

--------------------------------------------------------------
Hi Matt,

Sorry about the delay.  I have worked on similar projects, and JEE/JMS works well for this sort of thing.  Another technology you might consider is http://akka.io/ Akka, which could easily help you implement the message distribution.  JEE is a good candidate for this sort of project if you also need things like persistence, web capabilities, JNDI, etc.  Obviously, most JEE containers implement clustering and failover, too, which is a big mark in their favor.  For very high message volumes, you always need to get creative with caching, load-balancing, batching, etc., but in my experience, JEE scales very well out of the box (to, depending on the task and configuration, 10s to 100s of thousands of operations/second)

Best!

Josiah
--------------------------------------------------------------

Reply to this message by going to Community
[https://community.jboss.org/message/792210#792210]

Start a new discussion in Beginner's Corner at Community
[https://community.jboss.org/choose-container!input.jspa?contentType=1&containerType=14&container=2075]