Node.js Reviews

LakeFS Reviews

Node.js mentions (921)

• Stop Using Fetch() in React: A Better Way To Call Your Backend

  Node >= 22 or higher installed on their local development machine. - Source: dev.to / about 1 month ago

• How to develop an AI agent application

  TypeScript / Node.js: Excellent for building asynchronous backend systems that must stream text data smoothly to thousands of users simultaneously. - Source: dev.to / about 2 months ago

• 7 Hidden Security Vulnerabilities in Modern Node.js Applications

  Because Node.js operates on a single-threaded asynchronous runtime, it is inherently vulnerable to processes that hog the CPU for too long. I absolutely cringe whenever I see developers blindly copy-pasting complex regular expressions from StackOverflow without actually testing their performance impact. - Source: dev.to / about 2 months ago

• Docker basics: Using mkcert and caddy with docker compose to host web services over HTTPS for local development

  This tutorial walks you through setting up a simple Docker Compose project that serves two Node web servers over HTTPS using Caddy as a reverse proxy. You will learn how to use mkcert to generate wildcard certificates and the minimal configuration needed in the Caddyfile and docker-compose.yml to get it all working. - Source: dev.to / 2 months ago

• Do You Vibe Code? A DeAI Primer By Oasis

  Node.js: This is required for Hardhat. You can check if your terminal has it installed by running node -v. It will show a version number, if it is already available. If not, download the LTS version from https://nodejs.org/en, install it, then reopen your terminal and recheck to confirm successful installation. - Source: dev.to / 4 months ago

LakeFS mentions (6)

• Ask HN: AWS S3, Cloudflare R2, GCS, Wasabi, or B2?

  I would add https://github.com/gaul/s3proxy to your list. - Source: Hacker News / over 2 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  * data state - this is contents of both your data and metadata at a given point in time. if your data doesn't fit into a single database, this can be difficult to manage. We use this technology to help us: https://lakefs.io/. - Source: Hacker News / almost 3 years ago

• Dev / Stage / Prod is the wrong pattern for data pipelines

  Saltcured, find these comments super insightful! > Yeah, there's a lot of hidden magic/assumptions in having a "writable snapshot of a specific version" of production data. That's absolutely a huge assumption. This technology has been a game changer for us: https://lakefs.io/ > It becomes a headache when there is too much contention to use these sandboxes, or too much manual effort to reset them to a desired... - Source: Hacker News / almost 3 years ago

• Using git to version control experimental data (not code)?

  You should not store your data in git itself, but rather use git to version your data sets. The currently best option for that is (IMHO) https://lakefs.io though there are a few others in various states of usability/maturity. Source: about 3 years ago

• How are you incrementally testing your data pipelines as you develop them?

  I mean if you're ready to adopt a new framework into your ecosystem this is one of the major usecases for LakeFS. Source: over 3 years ago