Share this page!

Oliver Jumpertz Profile picture
Twitter logo
17 Dec, 6 tweets, 2 min read
Five Node.js web frameworks you could use to build your next API!

🧵⏬ Five Node.js web frameworks you could use to build your next
1️⃣ express

This is the classic and by far the most popular Node.js web framework.
It's fast, has a minimalistic approach, and doesn't get in your way.

You'll find the most tutorials for express, but it's still relatively easy to learn.

github.com/expressjs/expr…
2️⃣ koa

koa is quite similar to express, but tries to give you more freedom and less complexity.

It has a middleware stack that flows in a stack-like manner, allowing you to perform actions downstream then filter and manipulate the response upstream.

github.com/koajs/koa
3️⃣ sails

sails aims to resemble an MVC-like architecture pattern known from frameworks like Rails.

It provides support for modernized and data-oriented development.

github.com/balderdashy/sa…
4️⃣ Nest

Nest aims at being the enterprise-grade Node.js web framework.

If you ever took a look at Spring in the Java ecosystem, you'll notice at least some similarities.

It is a framework that sits on top of express or fastify.

github.com/nestjs/nest
5️⃣ fastify

fastify aims to provide what its name suggests, performance. And all that without sacrificing developer experience or productivity.

It comes with schema validation, is really fast, and is extendable.

fastify.io

• • •

Missing some Tweet in this thread? You can try to force a refresh
　

Keep Current with Oliver Jumpertz

Oliver Jumpertz Profile picture

Stay in touch and get notified when new unrolls are available from this author!

Read all threads

This Thread may be Removed Anytime!

PDF

Twitter may remove this content at anytime! Save it as PDF for later use!

Try unrolling a thread yourself!

how to unroll video
  1. Follow @ThreadReaderApp to mention us!

  2. From a Twitter thread mention us with a keyword "unroll"
@threadreaderapp unroll

Practice here first or read more on our help page!

More from @oliverjumpertz

Oliver Jumpertz Profile picture
18 Dec
AWS Lambda is an awesome offering. You provide the code, AWS handles the infrastructure and execution for you.

But where is your code actually executed? How does AWS do it?

I recently tried to find it out for myself, and this thread is the result of what I learned!

🧵⏬
1️⃣ Thinking about Lambda

We know that we can write a script that looks like below, and then upload it to AWS while they take care of everything else.

And from simply looking at the code, it doesn't look like the usual API method we'd implement in Express. Image
We're exporting a function, so something else must take our code, import it, and then handle everything else. 🤔

Conclusion number one:
Something must run our code.
Read 29 tweets
Oliver Jumpertz Profile picture
17 Dec
Here are three free ebooks to help you with leveling up your JavaScript skills!

🧵⏬
1⃣ Eloquent JavaScript

Eloquent JavaScript is pretty good at giving you a lot of examples of how to not use JavaScript.

If you try to improve your overall skills and learn how to actually use JS, I can recommend this one!

⛓️ eloquentjavascript.net
2⃣ You Don't Know JS

This is the first (complete) installment of the series, with a second one on the way.

If you're looking for a great book to dive into JS, this one's definitely for you.

⛓️ github.com/getify/You-Don…

⛓️ github.com/getify/You-Don…
Read 4 tweets
Oliver Jumpertz Profile picture
14 Dec
What actually is a Pod in Kubernetes?

If you ever read at least a little about Kubernetes or followed a simple tutorial, you must have come across the term "Pod".

In case you're still wondering what it is, this thread is for you!

🧵⏬
1️⃣ What is it?

A Pod is the smallest deployable unit in Kubernetes.

It's a group of one or more containers that form a logical local host. They share their storage, their network, are always co-located and co-scheduled.
The most common use case is having a Pod with exactly one container. Having multiple containers within a Pod is usually a pretty advanced use-case.

So, naively spoken, a Pod is often only a wrapper around one container.
Read 20 tweets
Oliver Jumpertz Profile picture
12 Dec
Kubernetes vs Serverless offerings

Why would you need Kubernetes when there are offerings like Vercel, Netlify, or AWS Lambda/Amplify that basically manage everything for you and offer even more?

Well, let's try to look at both approaches and draw our own conclusions!

🧵⏬
1️⃣ A quick look at Kubernetes

Kubernetes is a container orchestrator and thus needs containers to begin with. It's a paradigm shift to more traditional software development, where components are developed, and then deployed to bare metal machines or VMs.
There are additional steps now: Making sure your application is suited to be containerized (12-factor apps, I look at you: 12factor.net), containerizing the application, following some pretty well-proven standards, and then pushing the image to a registry.
Read 35 tweets
Oliver Jumpertz Profile picture
11 Dec
A gentle introduction to Kubernetes (short: K8s)

You might have heard the name Kubernetes already and can't really imagine what it is, or you've already heard about it but still need a little more info.

No matter what your background is, this thread is for you!

🧵⏬
1️⃣ What is Kubernetes?

Kubernetes is an open source container orchestration platform. It basically handles everything related to deploying, managing and scaling containerized applications.

Its name originates from Greek, meaning something like pilot.
You might have already worked with Docker and created a few containers, started them, and then used it to deploy a database to test your app locally.

And now imagine that you want to take your app, containerize it, and deploy it to a server.
Read 25 tweets
Oliver Jumpertz Profile picture
27 Nov
DI - Dependency Injection

Dependency injection is a technique in which an object receives other objects it depends on.

It is actually one form of the broader technique inversion of control.

🧵👇🏻
1⃣ What is it?

Dependency injection is a technique where every other object (service) an object (client) depends on is injected from the outside.

So instead of simply instantiating everything on its own, a class relies on it being passed in from the outside.
You can also view it this way:

Imagine your favorite RPG character could only wear the equipment they started with. No way to change the equipment or the look of your character's equipment from the outside.

Would be boring and inflexible, wouldn't it?
Read 13 tweets

Did Thread Reader help you today?

Support us! We are indie developers!

This site is made by just two indie developers on a laptop doing marketing, support and development! Read more about the story.

Become a Premium Member ($3/month or $30/year) and get exclusive features!

Become Premium

Too expensive? Make a small donation by buying us coffee ($5) or help with server cost ($10)

Donate via Paypal Become our Patreon

Thank you for your support!

Follow Us on Twitter!

Like this author's thread?

Get emails when @oliverjumpertz has new unrolls!

Check out other threads from @oliverjumpertz!

Read all threads by @oliverjumpertz