Railo server compared with Java - getrailo/railo GitHub Wiki
##Structure
Various Java techniques have parallels with Railo Server & CFML.
Servlets and POJOs written in Java are comparable to CFCs.
JSPs are comparable to CFMs.
Various EJB services are available in Railo Server, e.g. persistence, event-driven programming, scheduling, security
##Server
Changes to Railo Server are made with the Railo Server administrator. In Java projects, comparable changes, especially relating to injectable resources, are often made in the Java container in use.
##Pros & cons
Pros of Railo
CFML enables very fast prototyping
CFML typically allows for faster development
CFML does not have strong typing, which some developers may prefer
CFML uses a fraction of the amount of code lines Java does
CFML simplifies coding by abstracting away many details from developers
Railo Server can be extended with Java classes and libraries
Railo Server can access a service layer written in Java
No external libraries required for datasources, Amazon, zipping and many other functions
Because Railo Server can be deployed onto any servlet container, clients may be more likely to accept Railo Server than a non-Java product
Training staff to use Railo Server will take a lot less time than Java
IDEs and editors can be much simpler
Existing taglibs can be used in CFML pages
No need to build as this is done when the code is run for the first time
Cons of Railo
CFML does not have strong typing, whereas developers may prefer Java's strong typing
Clients may be resistant to change to Railo Server
Railo Server & CFML do not enforce practices whereas Java does
CFML may not be as flexible as Java because options are abstracted away
IDEs and editors are not as fully featured as Java environments