Name: Node Congress 2022
Start: 2022-02-17T08:00:00.000Z
End: 2022-02-18T20:00:00.000Z

Lera

Joanna Otmianowska

Robert

Ricardo Machado

Alex Hayton

Ian Sutherland

Vitor Barbosa

Aman Beg

Pratik Ghosalkar

Rishi Narang

Stephen Adams

Panayiotis Georgiou

Varun

Andrey Grunev

Vlad Dumitrica

Kate Bord

Nikunj R. Prajapati

Peter Collins

Peter Denham

Sachin Jambur

Ivina

Sujesh Thekkepatt

Kishen 

Miqdad

Adrián Cejudo García

Zain Fathoni

Bernd Matzner

Ismaeil Shajar

¿Sabes qué está pasando realmente en tu carpeta node_modules? Los ataques a la cadena de suministro de software han explotado en los últimos 12 meses y solo están acelerándose en 2022 y más allá. Profundizaremos en ejemplos de recientes ataques a la cadena de suministro y qué pasos concretos puedes tomar para proteger a tu equipo de esta amenaza emergente. Puedes consultar las diapositivas de la charla de Feross <a href="https://speakerdeck.com/feross/its-a-jungle-out-there-whats-really-going-on-inside-your-node-modules-folder">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Es una jungla ahí fuera: ¿Qué está pasando realmente dentro de tu carpeta Node_Modules?

The talk discusses the importance of supply chain security in the open source ecosystem, highlighting the risks of relying on open source code without proper code review. It explores the trend of supply chain attacks and the need for a new approach to detect and block malicious dependencies. The talk also introduces Socket, a tool that assesses the security of packages and provides automation and analysis to protect against malware and supply chain attacks. It emphasizes the need to prioritize security in software development and offers insights into potential solutions such as realms and Deno's command line flags.

Do you know what’s really going on in your node_modules folder? Software supply chain attacks have exploded over the past 12 months and they’re only accelerating in 2022 and beyond. We’ll dive into examples of recent supply chain attacks and what concrete steps you can take to protect your team from this emerging threat. You can check the slides for Feross' talk <a href="https://speakerdeck.com/feross/its-a-jungle-out-there-whats-really-going-on-inside-your-node-modules-folder">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

It's a Jungle Out There: What's Really Going on Inside Your Node_Modules Folder

Feross Aboukhadijeh

Puedes revisar las diapositivas de la charla de James <a href="https://drive.google.com/file/d/13gAh3Pw8u5fA2lIFwLoYuwB7hheBD67F/view?usp=sharing">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Hacia una Biblioteca Estándar para Runtimes de JavaScript

There is a need for a standard library of APIs for JavaScript runtimes, as there are currently multiple ways to perform fundamental tasks like base64 encoding. JavaScript runtimes have historically lacked a standard library, causing friction and difficulty for developers. The idea of a small core has both benefits and drawbacks, with some runtimes abusing it to limit innovation. There is a misalignment between Node and web browsers in terms of functionality and API standards. The proposal is to involve browser developers in conversations about API standardization and to create a common standard library for JavaScript runtimes.

You can check the slides for James' talk <a href="https://drive.google.com/file/d/13gAh3Pw8u5fA2lIFwLoYuwB7hheBD67F/view?usp=sharing">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Towards a Standard Library for JavaScript Runtimes

James Snell

En los primeros años de Node.js, los diagnósticos y la depuración eran puntos problemáticos considerables. Las versiones modernas de Node han mejorado considerablemente en estas áreas. Características como seguimiento de pila asíncrono, capturas de montón y perfilado de CPU ya no requieren módulos de terceros o modificaciones en el código fuente de la aplicación. Esta charla explora las diversas características de diagnóstico que se han incorporado recientemente a Node. Puedes consultar las diapositivas de la charla de Colin <a href="https://drive.google.com/file/d/1nH56Y5N5MDVU_Bhwl5XcgfQuLya--7mV/view?usp=sharing">aquí</a>.  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Diagnostics de Node.js listos para usar

This talk covers various techniques for getting diagnostics information out of Node.js, including debugging with environment variables, handling warnings and deprecations, tracing uncaught exceptions and process exit, using the v8 inspector and dev tools, and generating diagnostic reports. The speaker also mentions areas for improvement in Node.js diagnostics and provides resources for learning and contributing. Additionally, the responsibilities of the Technical Steering Committee in the TS community are discussed.

In the early years of Node.js, diagnostics and debugging were considerable pain points. Modern versions of Node have improved considerably in these areas. Features like async stack traces, heap snapshots, and CPU profiling no longer require third party modules or modifications to application source code. This talk explores the various diagnostic features that have recently been built into Node. You can check the slides for Colin's talk <a href="https://drive.google.com/file/d/1nH56Y5N5MDVU_Bhwl5XcgfQuLya--7mV/view?usp=sharing">here</a>.  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Out of the Box Node.js Diagnostics

Colin Ihrig

¿Puede Deno ejecutar aplicaciones y bibliotecas creadas para Node.js? ¿Cuáles son los compromisos? ¿Cómo funciona? ¿Qué sigue?

Compatibilidad con Node.js en Deno

Deno aims to provide Node.js compatibility to make migration smoother and easier. While Deno can run apps and libraries offered for Node.js, not all are supported yet. There are trade-offs to consider, such as incompatible APIs and a less ideal developer experience. Deno is working on improving compatibility and the transition process. Efforts include porting Node.js modules, exploring a superset approach, and transparent package installation from npm.

Can Deno run apps and libraries authored for Node.js? What are the tradeoffs? How does it work? What’s next?

Node.js Compatibility in Deno

Bartek Iwanczuk

¿Cuáles son algunos de los problemas del cliente HTTP del núcleo de Node actual y cómo podemos superarlos? Una charla sobre cómo undici intenta llevar el siguiente paso en el HTTP del lado del cliente en Node. Incluye algunos consejos prácticos para usar undici y trampas comunes con algunos comentarios en cuanto a decisiones de diseño de API y planes futuros con un extra de bonificación de la API Fetch. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Evolución del cliente HTTP de Node con undici

