tomcat - Which Java EE technologies to use? -
we're building web service scratch, right deciding java ee technologies use.
it looks apache-cxf choice frontend. accessing database, hibernate looks candidate. business logic in between? should ejb3 used?
if ejb3 not used, tomcat candidate app server? if ejb3 used, tomcat still good? or full-fledged java ee server better, glassfishv3 example?
basically asking question java developers did @ point or of careers. should go full blown application server or simpler container open source stack above it. couple of years ago advice go tomcat (or jetty), spring , whatever open source stack feel confortable with. lower turnaround time compensate time needed put together, solution more "lightweight" , simple. today java ee 6 web profile pretty simple , lightweight, glassfish has decent deploy , publishing time, , ejb 3.1 far being monster once (say ejb 2). fire app server , pretty setup (at cost of, maybe, little "service layer overhead" compared using "assemble yourself" frankenstein container). so, matter of personal taste, application may not need ejb (or spring), or may need (and can go tomcat + open ejb or easybeans alternative glassfish). experienced java ee developer migrating java ee 6, can i'm wondering approach best (see jetty 8 + ejb 3.1 + jta + cdi + jpa 2 stack?). not leave empty answer, i'm inclined toward glassfish (as said, setup , turnaround time pretty satisfactory, , think lot easier scale using glassfish cluster doing tomcat + apache + load balance + memcached / terracota / whatever). take (and other answer receive tending toward either tomcat 7 or glassfish) matter of personal opinion.
Comments
Post a Comment