> No web Gateway Interface like WSGI and Rack It uses http, which is much more standardized, used and accepted than Rack or WSGI. I can chain together http ser

> No web Gateway Interface like WSGI and Rack It uses http, which is much more standardized, used and accepted than Rack or WSGI. I can chain together http servers, use graphql http redirectors, etc. With WSGI and Rack you’d need a fronting web server to terminate and translate. > No DBMS API/SPI like JDBC. Covered this in another comment. > Express was supposed to be a Microframework like Sinatra and Flask but developers have to spend most of their time defining a robust web server. Doesn’t this mean it is a microframework? As opposed to something like Django that has everything included? > Since the http server and app code are tightly integrated, 12-Factor Apps or JSON API Microservices are more complicated than they need to be in Node. If you are serving up an express app directly with no fronting load balancer then perhaps they are tightly integrated. Otherwise they are not. Express does not and should not handle load balancing.