The Talk discusses the current state of the Node HTTP client and the problems it faces, including the lack of support for HTTP pipelining and the intrinsic link between request and response objects. The speaker introduces the library Indichy, which aims to provide a more user-friendly API for HTTP in Node. The Talk highlights the performance advantages of using WebAssembly in the Umidigi HTTP client and the plans to include it in Node Core. The speaker also mentions the support for signals and the ability to post requests in Umidigi. Additionally, the Talk covers the customization options in Undici, the different types of dispatchers available, and the potential inclusion of Indichy in Node Core. Future plans include support for HTTP 2 and 3, DNS lookup enhancements, and improvements to fetch and pool scheduling. The Talk concludes by discussing the differences in TCP implementations across operating systems and the considerations for adding Web APIs and standards to Node Core.

What are some of the problems of the current Node core HTTP client and how can we move beyond them? A talk about how undici tries to bring the next step in client side HTTP in Node. Includes some practical advice to using undici and common pitfalls with some commentary in regards to API design decisions and future plans with some extra Fetch API bonus.a <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Evolving the Node HTTP Client with undici

Robert Nagy

En esta charla, obtendremos una demostración en vivo de la construcción de autenticación personalizada. Cuando tienes las herramientas adecuadas (y nosotros las tenemos), la autenticación puede ser bastante simple y segura. Esto es más (y mejor) que simplemente: "Instala esta biblioteca y estás listo para ir". Cuando terminemos, tendremos nuestro propio código de autenticación que puede evolucionar con nuestros requisitos en constante cambio sin necesidad de aprender algunas APIs específicas de la biblioteca. Estaremos aprovechando la Plataforma Web de la manera en que se suponía que debía hacerse para darnos una autenticación del lado del servidor simple y segura para la web. Puedes revisar las diapositivas de la charla de Kent <a href="https://slides.com/kentcdodds/server-side-auth-with-remix-prisma-and-the-web-platform">aquí</a> así como <a href="https://github.com/kentcdodds/node-congress-auth">código de demostración</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Autenticación del lado del servidor con Remix, Prisma y la Plataforma Web

This Talk is about server-side authentication with Remix, Prisma, and the web platform. It covers adding authentication to a Remix app, troubleshooting and login setup, handling user login and session creation, creating user sessions and redirects, handling user ID retrieval and validation, and working with cookies in Remix. The speaker emphasizes that Remix is ready for production and suitable for enterprise apps. Remix simplifies the mental model and improves performance by bridging the network gap between the front end and back end.

In this talk, we'll get a live coded demo of building custom hand-rolled authentication. When you have the right tools (and we do), authentication can be quite simple and secure. This is more (and better) than just: "Install this library and you're good to go." When we're done we'll have our own auth code that can evolve with our ever-changing requirements without a need to learn some library-specific APIs. We'll be leveraging the Web Platform the way it was meant to be done to give us simple and secure server-side authentication for the web. You can check the slides for Kent's talk <a href="https://slides.com/kentcdodds/server-side-auth-with-remix-prisma-and-the-web-platform">here</a> as well as <a href="https://github.com/kentcdodds/node-congress-auth">demo code</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Server-side Auth with Remix, Prisma, and the Web Platform

Kent C. Dodds

Verdaccio es un registro privado y proxy de código abierto y ligero hecho en JavaScript con una configuración totalmente opcional que te permite publicar paquetes privados de Node.js y hacer proxy desde otros registros remotos. En esta charla, aprenderás cinco formas de aprovechar Verdaccio para mejorar tus flujos de trabajo y productividad. Puedes revisar las diapositivas de la charla de Juan <a href="https://speakerdeck.com/jotadeveloper/five-ways-of-taking-advantage-of-verdaccio-your-private-and-proxy-node-dot-js-registry">aquí</a><a href="https://drive.google.com/file/d/1dv0ZOFDTitrUHJfJAgKs6YiO4M8Fxwcs/view"></a><a href="https://drive.google.com/file/d/1dv0ZOFDTitrUHJfJAgKs6YiO4M8Fxwcs/view"></a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cinco formas de aprovechar Verdaccio, tu registro privado y proxy de Node.js

Verdash is a lightweight and proxy private Node.js registry that allows you to host and publish private packages. It offers five ways to use it, including publishing packages with npm workspaces and handling conflicts. Verdash improves project productivity and continuous integration by caching dependencies and versions. Security considerations are important, and Verdash provides security features like rate limiting. It can be used as a registry for open source projects and offers flexibility and customization options.

Verdaccio is an open-source lightweight private proxy registry made in JavaScript with an entirely optional configuration that allows you to publish Node.js private packages and proxy from other remote registries. In this talk, you will learn five ways to take advantage of Verdaccio to improve your workflows and productivity. You can check the slides for Juan's talk <a href="https://speakerdeck.com/jotadeveloper/five-ways-of-taking-advantage-of-verdaccio-your-private-and-proxy-node-dot-js-registry">here</a><a href="https://drive.google.com/file/d/1dv0ZOFDTitrUHJfJAgKs6YiO4M8Fxwcs/view"></a><a href="https://drive.google.com/file/d/1dv0ZOFDTitrUHJfJAgKs6YiO4M8Fxwcs/view"></a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Five Ways of Taking Advantage of Verdaccio, Your Private and Proxy Node.js Registry

Juan Picado

Compilar (o transpilar) JavaScript moderno a versiones compatibles con ECMAScript más antiguas ha permitido que la web evolucione increíblemente rápido mientras nos hace desarrolladores más felices. Pero, ¿cómo funciona el proceso de compilación? ¿Cómo podemos escribir nuestros propios plugins de Babel? ¡Vamos a descubrirlo! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Comprendiendo la Compilación de JavaScript

