Skip to main content

Posts

Node Garbage Collection

Garbage Collection Garbage collection (GC) can have a big impact on the performance of your apps. GC is a process that the Node.js runtime regularly runs to clean up any objects that were created and are not used anymore. If you create a lot of objects in your code (or a dependency does) this can slow down your app. It’s therefore a good idea to keep an eye on this. We shipped GC magic dashboard to make this easy for you! Once you upgrade your node package to  1.2.0  and deploy your app a new  Node.js Heap Statistics  dashboard will appear. Let’s look at what data is on the dashboard! Heap Statistics Node.js reserves memory to store your objects in. This is called the “heap”. The top graph in the dashboard displays the total size of your heap, and how much of it is used. If you see a lot of variation here that’s an indication something might be off. In this screenshot we put some load on this test app, and then stopped requesting pages for a bit. You can clearly see ...

NPM Package Size

Every JavaScript project starts ambitiously, trying not to use too many NPM packages along the way. Even with a lot of effort on our side, packages eventually start piling up.  package.json  gets more lines over time, and  package-lock.json  makes pull requests look scary with the number of additions or deletions when dependencies are added. “This is fine” — the team lead says, as other team members nod in agreement. What else are you supposed to do? We are lucky that the JavaScript ecosystem is alive and thriving! We should not be reinventing the wheel every time and trying to solve something that the open-source community has already solved. 👋 As you’re diving into JavaScript dependencies, you might want to dive into AppSignal  APM for Node.js  as well.  We provide you with out-of-the-box support for Node.js Core, Express, Next.js, Apollo Server, node-postgres and node-redis . Let’s say you want to build a blog and you would like to use Gatsby.js. T...

Behavioral Interview

blog Front End Behavioral Interview Front End Behavioral Interview Web Developer Job Interview Questions Front End Behavioral Interview Web Developer Job Interview Questions 1. DESCRIBE A WEB DEVELOPMENT PROJECT YOU WORKED ON FROM START TO FINISH. WHAT APPROACH DID YOU TAKE, WHAT CHALLENGES DID YOU FACE, AND HOW WERE YOU SUCCESSFUL? Tip: Be transparent about what a real web development project looks like for you. Highlight your wins, of course, but don’t shy away from being real about the challenges. Interviewers aren’t looking to hear that you never have setbacks (that’...