Websites like the New York Times can't wait for a twenty-minute build to deliver breaking stories. A CDN-based service like unpkg can't build a static filesystem for every possible npm package without exorbitant storage and compute costs. Yet these services stay fast in spite of the pitfalls of dynamic sites. How?
The 'serverless-jetpack' plugin continues its mission to make Serverless Framework packaging and deployment rocket-fast with new features including parallel build workers, full monorepo support, and a dedicated packaging CLI.
After introducing the 'serverless-jetpack' plugin two weeks ago, we took the entire problem back to the drawing board and came up with an even faster and more robust method of packaging and deploying Serverless Framework applications.
You've been using Redux for a while now. It was exciting at first, but the amount of code you need to ship a new feature is starting to creep upwards. With every new addition to the backend, you find yourself making sweeping changes across the project. Actions, reducers, containers — it feels like you're touching every file in the codebase and you ask yourself: Were things always this complicated?
The Serverless Framework is amazing, but can become incredibly slow to package and deploy applications as projects grow. We introduce the 'serverless-jetpack' plugin, a drop-in replacement for normal Serverless behavior, that offers significantly faster packaging and deployment speed.
Backend services built with the Serverless Framework on AWS Lambda are enormously popular and powerful, but unfortunately often difficult to secure in the cloud. We present the terraform-aws-serverless project, which provides battle-tested, fine-grained IAM privilege isolation to help lock down your Serverless Framework applications.
MongoDB is a document-based NoSQL database, and is a popular choice for applications in the Node ecosystem. This post is about testing in Node with MongoDB, however, and not about why you should or should not use MongoDB, so I’ll leave it to the pundits on Hacker News to hash that out.
A complex distributed computing problem application developers may encounter is controlling access to a resource or entity in a multi-user, concurrent environment. How can we guard against an arbitrary number of concurrent processes from potentially mutating or even having any access to an entity simultaneously?
YesNo is a new library for Node.js that simplifies how we write tests asserting the actual behavior of our HTTP requests.
Long before Node.js famously entered the backend development scene, the tech industry had experienced several evolutions of the "Next Big Thing" with both successful and failed patterns and techniques. In this article, we look at some of the shortcomings of Node.js programming models and how TypeScript offers the hope of increasing the legitimacy of Node.js ecosystem in the enterprise by bringing back some storied and successful programming paradigms from the past.
Node.js engineers spend significant amounts of time developing from the console. The usual workflow I've encountered goes something like: npm run test && node index.js which then dumps pages of text to stdout. Errors can easily go unnoticed when large volumes of output are...