Today's Talk explores the concepts of compilation and transpilation in JavaScript, highlighting the three steps involved: parsing, code transformation, and code generation. The process of traversing an abstract syntax tree is discussed, with examples of tools like Babel and ESLint that can be used for code transformations. Code transformation tools and techniques, such as CodeShift and T-TypeScript plugin, are introduced, emphasizing the power of abstract syntax trees and the visitor pattern. The summary concludes by encouraging further exploration of code refactoring and transformations using tools like Babel, TSLint, and astexplorer.net.

Compiling (or transpiling) modern JavaScript to older ECMAScript-compatible versions has allowed the web to evolve incredibly fast while making us happier developers. But how does the compilation process work? How can we write our own Babel plugins? Let's find out! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Understanding JavaScript Compilation

Michele Riva

Los errores le ocurren a todos los programadores. Los desarrolladores tienen diferentes opciones: suprimirlo, notificar al usuario, informar al equipo, ignorarlo o escribir código para manejar el error. En esta charla, aprenderás todos los aspectos importantes del sistema de errores de Node.js, los tipos de errores, diferentes formas de entregar un error y patrones para mejorar el manejo de errores, ¡con ejemplos! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Dominando el Manejo de Errores en Node.js

This Talk explores error handling in Node.js, including types of errors, handling techniques, and debugging. It discusses the use of exceptions, callbacks, and promises for error handling. The importance of proper error handling and the benefits of using error classes, expressive error messages, and automated testing are emphasized. The speaker also addresses the use of TypeScript and test-driven development for error prevention. Overall, the Talk provides valuable insights and techniques for mastering error handling in Node.js.

Errors happen to every programmer. Devs have different choices: suppress it, notify the user, report to the team, ignore it or write code to handle the error. In this talk, you will learn all the important aspects of the Node.js error system, the types of errors, different ways to deliver an error, and patterns to improve error handling - with examples! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Mastering Error Handling Node.js

Lizz Parody

Los navegadores modernos vienen equipados con tres tipos de Web Workers: Dedicated, Shared y Service Workers. Aunque cada uno ofrece la capacidad de ejecutar JavaScript en un hilo separado, sus diferentes APIs y capacidades significan que cualquier tarea dada generalmente tiene un trabajador ideal. Aprende los beneficios de cada trabajador y cómo elegir el adecuado. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Una Comparación de Web Workers

This Talk compares web workers, including dedicated workers, shared workers, and service workers. Web workers provide multithreading capabilities and use shared memory for higher performance. Dedicated workers have one parent and can execute on a separate thread. Shared workers can have multiple parents and are useful for communication across different windows. Service workers can intercept and proxy requests made from a web page and are useful for caching network assets and building progressive web apps.

Modern browsers come equipped with three types of Web Workers: Dedicated, Shared, and Service Workers. While each one offers the ability to execute JavaScript in a separate thread, their differing APIs and capabilities mean that any given task usually has an ideal worker. Learn the benefits of each worker and how to choose the right one. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

A Comparison of Web Workers

Thomas Hunter II

Las funciones en el Edge están empujando los límites de la computación sin servidor, pero con nuevas herramientas surgen nuevos desafíos. Debido a sus limitaciones, las funciones en el Edge no permiten conectarse a bases de datos populares como PostgreSQL y MySQL. En esta charla, aprenderás cómo puedes conectar e interactuar con tu base de datos desde Cloudflare Workers utilizando el Proxy de Datos de Prisma. Puedes consultar las diapositivas de la charla de Alex <a href="https://docs.google.com/presentation/d/1b_EYdhlifC1DU8M7JzsGPgjDv9Kijf80/edit?usp=sharing&amp;ouid=108102216742006062181&amp;rtpof=true&amp;sd=true">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Acceso a la base de datos en el Edge con Cloudflare Workers y Prisma

This Talk discusses database access on the edge with CloudFlare workers and the challenges of serverless platforms. It explores solutions for database access, including CloudFlare-specific solutions and using Prisma data proxy. The Prisma toolkit and demo are showcased, demonstrating how to convert an application to use a database. The process of setting up Prisma Data Platform and deploying the application to CloudFlare workers is explained. The Talk concludes with insights on database usage and the differences between serverless, CDN, and the Edge.

Edge functions are pushing the limit of serverless computing – but with new tools, come new challenges. Due to their limitations, edge functions don't allow talking to popular databases like PostgreSQL and MySQL. In this talk, you will learn how you can connect and interact with your database from Cloudflare Workers using the Prisma Data Proxy. You can check the slides for Alex's talk <a href="https://docs.google.com/presentation/d/1b_EYdhlifC1DU8M7JzsGPgjDv9Kijf80/edit?usp=sharing&amp;ouid=108102216742006062181&amp;rtpof=true&amp;sd=true">here</a>.  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Database Access on the Edge with Cloudflare Workers & Prisma

Alex Ruheni

Repasaremos la configuración de Sentry paso a paso para obtener visibilidad en nuestro frontend y backend. Una vez integrado, rastrearemos y solucionaremos errores y transacciones que se muestren en Sentry desde nuestros servicios para comprender por qué/dónde/cómo ocurrieron errores y ralentizaciones en nuestro código de aplicación.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Seguimiento de errores y ralentizaciones en Node + JavaScript utilizando Sentry

Today's Workshop focused on application monitoring using Sentry. The importance of tracking errors, slowdowns, and releases was highlighted, along with the integration process for React, Express, and Node.js applications. The debugging capabilities of Sentry were demonstrated, including identifying errors, slowdowns, and debugging backend issues. Monitoring releases, querying data, and visualizing information were also covered, along with the integration of Sentry with workflow tools. The Q&A session addressed various topics, including the use of Sentry in different environments and its integration with other tools.

We’ll go through setting up Sentry step--step to get visibility into our frontend and backend. Once integrated, we will track and triage errors + transactions surfaced Sentry from our services to understand why/where/how errors and slowdowns occurred within our application code. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Tracking errors and slowdowns in Node + JavaScript using Sentry

Neil Manvar

