3 ms·
Spring and other frameworks may be popular, but the base servlet api with db connection pooling is enough. This approach feels much lighter than using framework
by provolone 8y ago
Spring and other frameworks may be popular, but the base servlet api with db connection pooling is enough. This approach feels much lighter than using frameworks. Not sure where the 'over-engineered' view comes from. I'd call that 'sane'.
People complain about the verbosity of Java, but how much time do you spend learning a new framework and all of the gotchas? At the end of the day it seems easier to just write the boilerplate. All of that verbose code means you got exactly what you asked for.
JVM projects never surprise me. When there is a problem debugging is a dream.
- coldtea 8y ago>Spring and other frameworks may be popular, but the base servlet api with db connection pooling is enough. This approach feels much lighter than using frameworks. That. I've used the Servlets API for years in the early to late 00s. I'm now (for the past 5 years) using Express with Node. Static typing and cosmetic differences aside, Servlets and Express (or Node's raw handlers) are pretty much the same API. Request, Response objects, handlers, middleware (iirc we used to call those last "filters" in the Servlet era), etc. It's not like it's some alien convoluted design. (Java Server Faces now was another thing)