Back to Home

Daily Blog Reads

Daily dose of intriguing post in different websites

•3 min read

API with NestJS, Rate limiting using Throttler

When building a REST API, we must prepare for various cases. At first, everything might run smoothly, but as our API gains traction, we might encounter some issues. We might run into users who begin sending hundreds or thousands of requests per second, pulling data far more often than necessary. This might cause our server to struggle to keep up. This might make our API slow or unresponsive for other users. We can also encounter attackers launching a Denial of Service (DoS) attack, flooding our API with millions of requests, and crashing our system intentionally.

NestJS
Advanced

•3 min read

API with NestJS, Database normalization with Drizzle ORM and PostgreSQL

Database normalization is a key part of database design, but it’s often explained in complicated terms. In this article, we’ll break down the normalization rules and provide down-to-earth examples using Drizzle ORM and PostgreSQL. Database normalization aims to avoid unnecessarily duplicating our data and make it easier to manage. It does that through specific rules called the normal forms. They might seem complex at first, but they are pretty simple once explained in a straightforward way.

NestJS
Advanced
Database

•3 min read

Frontend Masters, SVG triangle of compromise

I enjoyed Micah R Ledbetter’s SVG triangle of compromise and generally think it’s a fair analysis of how any-which-way you use SVG on a page, you’re giving up some kind of nice ability it could have. For instance, if you use SVG through an <img> tag, it’s cached nicely, but you give up on CSS reaching in there to style things. If you drop it in as <svg>, you can style, but then it’s not cached well for repeated uses.

CSS
Performance
SVG

•3 min read

Frontend Masters, Web Performance Guide

I like how working on web performance is so well aligned with other worthy goals. A fast site is site more accessible to other people. A fast site tends to convert better. Using web standards and more native web technologies tends to lead to a faster site.

Web
Performance

•3 min read

Frontend Masters, Engineering for Slow Internet

Not everybody has smokin’ fast internet. Wait let me try that again. Most people don’t have smokin’ fast internet, especially not all the time. It’s part of the job to make sure our sites aren’t so slow we’re essentially depriving users access.

Web
Performance

•3 min read

Frontend Masters, Capo.js: A five minute web performance boost

You want a quick web performance win at work that’s sure to get you a promotion? Want it to only take five minutes? Then I got you.

HTML
Performance

•3 min read

Frontend Masters, MillionJS

Million.js caught my eye a few months back because of the big claim it makes: Make React 70% faster. I ended up listening to a podcast with the creator, and the meat of it is: it removes the need for “diffing” the virtual DOM that React uses when re-rendering to find what needs to change, which can be slow. I see the project still has momentum, now reaching 3.0.

MillionJS
Performance
React

•3 min read

WebSockets vs Long Polling vs Server-sent events

In today's digital landscape, real-time communication is essential for keeping users engaged. Social media platforms and live sports streaming services, for instance, require immediate updates, a standard that the traditional request-response model of client-server interaction often finds challenging to satisfy. To address this, technologies such as WebSockets, Long Polling, and Server-Sent Events have emerged, enabling more dynamic client-server interactions. This topic will dive into how these technologies differ and how they enhance the user experience.

WebSocket
NodeJS