Estaba viendo código que fue escrito hace unos años, que se consideraba "súper limpio" e "intuitivo", y me di cuenta de que el JavaScript que escribimos hoy es muy diferente al que solíamos escribir hace solo cinco años. Si has estado en esto por un tiempo, conoces la sensación de escribir "this = that" y pasar días depurando por qué esa variable se establece en null. La nueva sintaxis de Node, con esm, nuevos bundlers, refrescos más rápidos. El código nunca fue tan fácil de escribir y entender. Puedes revisar las diapositivas de la charla de Pedro <a href="https://node-like-its-2022.vercel.app/">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Escribe Node como si estuviéramos en 2022

Let's write Node like it's 2022. We can now iterate over objects more easily with the for-in loop. Template literals make string concatenation and multi-line strings much simpler. The structured clone feature allows us to clone complex objects without the need for hacks like stringifying and parsing. Default parameters in JavaScript are now much more convenient. Async await eliminates the need for callbacks. Arrow functions inherit the scope, eliminating the need for 'this equals that'. Const prevents variable reassignment. Let helps catch errors earlier. Write code like it's 2022!

I was seeing some code that was written a few years ago, that was considered the "super clean" and "intuitive", and I realised that the JavaScript that we write today is very different from the one that we used to write just five years ago. If you've been around for some time, you know the feeling of writing "this = that", and taking days debugging why that variable is set to null. The new node syntax, with esm, new bundlers, faster refreshes. The code was never so easy to write and understand. You can check the slides for Pedro's talk <a href="https://node-like-its-2022.vercel.app/">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Write Node like it's 2022

Pedro Filho

Los sitios web estáticos te brindan todo tipo de grandes beneficios. No tienes que preocuparte por la seguridad o la escalabilidad. Son simples de almacenar en caché, baratos de alojar y fáciles de mantener. ¡Pero a veces extraño todas las cosas divertidas que puedes hacer con solo un poco de estado! Combinando la plataforma Cloudflare Pages con Durable Objects y la API HTMLRewriter, ¡puedes tener tu pastel y comértelo también! Replicaremos una experiencia completa de WordPress con comentarios, publicaciones principales, botones de 'me gusta' y un contador de páginas. Todo en la plataforma gratuita de alojamiento de sitios estáticos de Cloudflare. Puedes consultar las diapositivas de la charla de Jonathan <a href="https://docs.google.com/presentation/d/e/2PACX-1vTnimCVlQtNo8Z27-PoYGVBoLDz81XFU-ix5jehQEY7eKI37cnwNx-LXJxwzf6AcOvhDEOq3RTDpnBH/pub?start=false&amp;loop=false&amp;delayms=3000">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Sitios web estáticos primero con Cloudflare Workers

The Talk covers the historical landscape of web development, the rise of static site generators, the serverless revolution, edge computing, and using Cloudflare services to enhance static websites. It explores the challenges of early web development, the shift to static sites and client-side rendering, and the advantages of server-side and client-side rendering. It also discusses Cloudflare services like Cloudflare workers, KV, durable objects, and HTML rewriter for building fast and minimal hosting solutions. The Talk highlights the use of DurableObjects for analytics and integration, dynamic content on static sites, JAMstack, and the advantages of using Cloudflare Workers for automatic deployment, multiple language support, and combining static pages with JavaScript functions. It introduces the concept of edge computing and the difference between Cloudflare Pages and Workers. It also touches on error handling and the use of HTML rewriter, Cloudflare KVstore, and DurableObjects for managing state and storing dynamic data.

Static websites give you all sorts of great benefits. You don’t have to worry about security or scalability. They are simple to cache, cheap to host and a breeze to maintain! But sometimes I miss all the fun things you can do with just a little bit of state! Combining the Cloudflare Pages platform with Durable Objects and the HTMLRewriter API, you can have your cake and eat it too! We’ll replicate a full WordPress experience with comments, top posts, like buttons and a page counter. All on Cloudflare’s free static site hosting platform. You can check the slides for Jonathan's talk <a href="https://docs.google.com/presentation/d/e/2PACX-1vTnimCVlQtNo8Z27-PoYGVBoLDz81XFU-ix5jehQEY7eKI37cnwNx-LXJxwzf6AcOvhDEOq3RTDpnBH/pub?start=false&amp;loop=false&amp;delayms=3000">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Static first websites with Cloudflare Workers

Jonathan Kuperman

Los módulos JSON han sido una característica importante del ecosistema de JavaScript durante mucho tiempo, y ahora están tomando una nueva forma con la nueva sintaxis de importación ESM. Veamos la historia del soporte de JSON en Node.js, su relación con la compatibilidad web y cómo podemos hacer que finalmente suceda.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

El camino hacia el soporte de importación de JSON en Node.js

This Talk discusses the road to JSON import support in NodeJS, covering the history and implementation of JSON modules. It explores security concerns and the proposal for import assertions. The Talk also explains how to use JSON modules in NetJS and the availability of support in different browsers. It mentions working with dynamic imports and future plans for adding more modules in Node Core. Additionally, it addresses the syntax differences between ESM and CommonJS and the challenges of overcoming them.

JSON modules have been an important feature of the JavaScript ecosystem for a long time, and it’s started to take a new shape with there new ESM import syntax. Let’s review the history of JSON support in Node.js, its relationship with web compatibility, and how we can make (finally) it happen. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

The Road to JSON Import Support in Node.js

Antoine du Hamel

Prisma es un ORM de código abierto para Node.js y TypeScript. En esta masterclass, aprenderás los flujos de trabajo fundamentales de Prisma para modelar datos, realizar migraciones de base de datos y consultar la base de datos para leer y escribir datos. También aprenderás cómo Prisma se integra en tu stack de aplicaciones, construyendo una API REST y una API GraphQL desde cero utilizando SQLite como base de datos. Tabla de contenidos: - Configuración de Prisma, modelado de datos y migraciones- Explorando Prisma Client para consultar la base de datos- Construyendo rutas de API REST con Express- Construyendo una API GraphQL con Apollo Server <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Flujos de base de datos y desarrollo de API con Prisma

