Over the years, I've been involved with deploying web sites for many years, and also in pentests of many sites where I see lots of misconfiguration. Throughout this journey, I've witnessed firsthand the significant impact that protocol updates can have. The introduction of HTTP/2 fundamentally altered how we approach web service delivery, prioritizing efficiency and speed. Now, HTTP/3 is poised to do the same, ushering in a new era of web performance and potentially even security.
JavaScript is known as the Wild West of web development. But despite the absence of law and order, there are a few things that even the wildest developers should stick to. These include consistent structure, documentation, and testing. We will take a look at how that works for API documentation with tsoa for Node.js.
A backend programmed in Node.js and executed with Docker is not much use on its own if it cannot be accessed for lack of a client. However, it does not have to have a graphical user interface. A command line tool will do - and is practical in many cases. How does it work?
Anyone developing an application in Node.js not only has to deal with the code itself. It also involves connecting infrastructure, including databases, and the execution layer with Docker. How does that work?
When developing with Node.js, it is not only important to write the actual code, but also to ensure quality. In addition to conscientious code structuring, this also includes applying code guidelines and executing automated tests.
One of the most common uses of Node.js is the development of web APIs. Numerous modules from the community are available for this, covering a whole range of aspects, such as routing, validation, and CORS.
If you develop modern web and cloud applications it’s just a matter of time until you encounter the JavaScript runtime environment Node.js. What is Node.js, how do you install and configure it, and how do you develop with it?
Will Deno make everything better and replace Node.js?
Node.js has long been an established environment for the execution of server-side JavaScript. Modern IT landscapes would be unthinkable without it; companies like Uber or Netflix have been using Node.js for years. But with the release of Deno, a server-side execution environment for TypeScript and JavaScript, this could soon change. Outdated traditions are ended and modern concepts are introduced. Will Deno join the IT landscape or even push the veteran Node.js from its place?
Deno is a new runtime for JavaScript and TypeScript, created by Ryan Dahl - the original creator of Node.js. The project is intended to fix design problems in Node.js described in Dahl's famous talk "10 Things I Regret About Node.js". We talked to Krzysztof Piechowicz (adesso AG) about the differences between Node.js and Deno. In the iJS video, Piechowicz goes into the topic in more detail and shows what is possible with Deno.
Nearly every programming language provides the ability to split the code that makes up a program into multiple files. The #include directive is used for this purpose in C and C ++, while Java and Python have the import keyword. JavaScript was one of the few exceptions up till now, but the new JavaScript standard (ECMAScript 6) changes this by introducing so-called ECMAScript modules. All major browsers already support this new standard – only Node.js seems to be lagging behind. Why is that?