All geek questions in one place

Which application server should I use? Not a very complicated application, data conversion, data sending

I am writing some application that will run in the background (Windows service? Maybe some application server?) The application receives some data, then converts / packs / optimizes to another stream, and then sends data to another stream next server (using WebServices). There will be a thick client (possibly Swing) to monitor the entire process through WebServices. The entire application will be written by my team (so there is no need to use complex integration services). The application will be composed of loosely coupled classes (a simple DI template), maybe JMS will be useful?

I wonder what technology I should use. Cat? Glass fish? or maybe something easier? Spring server?

+3
source share
2 answers

You do not need an application server. Keeping it as light as possible is a good choice. My suggestion for you is to use a lightweight structure that supports DI, transforms, threads / sed and integration (by calling weservices) out of the box so you can focus on your application logic. Frames like Apache Camel , Mule , etc. Good candidates.

+2
source

Tomcat . spring.

java- .

JBoss Glassfish.

0

Source: https://habr.com/ru/post/1778746/

More articles:


All Articles