Welcome to the Database Workflows and API Development with Prisma workshop. Prisma is an ORM that allows you to work with a relational database from an object-oriented programming language. The workshop covers topics such as data modeling, migrations, using Prisma Client for querying the database, and implementing REST and GraphQL APIs. It also highlights the benefits of Prisma, including its intuitive data modeling language, type-safe database client, and migration tool. The workshop provides hands-on tasks and guidance for beginners to get started with Prisma.

Prisma is an open-source ORM for Node.js and TypeScript. In this workshop, you’ll learn the fundamental Prisma workflows to model data, perform database migrations and query the database to read and write data. You’ll also learn how Prisma fits into your application stack, building a REST API and a GraphQL API from scratch using SQLite as the database. Table of contents: - Setting up Prisma, data modeling &amp; migrations- Exploring Prisma Client to query the database- Building REST API routes with Express- Building a GraphQL API with Apollo Server <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Database Workflows & API Development with Prisma

Nikolas Burk

En la era posterior a la Ley de Moore, debido a las limitaciones del hardware, necesitamos exprimir más rendimiento del hardware existente. Eso significa que el código nativo proporciona el mejor rendimiento. Sin embargo, la prevalencia del código nativo en el lado del servidor presenta desafíos para la seguridad y la administración de aplicaciones. El surgimiento y la llegada de Rust y WebAssembly ofrecen nuevas formas para que los desarrolladores escriban aplicaciones Node.js de alto rendimiento pero seguras. En esta charla, cubriré los conceptos básicos de Rust y WebAssembly, así como también mostraré cómo integrarlos con Node.js. Aprenderás cómo y cuándo diseñar una aplicación web híbrida. Cómo puedes codificar las funciones de alto rendimiento en Rust en una máquina virtual de WebAssembly y finalmente cómo unir todo en una aplicación JavaScript de Node.js.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Node.js de Alto Rendimiento Potenciado por Rust y WebAssembly

This talk explores using Rust and WebAssembly to enhance the performance of Node.js applications. By leveraging Rust's efficiency and safety features, and compiling it into WebAssembly bytecode, developers can achieve high-performance computations while ensuring security. WebAssembly enables direct communication with native hardware and is optimized for server-side applications, making it suitable for tasks like AI inference and storage databases. Overall, this talk highlights the potential of combining JavaScript, Rust, and WebAssembly to build performant and portable applications.

In the post Moore’s Law era, due to limitations of the hardware, we need to squeeze more performance from the existing hardware. That means that the native code provides the best performance. However, the prevalence of native code on the server-side presents challenges to application safety and manageability. The rise and advent of Rust and WebAssembly offers new ways for developers to write high performance yet safe Node.js applications. In this talk, I will cover the basics of Rust and WebAssembly, as well showcase how to go about their integration with Node.js. You will learn how and when to design a hybrid web application. How can you code the high performance functions in Rust in a Web Assembly virtual machine and finally how to tie everything together in a Node.js JavaScript application. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

High Performance Node.js Powered by Rust and WebAssembly 

Shivay Lamba

“Nunca creerás de dónde vienen los objetos en JavaScript.” “Estos 10 lenguajes son peores que JavaScript en programación asíncrona.” Exploraremos algunos aspectos de JavaScript que podrías dar por sentado en el taller más sensacionalista de nodecongress.com. Para asistir a este taller solo necesitas ser capaz de escribir y ejecutar código NodeJS en tu computadora. Tanto desarrolladores junior como senior son bienvenidos. Los objetos son de Marte, las funciones son de Venus Sumergámonos en los entresijos de los objetos y luego ampliemos nuestra perspectiva para ver los módulos desde un punto de vista diferente. ¿Cuántas formas hay de crear objetos? ¿Son realmente útiles? ¿Cuándo deberías considerar usarlos? Si ahora estás pensando `¿a quién le importa?`, entonces este taller es probablemente para ti. JavaScript asíncrono: ¿las partes buenas? Tengamos una conversación honesta. Quiero decir... ¿por qué, oh por qué, tenemos que lidiar con todo esto? Supongo que también depende de la perspectiva. Primero asumamos una verdad incómoda al respecto: podría ser peor... luego tal vez podamos empezar a ver las características no tan malas, incluso geniales, de JavaScript en relación a los programas no bloqueantes. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Vuelta a los fundamentos

This workshop covers basic principles and patterns in software development and engineering. It explores topics such as objects, functions, prototype chains, classes, modules, and asynchronous programming in JavaScript. The workshop emphasizes the importance of understanding context, encapsulation, and the use of promises for managing asynchronous behavior. It also discusses the differences between synchronous and asynchronous code execution and provides insights into the design patterns and best practices for writing efficient and maintainable code.

“You’ll never believe where objects come from in JavaScript.” “These 10 languages are worse than JavaScript in asynchronous programming.” Let’s explore some aspects of JavaScript that you might take for granted in the clickbaitest nodecongress.com workshop. To attend this workshop you only need to be able to write and run NodeJS code on your computer. Both junior and senior developers are welcome. Objects are from Mars, functions are from Venus Let’s deep-dive into the ins and outs of objects and then zoom out to see modules from a different perspective. How many ways are there to create objects? Are they all that useful? When should you consider using them? If you’re now thinking “who cares?“, then this workshop is probably for you. Asynchronous JavaScript: the good? parts Let’s have an honest conversation. I mean… why, oh why, do we need to bear with all this BS? My guess is that it depends on perspective too. Let’s first assume a hard truth about it: it could be worse… then maybe we can start seeing the not-so-bad-even-great features of JavaScript regarding non-blocking programs. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Back to the basics

Guillermo Gutierrez Almazor

Tenemos un frontend de JavaScript que se conecta a un backend de Node (Express.js). Vamos a ver cómo saber qué parte es responsable de cada error, cuál es el impacto y todo el contexto necesario para resolverlo.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Monitorización de errores y ralentizaciones con un frontend de JS y un backend de Node

