Skip to main content

Home/ Larvata/ Group items tagged nodejs

Rss Feed Group items tagged

Filter: All | Bookmarks | Topics Simple Middle
張 旭

The package-lock.json file - 0 views

nodejs.dev/...the-package-lock-json-file

nodejs

shared by 張 旭 on 22 May 22 - No Cached
  • You don't commit to Git your node_modules folder, which is generally huge, and when you try to replicate the project on another machine by using the npm install command,
  • Even if a patch or minor release should not introduce breaking changes
  • The package-lock.json sets your currently installed version of each package in stone, and npm will use those exact versions when running npm ci
  • ...1 more annotation...
  • The package-lock.json file needs to be committed to your Git repository
  • 張 旭 on 22 May 22
     
    "You don't commit to Git your node_modules folder, which is generally huge, and when you try to replicate the project on another machine by using the npm install command,"
crazylion lee

Node-RED - 0 views

nodered.org

javascript nodejs pi

shared by crazylion lee on 16 Oct 15 - No Cached
  • crazylion lee on 16 Oct 15
     
    "A visual tool for wiring the Internet of Things"
crazylion lee

shrinkwrap | npm Documentation - 0 views

docs.npmjs.com/shrinkwrap

nodejs npm node

shared by crazylion lee on 11 Jul 16 - No Cached
  • crazylion lee on 11 Jul 16
     
    "Lock down dependency versions"
crazylion lee

deepstream.io | A Scalable Server for Realtime Web Apps - 0 views

www.deepstream.io

nodejs server realtime websocker

shared by crazylion lee on 26 Mar 16 - No Cached
  • crazylion lee on 26 Mar 16
     
    " A Scalable Server for Realtime Web Apps"
crazylion lee

Unitech/pm2 - 0 views

github.com/pm2

nodejs loadbalancing

shared by crazylion lee on 21 Nov 15 - No Cached
  • crazylion lee on 21 Nov 15
     
    "Production process manager for Node.js applications with a built-in load balancer"
張 旭

Scalable architecture without magic (and how to build it if you're not Google) - DEV Co... - 0 views

dev.to/...ld-it-if-youre-not-google-336a

development architecture system google

shared by 張 旭 on 24 Feb 19 - No Cached
  • Don’t mess up write-first and read-first databases.
  • keep them stateless.
  • you should know how to make a scalable setup on bare metal.
  • ...29 more annotations...
  • Different programming languages are for different tasks.
  • Go or C which are compiled to run on bare metal.
  • To run NodeJS on multiple cores, you have to use something like PM2, but since this you have to keep your code stateless.
  • Python have very rich and sugary syntax that’s great for working with data while keeping your code small and expressive.
  • SQL is almost always slower than NoSQL
  • databases are often read-first or write-first
  • write-first, just like Cassandra.
  • store all of your data to your databases and leave nothing at backend
  • Functional code is stateless by default
  • It’s better to go for stateless right from the very beginning.
  • deliver exactly the same responses for same requests.
  • Sessions? Store them at Redis and allow all of your servers to access it.
  • Only the first user will trigger a data query, and all others will be receiving exactly the same data straight from the RAM
  • never, never cache user input
  • Only the server output should be cached
  • Varnish is a great cache option that works with HTTP responses, so it may work with any backend.
  • a rate limiter – if there’s not enough time have passed since last request, the ongoing request will be denied.
  • different requests blasting every 10ms can bring your server down
  • Just set up entry relations and allow your database to calculate external keys for you
  • the query planner will always be faster than your backend.
  • Backend should have different responsibilities: hashing, building web pages from data and templates, managing sessions and so on.
  • For anything related to data management or data models, move it to your database as procedures or queries.
  • a distributed database.
  • your code has to be stateless
  • Move anything related to the data to the database.
  • For load-balancing a database, go for cluster.
  • DB is balancing requests, as well as your backend.
  • Users from different continents are separated with DNS.
  • Keep is scalable, keep is stateless.
  • 張 旭 on 24 Feb 19
     
    "Don't mess up write-first and read-first databases."
crazylion lee

GitHub - olark/up: Zero-downtime reloads and requests load balancer based on distribute. - 0 views

github.com/up

nodejs load balancing

shared by crazylion lee on 21 Feb 18 - No Cached
  • crazylion lee on 21 Feb 18
     
    "Zero-downtime reloads and requests load balancer based on distribute."
crazylion lee

taiko - 0 views

www.npmjs.com/taiko

puppeteer nodejs

shared by crazylion lee on 26 Jan 18 - No Cached
  • crazylion lee on 26 Jan 18
     
    "An easy to use wrapper over Google Chrome's Puppeteer library."
crazylion lee

Total.js Messenger - Total.js - 0 views

www.totaljs.com/messenger

nodejs slack chat

shared by crazylion lee on 14 May 17 - No Cached
  • crazylion lee on 14 May 17
     
    " Total.js Messenger is a small alternative to Slack. Our solution is small, fast and open-source web application which you can customize it by your needs. Try our great solution as a communication channel in your company or sell it for your customers."
crazylion lee

Cleaver - 0 views

jdan.github.io/cleaver

presentation markdown nodejs

shared by crazylion lee on 14 May 17 - No Cached
  • crazylion lee on 14 May 17
     
    "30-second slideshows for hackers"
crazylion lee

Server.js - server.js - 0 views

serverjs.io

nodejs express framework

shared by crazylion lee on 05 Nov 17 - No Cached
  • crazylion lee on 05 Nov 17
     
    "server.js for Node"
張 旭

Gracefully Shutdown Docker Container - Kakashi's Blog - 1 views

kkc.github.io/...ully-shutdown-docker-container

docker process nodejs

shared by 張 旭 on 17 Nov 20 - No Cached
  • The initial idea is to make application invokes deconstructor of each component as soon as the application receives specific signals such as SIGTERM and SIGINT
  • When you run a docker container, by default it has a PID namespace, which means the docker process is isolated from other processes on your host.
  • The PID namespace has an important task to reap zombie processes.
  • ...11 more annotations...
  • This uses /bin/bash as PID1 and runs your program as the subprocess.
  • When a signal is sent to a shell, the signal actually won’t be forwarded to subprocesses.
  • By using the exec form, we can run our program as PID1
  • if you use exec form to run a shell script to spawn your application, remember to use exec syscall to overwrite /usr/bin/bash otherwise it will act as senario1
  • /bin/bash can handle repeating zombie process
  • with Tini, SIGTERM properly terminates your process even if you didn’t explicitly install a signal handler for it.
  • run tini as PID1 and it will forward the signal for subprocesses.
  • tini is a signal proxy and it also can deal with zombie process issue automatically.
  • run your program with tini by passing --init flag to docker run
  • use docker stop, docker will wait for 10s for stopping container before killing a process (by default). The main process inside the container will receive SIGTERM, then docker daemon will wait for 10s and send SIGKILL to terminate process.
  • kill running containers immediately. it’s more like kill -9 and kill --SIGKILL
1 - 14 of 14
Showing 20▼ items per page