Hello Arthur This topic is more than application server selection. You can use the best application server in the world but if your architecture (including scalability, security, failover etc. ) is not designed well from the beginning of your project, you may be in trouble. It is also very important to understant what you mean by “respond in real-time?” Real time respond in 1 ms, 10 secs, 150 ns ?
You have to consider: - Web servers with HA in mind (for HTML, CSS, JS static delivery, example : Nginx, Apache) - Using CDN (delivering your static contents, images etc. faster and also with no downtime) - Security from start (XSS attacks, DNS attacks etc.) - Clustered databases for scalable RW - Clustered application servers for failure, HA scenarios - In memory /distributed caches to cache mostly used stuff - Client side or server side rendering platforms (JSF or Angular JS with Bootstrap etc.) - WebSocket frameworks (if you use web sockets but it is not globally accepted standard yet) - Also, your architecture must allow you to scale your instances proportional to your application workload etc. As you see, there are lots of consideration to implement such a big system irrespective of the application server you use. Best. Gurkan Erdogdu Founder, ManageCat p. +1 (909) - 366 – 9337 a. 340 S Lemon Ave #7996 Walnut, CA 91789 w. http://managecat.com <http://managecat.com/> e [email protected] <mailto:[email protected]> <http://twitter.com/gerdogdu> <https://tr.linkedin.com/in/gerdogdu> > On 16 Sep 2015, at 23:20, Arthur Portas <[email protected]> wrote: > > Hi, > > to deal with a scenario like this: > "develop a system capable of scaling to support the load of dozens of > countries , and algorithms able to respond in real -time" > what would be your suggestions to draw such a system architecture with > TomEE? > > Love to hear our thoughts! > > Cheers, > > Arthur Portas