Sentry is code monitoring for developers, specifically designed for the application layer. It helps identify error details, frequency, release, user information, and stack trace. Source maps can be uploaded to see the original source code and suspect commits can be identified. Performance monitoring helps identify slowdowns and determine the cause. Automating alerts and investigating errors helps gain instant context and trace errors across different projects.

We've got a JavaScript frontend hitting a Node (Express.js) backend. We'll go through how to know which party is responsible for which error, what the impact is, and all the context needed to solve it. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Monitoring Errors and Slowdowns with a JS Frontend and Node Backend

Chris Stavitsky

Blitz fue creado como un framework full-stack de React, inspirado en Ru on Rails, y con el objetivo de hacerte lo más productivo posible. Cuenta con una capa de abstracción de datos "Zero-API", autenticación y autorización integradas, y algunas características más emocionantes. Sin embargo, recientemente decidimos cambiar Blitz a un kit de herramientas independiente del framework, lo que significa un cambio enorme y emocionante para la comunidad de Blitz. Durante esta charla, presentaré los conceptos principales, hablaré sobre el por qué y el cómo del cambio, y te daré un vistazo al futuro de Blitz. Puedes ver las diapositivas de la charla de Aleksandra <a href="https://slides.com/aleksandrasikora/blitzjs">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Un vistazo al futuro del desarrollo full-stack con Blitz.js

Today's Talk focused on the future of full-stack web development with Blitz.js. Blitz is a React framework built on top of Next.js, offering direct database access and authentication with authorization. The core features of Blitz include the zero-API layer and the ability to run server code directly from the frontend. The future of Blitz includes expanding to other frameworks and runtime environments. The new Blitz toolkit will be decoupled from any specific framework, allowing developers to choose their preferred foundation. It will retain the core value of Blitz while adding additional features like JWT authentication and advanced data-aware authorization. The migration to the new toolkit will be seamless for existing Blitz projects. The Blitz toolkit will have a plugin system for customization and support multiple resolvers. The Blitz project is currently going through a pivot and will focus on the Blitz toolkit. The goal is to release the toolkit by the end of March. The most exciting part of the toolkit is the plugin system design that allows users to customize their experience.

Blitz was created as a fullstack React framework, inspired Ru on Rails, and with a goal to make you as productive as possible! It features a ""Zero-API"" data layer abstraction, has authn &amp; authz out of the box and a few more exciting features. However, we recently decided to pivot Blitz to a framework agnostic toolkit, which means a huge and thrilling change for the Blitz community. During this talk, I will introduce the core concepts, talk about the why &amp; how of the pivot, and give you a glimpse of Blitz's future. You can check the slides for Aleksandra's talk <a href="https://slides.com/aleksandrasikora/blitzjs">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

A Glimpse Into the Future of Fullstack Development with Blitz.js

Aleksandra Sikora

JavaScript nació en el navegador, Node lo llevó al servidor abrazando primitivas de Unix y E/S asíncrona, y recientemente Cloudflare Workers &amp; Deno Deploy lo llevaron al borde. Veamos hacia dónde se dirigen los runtimes de JavaScript y cómo darán forma al software que escribimos. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

El Futuro de los Runtimes de JavaScript

Today's Talk explores the future of JavaScript runtimes, their evolution, and impact on software development. It discusses the historical trends of JavaScript, the adoption of new tools and libraries, and the convergence of Node and Deno. The emergence of isolate clouds and their potential to replace traditional VMs and containers is also highlighted. Additionally, the talk touches on the possibilities of JavaScript in exotic use cases, its impact on machine learning, and the potential for TypeScript to become the de facto language for JavaScript development.

JavaScript was born in the browser, Node brought it to the server embracing unix primitives and async I/O and lately Cloudflare Workers &amp; Deno Deploy have brought it to the edge. Let’s take a look at where JavaScript runtimes are heading and how it will shape the software we write. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

The Future of JavaScript Runtimes

Aaron O'Mullan

Next.js es un marco convincente que hace que muchas tareas sean sencillas al proporcionar muchas soluciones listas para usar. Pero cuando se trata de autenticación y seguridad del usuario, nuestra misión es hacerla confiable, segura y eficiente. En esta masterclass, nos centraremos en diferentes enfoques de autenticación de usuarios y gestión de sesiones, comenzando desde una estrategia de autenticación personalizada (que construiremos juntos) y terminando aprendiendo cómo identificar e integrar el proveedor de autenticación adecuado (Auth0, Firebase, etc.) para cualquier aplicación. Tabla de contenidos:- Una breve introducción a Next.js- Construyendo un mecanismo de autenticación desde cero- Por qué debemos evitar la autenticación personalizada- Cómo identificar el mecanismo de autenticación y proveedor adecuados- Integración de NextAuth.js, Auth0, Firebase u otro proveedor <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Gestión de la autenticación en Next.js

Welcome to the workshop on managing authentication in Next.js. We'll cover custom authentication methods, integrating Firebase, and the pros and cons of different approaches. We will explore bcrypt for password hashing and comparison, and JWT tokens for authentication. Iron Session will be used for cookie management. The importance of server-side rendering and protecting routes will also be discussed.

Next.js is a compelling framework that makes many tasks effortless providing many out-of-the-box solutions. But when it comes to authentication and user security, it's our mission to make it reliable, secure, and efficient. In this workshop, we'll focus on different user authentication and session management approaches, starting from a custom authentication strategy (that we will build together), and ending learning how to identify and integrate the right auth provider (Auth0, Firebase, etc.) for any app. Table of contents:- A brief introduction to Next.js- Building an authentication mechanism from scratch- Why we should avoid custom authentication- How to identify the proper authentication mechanism and provider- Integrating NextAuth.js, Auth0, Firebase, or any other provider <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Managing Authentication in Next.js

