micro

Looks good! Some of its features: - 2.5x faster than Express - Full Express middleware support - Async middleware support - Types out of the box - Modules can be used with built-in `http` module --- I've been a fan of Micro, which is in a similar space. Like Express, I think the existence of an ecosystem of middlewares would be key to adoption - not necessarily many, but enough to cover common needs (parse cookie, handle uploads, etc). https://github.com/vercel/micro

Not the parent commenter, but.. Having only a superficial knowledge of Meteor, I prefer a more modular approach: - React/Preact with context or hooks instead of Redux - Micro for server - https://github.com/zeit/micro - Postgres with Knex for data persistence - https://knexjs.org/ Add authentication, WebSockets, etc., and it starts to look like an ad-hoc framework - except that all layers are generic and replaceable (theoretically) with equivalent features, like using Express or MariaDB. I'm also quite fond of Next.js, which lets me have all the above. https://nextjs.org/

Great article. Anyone working with Node.js should be familiar with these fundamentals. It also demonstrates the simplicity (and dare I say "elegance", though that's subjective..) of Node.js and its concepts. These days my favorite library for writing an HTTP server is micro [0] (and a few middlewares). I like how it provides a minimal, functional layer of abstraction. [0] https://github.com/zeit/micro

Next.js is not prescriptive about your backend stack, it gives you a way to fetch data using `getInitialProps`. At ZEIT most of our APIs are built using Micro: github.com/zeit/micro, which is a very lightweight way to build APIs.

Come to https://github.com/zeit/micro ... :)

I'm really digging https://github.com/zeit/micro on https://zeit.co/now.

Check out Micro as well: https://github.com/zeithq/micro. It's also oriented around single-purpose (single-function) microservices, but pure HTTP.