Fastify es un marco de trabajo HTTP para Node.js que se enfoca en proporcionar una buena experiencia de desarrollo sin comprometer las métricas de rendimiento. Lo que hace especial a Fastify no son sus detalles técnicos, sino su comunidad, que está abierta a contribuciones de cualquier tipo. Parte de la fórmula secreta es la arquitectura de complementos de Fastify que permite a los desarrolladores escribir más de cien complementos. Este masterclass práctico está estructurado en una serie de ejercicios que abarcan desde lo básico, como "hola mundo", hasta cómo estructurar un proyecto, realizar acceso a bases de datos y autenticación. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Masterclass de Fastify

The Fastify Workshop covers the basics and advanced topics of the Fastify web framework, known for its speed, security, and developer experience. It has a strong and welcoming community and is highly performant, extensible, and supports JSON schema. The workshop consists of multiple modules where participants build a small app together, adding more features at each step. Topics covered include logging, serialization, testing, code coverage, validation, authentication, decorators, hooks, and auto-loading routes. The workshop emphasizes the use of TypeScript and provides tools like TypeBox for generating JSON schema and defining types.

Fastify is an HTTP framework for Node.js that focuses on providing a good developer experience without compromising on performance metrics. What makes Fastify special are not its technical details, but its community which is wide open for contributions of any kind. Part of the secret sauce is Fastify plugin architecture that enabled developers to write more than a hundred plugins. This hands-on workshop is structured around a series of exercises that covers from basics "hello world", to how to structure a project, perform database access and authentication. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Fastify Workshop

Matteo Collina

Las tecnologías serverless nos ayudan a construir aplicaciones mejores y más escalables en la nube. Es un paradigma poderoso que nos permite centrarnos en crear valor empresarial y dejar que el proveedor de la nube se encargue de las tareas pesadas no diferenciadas, como gestionar la infraestructura subyacente. En esta sesión, Yan Cui nos guiará a través de muchas de las lecciones que ha aprendido al ejecutar cargas de trabajo serverless en producción durante los últimos cinco años, incluyendo consejos de desarrollo, estrategias de prueba y observabilidad, y mucho más. Puedes consultar las diapositivas de la charla de Yan <a href="https://drive.google.com/file/d/1cHZIF9E82VxEAd6s_YZ_d-UexuRWWsrX/view?usp=sharing">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Serverless en Producción, Lecciones desde las Trincheras

This Talk provides valuable insights for those considering serverless in 2022, with a focus on troubleshooting and observability using Lumigo. It emphasizes the use of multiple AWS accounts and Org Formation for better control and scalability. Security considerations include securely loading secrets at runtime and implementing zero-trust networking. Optimizing Lambda performance is discussed, along with updates on serverless frameworks and the role of Terraform. The Talk also compares Honeycomb and Lumigo for observability in serverless applications.

Serverless technologies help us build better and more scalable applications in the cloud. It's a powerful paradigm that allows us to focus on creating business values and letting the cloud provider handle the undifferentiated heavy-liftings such as managing the underlying infrastructure. In this session, Yan Cui would take us through many of the lessons that he has learnt from running serverless workloads in production over the last five years, including development tips, testing and observability strategies, and much more. You can check the slides for Yan's talk <a href="https://drive.google.com/file/d/1cHZIF9E82VxEAd6s_YZ_d-UexuRWWsrX/view?usp=sharing">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Serverless in Production, Lessons from the Trenches

Yan Cui

En esta breve charla relámpago registraré un dominio y demostraré cómo utilizar el cliente de la API de DNSimple para NodeJS para registrar un nombre de dominio y configurar el DNS necesario para que apunte a un servicio web en solo unos minutos. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cómo registrar un dominio utilizando Node y la API de DNSimple en 5 minutos

Today's Talk is a demo of the DnSimple node client, including the installation process, authentication, domain availability check, and registration. The speaker emphasizes testing in the sandbox environment before moving to production. Setting up DNS records and registering domains are also covered, with the importance of verifying the code's functionality. Additional information about other clients and the DNSimple API is available at dnsimple.com/API.

In this short lightning talk I’ll register a domain and demonstrate how to use the DNSimple NodeJS API client to register a domain name and set up the DNS needed to make it point to a web service in just a few minutes. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How to Register a Domain Using Node and the DNSimple API in 5 min

Anthony Eden

Node.js se ha convertido en un lenguaje cada vez más popular para construir y desplegar APIs backend. En un mundo de CMSs heredados que adoptan implementaciones desacopladas, han surgido muchos frameworks que se autodenominan CMS "headless", diseñados desde el principio para proporcionar una forma fácil de personalizar modelos de contenido, administrar permisos y autenticación, y servir rápidamente una API de contenido. Strapi, uno de los líderes en este espacio, ha lanzado recientemente su versión 4 del framework, y con Platform.sh se puede desplegar junto con varios frontends dentro del mismo proyecto, lo que brinda una experiencia de desarrollo drásticamente simplificada al trabajar con sitios desacoplados. En este masterclass, desplegaremos una aplicación de demostración de Strapi, que ha sido configurada para servir un sitio de reseñas de restaurantes. Paso a paso, agregarás servicios de base de datos, pruebas y frontends, todo dentro de entornos de desarrollo aislados. Al final, cada usuario tendrá un sitio desacoplado funcional y una mayor comprensión de cómo trabajar con sitios desacoplados en producción. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Desplegando un sitio de reseñas de restaurantes desacoplado en producción con Strapi y Platform.sh

The Workshop covers the use of PlatformSH and Strapi for building and deploying decoupled applications. It explores setting up projects, configuring databases, middleware, and plugins. The workshop also covers building and deploying the application, syncing data, and exploring the site. It highlights the benefits of PlatformSH, such as isolated development environments and easy deployment of multi-app architectures. The workshop concludes with a discussion on handling drafts and implementing live previews.

Node.js has become an increasingly popular language to build and deploy backend APIs. In a world of legacy CMSs adopting decoupled implementations, plenty of frameworks have sprung up to classify themselves as "headless" CMSs, designed from the start to provide an easy way to personalize content models, administer permissions and authentication, and serve a content API quickly. Strapi, one of the leaders in this space, has recently released their v4 version of the framework, and with Platform.sh it can be deployed alongside a number of frontends within the same project, giving a drastically simplified development experience working with decoupled sites. In this workshop, we'll deploy a Strapi demo application, which has been configured to serve a restaurant review site. Piece piece you will add database services, tests, and frontends, all within the safety of isolated development environments. At the end, each user will have a functioning decoupled site, and some greater understanding of working with decoupled sites in production. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Deploying a decoupled restaurant review site to production with Strapi and Platform.sh

Shedrack Akintayo

Chad Carlson

¿Listo para comenzar tu carrera como freelancer o recién estás comenzando en tu viaje como freelance? Estás en el lugar correcto. Aprende los trucos del oficio de los freelancers más experimentados de la industria. El movimiento de talento independiente es el futuro del trabajo. Si estás considerando dejar el empleo a tiempo completo para una carrera como freelancer, ahora es el momento de encontrar tu espacio exitoso en la fuerza laboral de talento independiente. Hoy en día, más personas trabajan como freelancers que nunca antes, y el mercado de freelancers contribuye con $1.2 billones a la economía de los Estados Unidos. Algunos de los roles más demandados para freelancers en este momento son desarrolladores senior con experiencia profesional en React, Python, Blockchain, QA y Node.js. Este masterclass te ayudará a diseñar una carrera como freelancer/contratista sostenible y rentable a tiempo completo (o parcial). Te proporcionaremos herramientas, consejos, mejores prácticas y te ayudaremos a evitar errores comunes. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cómo Diseñar una Carrera Sostenible como Freelancer/Contratista

Freelancing has become a popular career path, offering stability, flexibility, and economic opportunity. Major corporations are increasing their use of freelancers, and freelancers enjoy the ability to work on their passions and hobbies. Negotiating contracts and analyzing market rates are important for freelancers to get paid appropriately. Building a strong brand and online presence is crucial for freelancers to attract clients. Platforms like TopTel offer exclusive networks, support, and vetted clients for freelancers.

Ready to kickstart your freelance career or just getting started on your freelance journey? You’re in the right spot. Learn the tricks of the trade from the industry’s most experienced freelancers. The independent talent movement is the future of work. If you’re considering leaving full-time employment for a career as a freelancer, now is the time to find your successful space in the independent talent workforce. More people are working freelance today than ever before, with the freelance marketplace now contributing $1.2 trillion to the US economy. Some of the most in-demand roles for freelancers right now are senior developers with professional experience in React, Python, Blockchain, QA, and Node.js. This workshop will help you design a sustainable and profitable full-time (or part-time) freelancing/contracting career. We will give you tools, tips, best practices, and help you avoid common pitfalls. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How To Design A Sustainable Freelance/Contracting Career

Shane Ketterman

Alexander Weekes

Las pruebas de seguridad tradicionales para aplicaciones Node y JS se han centrado en el front-end, pero los problemas de seguridad reales suelen estar en la API REST de respaldo. Únete al cofundador de StackHawk, Scott Gerlach, para obtener una breve descripción de por qué debes replantear cómo pruebas tus aplicaciones JS y cómo StackHawk puede ayudarte a encontrar y solucionar rápidamente problemas de seguridad. Puedes consultar las diapositivas de la charla de Scott <a href="https://drive.google.com/file/d/1nRupxCNMRXs3aCi_ymS_EMahjCwjmx8n/view?usp=sharing">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Pruebas automatizadas de seguridad de aplicaciones con StackHawk

StackHawk is a dynamic application security testing tool that integrates with CI-CD workflows and simplifies finding and fixing security issues. The scan results include detailed descriptions of identified issues, along with links and request/response details for replaying the attack. The StackHawk YAML configuration allows for specifying application location, environment, and additional options for authentication and scanning exclusions.

Traditional security testing for Node and JS apps has focused on the front-end, but actual security issues most often lie in the backing REST API. Join StackHawk co-founder Scott Gerlach for a quick overview of why you need to rethink how you test your JS apps and how StackHawk can help you find and fix security bugs fast. You can check the slides for Scotts's talk <a href="https://drive.google.com/file/d/1nRupxCNMRXs3aCi_ymS_EMahjCwjmx8n/view?usp=sharing">here</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Automated Application Security Testing with StackHawk

Scott Gerlach

NodeJS es una representación del lado del servidor de Javascript que puede funcionar bien como backend de una aplicación y puede ejecutarse en varios servidores e infraestructuras. En esta charla, repasaremos el recorrido de cómo se ha implementado Nodejs a lo largo de los años a través de varias infraestructuras, desde PaaS hasta Contenedores. Puedes consultar las diapositivas de la charla de Shedrack <a href="https://drive.google.com/file/d/1olBLlCmJKzr-0sYw6olVJP6Nju4aDiQl/view?usp=sharing">aquí</a>. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

La Evolución de la Implementación de Node en Servidores y Plataformas

Today's talk covers the evolution of deploying Node on servers and platforms, including physical servers, monolith servers, PaaS, containers, and serverless. Node deployment has become easier over the years thanks to the evolution of Node.js. Each deployment method has its pros and cons, with serverless offering lower costs and simpler backend code. However, it also has drawbacks like vendor locking and unsuitability for long-term tasks. Overall, Node.js deployment has evolved from on-premise to containers to serverless.

NodeJS is a server-side representation of Javascript that can work well as an application's backend and can be run on various servers and infrastructures. In this talk, we'll be going through the journey of how Nodejs has been deployed over the years via various infrastructures from PaaS to Containers. You can check the slides for Shedrack's talk <a href="https://drive.google.com/file/d/1olBLlCmJKzr-0sYw6olVJP6Nju4aDiQl/view?usp=sharing">here</a>.  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Node Congress 2022

Master Fullstack: JS Backends, DevOps, Architecture