Name: Node Congress 2021
Start: 2021-02-16T23:00:00.000Z
End: 2021-02-18T23:00:00.000Z

TypeScript hace JavaScript más seguro agregando definiciones de tipo estático. Las definiciones estáticas son maravillosas; evitan que los desarrolladores cometan errores triviales asegurando que cada asignación e invocación se haga correctamente. Una variable tipificada como una cadena no puede ser asignada un número, y una función que espera tres argumentos no puede ser llamada con solo dos. Estas definiciones solo existen en el momento de la compilación; el código que finalmente se ejecuta es solo JavaScript. ¿Pero qué pasa con la respuesta de una solicitud de API? En esta charla, Ethan Arrowood, Ingeniero de Software 2 @ Microsoft, cubrirá varias soluciones para tipificar de manera segura los datos dinámicos en las aplicaciones TypeScript. Esta charla presenta tecnologías populares como Fastify, JSON Schema, Node.js, y más! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Manejo Seguro de Datos Dinámicos con TypeScript

This Talk discusses the safe handling of dynamic data with TypeScript using JSON Schema and TypeBox. Fastify, a web framework, allows developers to validate incoming data using JSON schema, providing type safety and error handling. TypeBox is a powerful library that allows developers to define JSON schemas and derive static types in TypeScript. The combination of JSON schema, TypeBox, and Fastify provides powerful tools for type safety and validation of dynamic data.

TypeScript makes JavaScript safer adding static type definitions. Static definitions are wonderful; they prevent developers from making trivial mistakes ensuring every assignment and invocation is done correctly. A variable typed as a string cannot be assigned a number, and a function expecting three arguments cannot be called with only two. These definitions only exist at build time though; the code that is eventually executed is just JavaScript. But what about the response from an API request? In this talk Ethan Arrowood, Software Engineer 2 @ Microsoft, he will cover various solutions for safely typing dynamic data in TypeScript applications. This talk features popular technologies such as Fastify, JSON Schema, Node.js, and more! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Safely Handling Dynamic Data with TypeScript

Ethan Arrowood

Hoy en día es posible escribir aplicaciones complejas con solo un puñado de desarrolladores en un corto período de tiempo, confiando en Frameworks y herramientas. Pero, ¿qué sucede cuando la aplicación se bloquea con errores de falta de memoria? ¿Cómo es posible garantizar tiempos de respuesta rápidos? Estos problemas aún se consideran difíciles de resolver.Sumergámonos en los entresijos de Node.js y aprendamos sobre los perfiles y el recolector de basura. Comprender cómo funciona el sistema en profundidad te permite escribir código más seguro, más rápido y con menos errores.Asegurémonos siempre de brindar la mejor experiencia para todos. Tanto para ti como para tus clientes. Encontremos esa fuga de memoria y solucionémosla.Aprendizajes<ul><li>Los participantes comprenden el manejo de memoria de Node.js y sus limitaciones.</li><li>Los participantes saben cuándo perfilar su aplicación para identificar fugas de memoria y código lento.</li><li>Los participantes son capaces de encontrar y solucionar la mayoría de las fugas de memoria.</li></ul><a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Desmitificando las fugas de memoria en JavaScript

The Talk discusses demystifying memory leaks in JavaScript, covering topics such as memory allocation, typical memory leaks and issues, handling file descriptors and event listeners, tools and techniques for identifying memory leaks, fixing memory leaks and restarting applications, and Ruben's personal experience with memory leaks.

Today it is possible to write complex applications with only a handful of developers in a short time frame relying upon Frameworks and tooling. But what happens when the application crashes with out of memory errors? How is it possible to guarantee fast response times? These problems are still considered difficult to solve.Let's dive into the Node.js internals and learn about profilers and the garbage collector. Understanding how the system works in depth let's you write code that is safer, faster and less error prone.Let's make sure you always provide the best experience for everyone. Yourself and your customer. Let us find that memory leak and fix it.Learnings<ul><li>        Participants understand the Node.js memory handling and their shortcomings.</li><li>        Participants know when to profile their application to identify memory leaks and slow code.</li><li>        Participants are able to find and address most memory leaks.</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Demystifying Memory Leaks in JavaScript

Ruben Bridgewater

¿Cómo escalas una aplicación web para ser desarrollada por miles de ingenieros y actualizarla para utilizar las últimas tecnologías de JavaScript (Node.js + React)? ¡La respuesta es utilizando Micro Frontends!American Express es pionero en el uso de esta arquitectura, utilizándola en producción desde 2016 y transformando la cara de un sitio web utilizado por millones de usuarios en todo el mundo.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

La Revolución de los Micro Frontends en Amex

This Talk discusses the micro front-end revolution at American Express, highlighting the challenges of independent delivery and the solution of micro frontends. The architecture involves a Node.js server for server-side rendering and module composition, with Holocron modules deployed to a CDN. The development workflow includes local development environments and CI pipelines. Microfrontends are a pattern, not a set of tools, and should be implemented based on the specific use case. The adoption challenges include reworking the architecture and implementing features like Webpack and Module Federation. Communication between modules should be kept independent, and migration to micro frontends is simplified with existing microservices and Kubernetes. Server-side rendering is optional, and bundle size is limited to 250K.

How do you scale a web application to be developed thousands of engineers and upgrade it to use the latest Javascript technologies (Nodejs + React)? The answer is, using Micro-Frontends!American Express is a pioneer in the usage of this architecture using it in production since 2016 and transforming the face of a website used millions of users worldwide. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

The Micro-Frontend Revolution at Amex

Ruben Casas

El registro, las métricas y el rastreo distribuido son tres herramientas vitales para observar los servicios de Node.js. En esta charla consideraremos los diferentes escenarios en los que cada herramienta prospera, analizaremos paneles y visualizaciones, e incluso examinaremos el código necesario para instrumentar estas herramientas en un servicio de Node.js.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Registro, Métricas y Rastreo con Nodejs

This talk covers logging, metrics, and tracing with Node.js. It explores logging configuration with Winston and logging conventions and solutions. The talk also discusses logging dashboards and metrics, as well as metrics and distributed tracing. It touches on tracing tools and visualizations, async-await and logging in Node.js, and request-specific logging and distributed tracing. Additionally, it covers logging middleware and serverless functions, and the difference between automatic and manual instrumentation.

Logging, Metrics, and Distributed Tracing are three vital tools for observing Node.js services. In this talk we’ll consider the different scenarios in which each tool thrives, look at dashboards and visualizations, and even examine the code required to instrument these tools in a Node.js service. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Logging, Metrics, and Tracing with Nodejs

Thomas Hunter II

El cliente HTTP de Node.js es una parte fundamental de cualquier aplicación, sin embargo, muchos piensan que no se puede mejorar. Tomé esto como un desafío y ahora estoy listo para presentar un nuevo cliente HTTP para Node.js, undici, que duplica el rendimiento de tu aplicación. La historia detrás de esta mejora comienza con el nacimiento de TCP/IP y está arraigada en una de las limitaciones fundamentales de las redes: el bloqueo de cabeza de línea (HOL blocking). El bloqueo de cabeza de línea es uno de esos temas que los desarrolladores ignoran felizmente y, sin embargo, afecta profundamente la experiencia de tiempo de ejecución de las aplicaciones distribuidas que construyen todos los días. Undici es un cliente HTTP/1.1 que evita el bloqueo de cabeza de línea utilizando keep-alive y pipelining, lo que resulta en una duplicación del rendimiento de tu aplicación.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

¿Podemos duplicar el rendimiento del cliente HTTP?

Today's Talk discusses HTTP clients, servers, microservices, and maximizing performance in Node.js. It covers topics such as TCP, latency, HTTP Keep-Alive, pipelining, the Node.js event loop, timeouts, and introduces the Undici library. The speaker emphasizes the importance of reusing connections, minimizing blocking, and using benchmarks to measure performance impact. Undici is highlighted as a new client for Node.js that eliminates the need for multiple agents and offers easy configuration options.

The Node.js HTTP client is a fundamental part of any application, yet many think it cannot be improved. I took this as a challenge and I’m now ready to present a new HTTP client for Node.js, undici, that doubles the throughput of your application The story behind this improvement begins with the birth of TCP/IP and it is rooted in one of the fundamental limitations of networking: head-of-line blocking (HOL blocking). HOL blocking is one of those topics that developers blissfully ignore and yet it deeply impacts the runtime experience of the distributed applications that they build every day. Undici is a HTTP/1.1 client that avoids HOL blocking using keep-alive and pipelining, resulting in a doubling of your application throughput. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Can We Double HTTP Client Throughput?

Matteo Collina

Este masterclass te enseña los conceptos básicos del desarrollo de aplicaciones serverless con TypeScript. Comenzaremos con una función Lambda simple, configuraremos el proyecto y la infraestructura como código (AWS CDK) y aprenderemos cómo organizar, probar y depurar una aplicación serverless más compleja. Tabla de contenidos:<ul><li>        - Cómo configurar un proyecto serverless con TypeScript y CDK</li><li>        - Cómo escribir una función Lambda testeable con arquitectura hexagonal</li><li>        - Cómo conectar una función a una tabla DynamoDB</li><li>        - Cómo crear una API serverless</li><li>        - Cómo depurar y probar una función serverless</li><li>        - Cómo organizar y hacer crecer una aplicación serverless Materiales mencionados en el masterclass: <a href="https://excalidraw.com/#room=57b84e0df9bdb7ea5675,HYgVepLIpfxrK4EQNclQ9w" target="_blank">https://excalidraw.com/#room=57b84e0df9bdb7ea5675,HYgVepLIpfxrK4EQNclQ9w </a>Blog de DynamoDB de Alex DeBrie: https://www.dynamodbguide.com/ Excelente libro para DynamoDB: <a href="https://www.dynamodbbook.com/" target="_blank">https://www.dynamodbbook.com/ https://slobodan.me/workshops/nodecongress/prerequisites.html </a></li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Construyendo Aplicaciones Serverless en AWS con TypeScript

This workshop focuses on learning serverless with TypeScript and building a serverless app for a coffee shop. It covers various topics such as serverless services and pricing, serverless workflow with AWS, setting up IAM and credentials, CDK project setup, organizing functions, and creating DynamoDB tables. The workshop also explores the benefits of a single-table layout in DynamoDB, creating APIs with AWS Lambda and API Gateway, and troubleshooting deployment issues. Additionally, it discusses environment variables, testing and debugging, and handling environments and rollbacks.

This workshop teaches you the basics of serverless application development with TypeScript. We'll start with a simple Lambda function, set up the project and the infrastructure-as-a-code (AWS CDK), and learn how to organize, test, and debug a more complex serverless application. Table of contents:<ul><li>        - How to set up a serverless project with TypeScript and CDK</li><li>        - How to write a testable Lambda function with hexagonal architecture</li><li>        - How to connect a function to a DynamoDB table</li><li>        - How to create a serverless API</li><li>        - How to debug and test a serverless function</li><li>        - How to organize and grow a serverless application Materials referred to in the workshop: <a href="https://excalidraw.com/#room=57b84e0df9bdb7ea5675,HYgVepLIpfxrK4EQNclQ9w" target="_blank">https://excalidraw.com/#room=57b84e0df9bdb7ea5675,HYgVepLIpfxrK4EQNclQ9w </a>DynamoDB blog Alex DeBrie: https://www.dynamodbguide.com/ Excellent book for the DynamoDB: <a href="https://www.dynamodbbook.com/" target="_blank">https://www.dynamodbbook.com/ https://slobodan.me/workshops/nodecongress/prerequisites.html </a></li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Building Serverless Applications on AWS with TypeScript

Slobodan Stojanović

Node.js es famosamente un tiempo de ejecución de JavaScript que fomenta el uso de operaciones asíncronas siempre que sea posible, pero ¿qué sucede cuando realmente, realmente necesitas hacer E/S síncrona? Anna ofrece una visión general de las muchas y sorprendentes formas de lograr esto, y lo que podemos aprender sobre cómo funciona el lenguaje y las internas de Node.js a partir de ellas.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

No lo intentes en casa: E/S síncrona en Node.js

This Talk explores synchronous IO in Node.js and the advantages of asynchronous IO. It discusses exceptions to synchronous IO and approaches to achieving synchronous IO in Node.js, including using WASI and native add-ons. The Talk also covers mixing workers with atomics for synchronous IO and embedding Node.js to create a synchronous worker. Additionally, it touches on TypeScript migration, optimizations in Node.js, and experiences and advice on contributing to Node.js.

Node.js is famously a JavaScript runtime that encourages using asynchronous operations wherever possible – but what happens when you really, really need to do synchronous I/O? Anna gives an overview over the – surprisingly many – different ways to achieve this, and what we can learn about how the language and Node.js internals work from them. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Don’t Try This at Home: Synchronous I/O in Node.js

Anna Henningsen

Node.js ejecuta grandes sistemas hoy en día. A veces, puedes mejorar la experiencia del usuario y ahorrar en gastos en la nube optimizando tus scripts de Node.js. En esta charla compartiré consejos de producción sobre cómo mejorar el rendimiento en tiempo de ejecución de Node.js. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Consejos de rendimiento de Node.js en tiempo de ejecución

This Talk focuses on the importance of runtime optimization in software development. It discusses the impact of unoptimized functions and the role of garbage collection. The Talk also highlights the use of profiling tools to identify and improve performance issues. Additionally, it emphasizes the importance of memory profiling to prevent memory leaks and optimize application performance.

Nodejs runs big systems today. Sometimes, you can improve user experience and save on cloud expanses optimizing your nodejs scripts. In this talk I will share tips from production on how to improve nodejs runtime performance. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Nodejs Runtime Performance Tips

Yonatan Kra

Fastify es un marco de trabajo HTTP para Node.js que se enfoca en brindar 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 plugins de Fastify, que permite a los desarrolladores escribir más de cien plugins.Este masterclass práctico está estructurado en una serie de ejercicios que cubren 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://github.com/nearform/the-fastify-workshop" target="_blank">https://github.com/nearform/the-fastify-workshop</a> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Aprende Fastify Un Plugin a la Vez

This Fastify Workshop covers the basics of the framework and its key plugins, highlighting its speed, extensibility, and schema-based approach. It emphasizes the importance of using Node.js LTS version 14 and ESM modules. The workshop includes exercises on folder organization, route creation, dynamic imports, logging with Pino, schema validation, unit testing, JWT authentication, environment variable configuration, and integration with Fastify Autoload. The speaker also discusses Fastify use cases, compares it to Golang, and recommends Fastify for better developer productivity. The workshop concludes with insights on data access, upcoming Fastify features, and contributions to the project.

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://github.com/nearform/the-fastify-workshop" target="_blank">https://github.com/nearform/the-fastify-workshop</a> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Learn Fastify One Plugin at a Time

Escribe e implementa modelos de aprendizaje automático fácilmente en Node.js utilizando Tensorflow.js. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Aprendizaje automático en Node.js utilizando Tensorflow.js

The Talk introduces TensorFlow.js in Node.js for machine learning, highlighting its open-source nature and easy integration with JavaScript. It emphasizes the benefits of using Node.js, such as the ability to write machine learning models directly in JavaScript, access to the NPM ecosystem, and improved performance. The different packages available for utilizing TensorFlow.js in Node.js, including CPU, GPU, and vanilla packages, are discussed. The importance of setting up Node.js bindings to avoid blocking the main thread is mentioned, along with the availability of APIs like dfNode and TensorBoard.

Write and deploy machine learning models easily in Nodejs using Tensorflow.js. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Machine Learning in Node.js using Tensorflow.js

Shivay Lamba

¿Cómo sabes si tu función está funcionando perfectamente en producción? Si algo se rompe en producción, ¿cómo lo sabrás? ¿Esperarás a que un usuario te lo informe? ¿Qué haces cuando los resultados de tus pruebas de preparación no reflejan el comportamiento actual de producción? ¡Para probar de manera proactiva en lugar de reactiva, prueba en producción! Tendrás una mayor precisión en los resultados de las pruebas, tus pruebas se ejecutarán más rápido debido a la eliminación de datos incorrectos y tendrás más confianza antes de los lanzamientos. Esto se puede lograr a través de la implementación de flags de características, lanzamientos canarios, configuración de un pipeline de CI/CD adecuado y limpieza de datos. Saldrás de esta charla con estrategias para mitigar riesgos, mejorar tu comprensión de los pasos necesarios y cambiar la cultura de pruebas de tu empresa, para poder brindar la mejor experiencia posible a tus usuarios. Al final del día, no nos importa si tus funciones funcionan en preparación, nos importa si funcionan en producción. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Usando Feature Flags para Habilitar Pruebas en Producción

Today's Talk discusses enabling tests in production, including challenges with staging environments, the use of feature flags for testing, and automating feature flag testing. It also covers running tests in production while ensuring no impact on real users, determining what to test in production, recommended tools and dependencies, and mitigating risks. The importance of testing in production and shifting the testing culture is emphasized, along with the need for a solid automation framework and managing feature flag dependencies.

How do you know your feature is working perfectly in production? If something breaks in production, how will you know? Will you wait for a user to report it to you? What do you do when your staging test results do not reflect current production behavior? In order to test proactively as opposed to reactively, try testing in production! You will have an increased accuracy of test results, your tests will run faster due to the elimination of bad data, and you will have higher confidence before releases. This can be accomplished through feature flagging, canary releases, setting up a proper CI/CD pipeline, and data cleanup. You will leave this talk with strategies to mitigate risk, to better your understanding of the steps to get there, and to shift your company’s testing culture, so you can provide the best possible experience to your users. At the end of the day, we don't care if your features work in staging, we care if they work in production. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Using Feature Flags to Enable Testing in Production

Talia Nassi

Pruebas en Producción

Today's Talk discusses the concept of testing in production, including challenges with staging environments and data mismatch. The use of feature flags is highlighted as a solution to enable testing in production. Automation is emphasized as a key component for efficient feature flag testing. The benefits of testing in production are increased developer velocity and confidence. Organizational requirements and resistance to testing in production are also addressed. The Talk concludes by discussing feature flag management and user segmentation in feature flag services.

Testing in Production

Node.js core no tiene una hoja de ruta oficial: es la suma de los intereses y esfuerzos de los colaboradores lo que determina la dirección futura del proyecto. La evolución de una nueva característica en Node.js puede tomar diferentes giros y vueltas. Algunas características nuevas se implementan como experimentales, para dar tiempo a recopilar comentarios de los usuarios antes de considerarlas estables. Otras características se implementarán como estables desde el principio. Entonces, ¿qué hay en el horizonte? Esta charla echará un vistazo a algunas de las características nuevas y experimentales en el núcleo de Node.js. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Node.js: lo Nuevo y lo Experimental

Beth Brix, a senior software engineer at Red Hat, discusses new and experimental features in Node.js, the release process, API stability, and the importance of user feedback. Some stable features in Node.js 15 include the abort controller, MPM7, and V886. Node 14 is the most popular version among users. The future releases of Node.js will likely include a major v8 update with new JavaScript language features. The Node community is supportive and willing to help users with migration and finding solutions.

Node.js core does not have an official roadmap - it’s the sum of the interests and efforts of the contributors that determines the future direction of the project. The evolution of a new feature in Node.js can take different twists and turns. Some new features land as experimental, to give time to gather user feedback before they’re considered stable. Other features will land as stable from the start. So, what’s in the pipeline? This talk will take a look at some of the new and experimental features in Node.js core. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Node.js: the New and the Experimental

Bethany Griggs

Todos hemos escuchado el revuelo sobre llevar la seguridad de las aplicaciones a manos de los desarrolladores, pero si eres como la mayoría de las empresas, ha sido difícil hacer esto realidad. No estás solo: establecer la cultura, los procesos y las herramientas necesarias para lograrlo es difícil, especialmente para aplicaciones sofisticadas. Únete a Scott Gerlach (CSO, StackHawk) y Liran Tal (Defensor del Desarrollador, Snyk) mientras profundizan en cómo puedes agregar pruebas de seguridad de aplicaciones a tu canal de CI/CD para enviar código seguro más rápido. Prerrequisitos:Docker es recomendado <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Asegurando Aplicaciones Node con Pruebas de Seguridad Automatizadas en CI/CD

This workshop on automated application security testing for Express apps covers the importance of early bug detection, the challenges of testing in production, and the benefits of using developer-friendly security tools. It explores different types of application security testing, including static testing and dynamic application security testing, and emphasizes the need to address vulnerabilities in both areas. The workshop also highlights the shift to cloud-native development, the responsibility of developers in managing infrastructure, and the importance of integrating security throughout the development process. The demo showcases the use of StackHawk and Snyk tools to find and fix security vulnerabilities in an app, demonstrating the effectiveness of dynamic application security testing and software composition analysis tools.

We’ve all heard the buzz around pushing application security into the hands of developers, but if you’re like most companies, it has been hard to actually make this a reality. You aren’t alone - putting the culture, processes, and tooling in place to make this happen is tough - especially for sophisticated applications. Join Scott Gerlach (CSO, StackHawk) and Liran Tal (Developer Advocate, Snyk) as they dive into how you can add AppSec testing to your CI/CD pipeline to ship secure code faster. Prerequisites:Docker is a nice to have <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Securing Node Applications with Automated Security Testing in CI/CD

Scott Gerlach

Liran Tal

Imagina tu productividad y confianza al desarrollar aplicaciones web sin las herramientas de Chrome DevTools. Muchos hacen exactamente eso con Node.js.Es importante observar y aprender lo que está sucediendo en tu aplicación para mantenerse competitivo y crear las aplicaciones Node.js más eficientes y de mejor rendimiento, siguiendo las mejores prácticas.En esta charla, exploraremos herramientas útiles para examinar tus aplicaciones Node.js y cómo la observabilidad acelerará el desarrollo, producirá un código mejor y mejorará la confiabilidad y el tiempo de actividad. ¡No te lo pierdas!<a href="https://www.froala.com/wysiwyg-editor?pb=1"></a>

Examinando la Observabilidad en Node.js

Today's Talk explores the concept of observability in Node.js, emphasizing the importance of understanding what's happening inside a system without needing to ship new code. The Talk covers various observability tools and techniques, including performance measurement and tracing, HeapSnapshot and Chrome DevTools, the BA Inspector, and external tools like nSolid. nSolid is highlighted as an enhanced observability tool specifically built for Node.js, offering low-input performance insights and greater security for mission-critical applications.

Imagine your productivity and confidence developing web apps without chrome dev tools. Many do exactly that with Node.js.It is important to observe and learn what’s happening in your app to stay competitive and create the most performant and efficient Node.js applications, following the best practices.In this talk, we will explore useful tools to examine your Node.js applications and how observability will speed up development, produce better code while improving reliability and uptime. Don’t miss it! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Examining Observability in Node.js

Lizz Parody

Esta charla explora el poder de la infraestructura tecnológica como código, permitiendo a las organizaciones construir, escalar y desmantelar infraestructuras del mundo real de manera rápida, confiable y reproducible, con un enfoque en pilas de NodeJS. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Infraestructura como Código con enfoque en Node

Today's Talk discussed infrastructure as code using serverless Node.js with a focus on AWS Lambda and Terraform. The speaker emphasized the benefits of infrastructure as code, such as collaboration, versioning, and reproducibility. The Talk provided a step-by-step demonstration of deploying a Node.js app to AWS Lambda using Terraform. Key takeaways include the advantages of mechanized and automated processes, ephemeral state, repeatable processes, and transparency. The speaker also mentioned the importance of having DevOps experts on the team and highlighted the cost-effectiveness of serverless functions.

This talk explores the power of tech infrastructure as code, allowing organizations to quickly, reliably and reproducibly build up, scale, and tear down real-world infrastructure as needed — with a focus on NodeJS stacks. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Infrastructure as Code with a Node Focus

Tejas Kumar

Cuando se solucionan problemas en aplicaciones complejas de Node.js, siempre es útil recopilar información sobre la red, el sistema de archivos o las dependencias externas. Incluso al trabajar con una nueva base de código, es importante tener información sobre cómo se construye la aplicación, qué llamadas asíncronas se están utilizando y con qué frecuencia. En esta charla, quiero presentar "instrument", una herramienta que he creado para esto y que también es de código abierto.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Instrumentando Internals de Node.js

The Talk is about troubleshooting Node.js applications and using a tool for improved visibility and information. The tool can collect information about URLs and module imports in a server. However, it is not recommended for use in non-local environments due to performance overhead and potential bugs.

When troubleshooting complex Node.js applications recollecting information about the network, filesystem or external dependencies is always useful. Even when working with a new codebase insights on how the application is built, which asynchronous calls are being used or how often. In this talk I want to introduce "instrument", a tool I've created for this which is also Open Source. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Instrumenting Node.js Internals

Alejandro Oviedo

Pruebas de seguridad para aplicaciones respaldadas por GraphQL

StackHawk is an automated application and API security testing tool that integrates with CI/CD. It uses the ZAP scanner and supports various types of applications and APIs. StackHawk provides detailed vulnerability information and triage features to manage low-risk issues. The tool aims to seamlessly integrate into engineering workflows and make security accessible for teams.

Security Testing for GraphQL Backed Applications

Ryan Severns

Los beneficios de Node.js para desarrollar aplicaciones en tiempo real a gran escala son muy conocidos. A medida que las arquitecturas de Node.js se vuelven más complejas, la visualización de su arquitectura basada en microservicios es crucial. Sin embargo, la visualización de los microservicios es increíblemente compleja debido a la escala y las transacciones entre ellos. En este masterclass, aprenderás cómo aprovechar los mapas de servicios para comprender instantáneamente tu arquitectura y solucionar cualquier error de API. Escribiremos una aplicación Express simple y exploraremos las mejores prácticas al usar Express. Luego, desplegaremos la aplicación en AWS, integraremos el entorno con Epsagon y profundizaremos en varias características de la plataforma para permitir la detección inmediata y la solución rápida de errores de la aplicación. Objetivos: Visualizar tu arquitectura, monitorear tus aplicaciones, reducir tu tiempo medio de detección y recuperación (MTTD y MTTR). ¿Quién debería asistir? DevOps, Ingenieros, Arquitectos de Cloud, IT, Desarrolladores de Software, Arquitectos y Ingenieros de Soluciones, SREs y cualquier persona que ejecute aplicaciones basadas en microservicios (Kubernetes, contenedores, funciones sin servidor, y más) en la nube. Prerrequisitos<ul><li>Preferimos usar VSCode para una mejor experiencia (otros IDE también son válidos)</li><li>Instalar previamente npm y node</li><li>        Cuenta de AWS preexistente: puedes crear una cuenta gratuita <a href="https://aws.amazon.com/ru/free/?all-free-tier.sort-=item.additionalFields.SortRank&amp;all-free-tier.sort-order=asc">aquí</a></li><li>        Los asistentes pueden crear una cuenta de Epsagon con anticipación <a href="https://app.epsagon.com/login">aquí</a>, no es obligatorio</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cómo solucionar errores de API y reducir MTTD/R

Today's workshop focused on observability in modern Node.js applications and the challenges in distributed systems. The workshop covered building an Express application, making API requests, deploying to AWS Lambda, and integrating with Epsilon for tracing and troubleshooting. Epsilon provides a comprehensive solution for monitoring and troubleshooting, including visualizing trace data, indexing requests, and creating alerts. The workshop also included a treasure hunt contest to find a hidden password within the APIs. Overall, the workshop emphasized the importance of observability and provided practical tools and techniques for implementing it in real-world applications.

The benefits of Node.js to develop real-time applications at scale are very well known. As Node.js architectures get more and more complex, visualization of your microservices-based architecture is crucial. However, the visualization of microservices is incredibly complex given the scale and the transactions across them. In this workshop, you will learn how to leverage service maps to instantly understand your architecture and troubleshoot any API error. We will write a simple Express application and explore best practices when using Express. Then, we’ll deploy the application on AWS, integrate the environment with Epsagon, and deep-dive into various features of the platform to enable immediate detection and fast troubleshooting of application errors. Goals: Visualizing your architecture, monitoring your applications, reducing your mean time to detection and recovery (MTTD and MTTR). Who should attend? DevOps, Engineers, Cloud Architects, IT, Software Developers, Solution Architects and Engineers, SREs, and anyone who is running microservice-based applications (Kubernetes, containers, serverless functions, and more) in the cloud. Prerequisites<ul><li>We prefer to use VSCode for a better experience (other IDEs are fine)</li><li>Preinstall npm and node</li><li>        Pre-existing AWS Account - You can create a free tier <a href="https://aws.amazon.com/ru/free/?all-free-tier.sort-=item.additionalFields.SortRank&amp;all-free-tier.sort-order=asc">here</a></li><li>        Attendees are free to create an Epsagon account in advance <a href="https://app.epsagon.com/login">here</a>, not mandatory</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How to Troubleshoot API Errors and Reduce MTTD/R 

Gal Bashan

En esta charla, Zoe Steinkamp hablará sobre Giraffe, una biblioteca de visualización de código abierto que impulsa las visualizaciones de datos en la interfaz de usuario de InfluxDB 2.0. Giraffe se puede utilizar para mostrar sus datos dentro de su propia aplicación y es compatible con Fluxlang. Utiliza algoritmos para manejar la visualización de grandes volúmenes de datos de series temporales que InfluxDB puede ingestar y consultar.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cómo creamos las bibliotecas Giraffe para datos de series temporales

I will be presenting Influx Data's open source time series graphing library GIRAFFE, which powers the visualizations of the InfluxDB dashboard and the Data Explorer. GIRAFFE is a JavaScript library based on React for charting and mapping, supporting various graph types and data sources. It offers a sandbox with examples of different graphs and provides links to GitHub, quick start guides, demos, and code samples.

In this talk, Zoe Steinkamp will talk about Giraffe, an open source visualization library that powers data visualizations in the InfluxDB 2.0 UI. Giraffe can be used to display your data within your own app and is Fluxlang-supported! It uses algorithms to handle visualizing high volumes of time series data that InfluxDB can ingest and query. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How We Created the Giraffe Libraries for Time Series Data

Zoe Steinkamp

De 1 a 101 Funciones Lambda en Producción: Evolucionando una Arquitectura Serverless

Vacation Tracker is a serverless startup using Node.js that started with a simple lambda function and now has many lambda functions. They built a system connected to Slack and calendars, which is now used by many startups, companies, and organizations. They evolved to an event-driven architecture using CQRS and AWS AppSync with Managed GraphQL. Onboarding new developers is a challenge, but serverless allows them to assign a new environment and AWS account to each developer. Testing and monitoring are crucial, and they have successfully migrated from MongoDB to DynamoDB.

From 1 to 101 Lambda Functions in Production: Evolving a Serverless Architecture

En esta charla, nos divertiremos intentando manipular un proceso de Node.js en ejecución para cambiar su comportamiento en tiempo de ejecución. Sin cambiar el código ni reiniciar el proceso, encontraremos una forma de inyectar nuestra propia lógica en él y comenzar a hacer las cosas que queremos. ¿Cuáles son las limitaciones de este enfoque? ¿Hay alguna parte de él que se pueda utilizar en escenarios de la vida real? ¡Ven y descúbrelo! Sí, habrá una demostración en vivo.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

¿Puedes Cambiar el Comportamiento de un Proceso de Node.js en Ejecución desde el Exterior?

This talk explores how to remotely change the behavior of a Node.js process at runtime and inject a logger using the Chrome DevTool protocol. It demonstrates the power of dev tools and encourages their usage. Remote debugging is useful for debugging memory leaks in production. The method requires local machine access and has security implications, but it requires significant access and indicates a major breach. The talk emphasizes the importance of having awareness and monitoring in place for application protection.

In this talk, we will have fun trying to tamper with a running Node.js process to change its behavior at runtime. Without changing the code or restarting the process, we will find a way to inject our own logic into it and start to do the things we want. What are the limitations of such an approach? Is there part of it that can be used in real life scenarios? Come and find out! Yes, there will be some live demo. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Can You Change the Behavior of a Running Node.js Process From the Outside?

Vladimir de Turckheim

Considera cuántas notificaciones recibes al día... y ahora considera los millones de personas que también reciben notificaciones. 16 millones de notificaciones al día que tienen lugares a los que ir y personas que ver, en una carrera contra el tiempo, la carga y la latencia.Entonces, ¿qué sucede detrás de escena para asegurarse de que todas esas notificaciones lleguen a donde deben ir y rápidamente? Una combinación de autoescalado, rabbitMQ, monitoreo minucioso y un equipo de desarrollo incansable. En esta charla, discutiré la funcionalidad del bus de mensajes en el núcleo de la plataforma de comunicaciones de Vonage, los poderosos scripts de Node que impulsan toda la operación y cómo puedes utilizar soluciones similares para diversos desafíos. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Notificaciones Push: No se puede vivir con ellas, no se puede vivir sin ellas

The Talk explores the journey of a notification in a communications platform, highlighting the challenges of infrastructure engineering. Trace IDs and local storage play a crucial role in ensuring the arrival of notifications, allowing for easy debugging if they don't reach the device. The logs demonstrate the journey of a notification, reaching the app store in just 4 milliseconds.

Consider how many notifications you get per day... and now consider the millions of other people who are also receiving notifications. 16 million notifications a day that have places to be and people to see, in a race against time, load, and latency.So what happens behind the scenes to ensure that all those notifications get where they need to go, and quickly? A combination of auto-scaling, rabbitMQ, scrupulous monitoring, and a tireless dev team. In this talk I’ll discuss the functionality of the message bus at the core of Vonage’s communications platform, the powerful Node scripts that power the entire operation, and how you can use similar solutions for a number of different challenges. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Push Notifications: Can’t Live With Em, Can’t Live Without Em

Avital Tzubeli

¿Tienes una forma de verificar rápidamente todos tus repositorios en busca de vulnerabilidades a varios ataques? ¿Sabes a qué ataques deberías preparar tus aplicaciones? En esta charla, cubriremos los 10 ataques principales a las aplicaciones de Node y cómo manejarlos. Se cubrirán varias herramientas, todas las cuales se han utilizado en producción en diferentes arquitecturas de backend.Algunas de las áreas que se cubrirán incluyen la seguridad de las dependencias, la seguridad de los datos y la seguridad de tu servidor. Al final de esta charla, los asistentes deberían tener una caja de herramientas de seguridad completa y sabrán cómo implementarla rápidamente. Esto ayudará con las aplicaciones de producción porque podrás cumplir con tus sprints a tiempo y podrás descansar sabiendo que tienes medidas de seguridad en su lugar.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

La Caja de Herramientas de Seguridad para Node

The Talk focuses on Node application security, covering topics such as OWASP top 10 vulnerabilities, handling packages, managing data, and protecting servers. Best practices include password security, input validation, and data encryption. The importance of securing access to packages and managing data is emphasized. Encrypting data for secure communication is discussed, along with protecting servers using HTTPS and rate limiting. The challenges of security implementation and resources for learning are mentioned, as well as the use of attacker tools. Docker security and preventing IP attacks are also touched upon.

Do you have a way to quickly check all of your repos for any vulnerabilities to various attacks? Do you know which attacks you should be preparing your applications for? In this talk, we will cover the top 10 attacks on Node applications and how to handle all of them. Multiple tools will be covered, all of which have been used in production across different back-end architectures.A few of the areas that will be covered include securing dependencies, securing data, and securing your server. By the end of this talk, attendees should have a full security toolbox and they will know how to implement it quickly. This will help with production applications because you will still get through your sprints on time and you will be able to rest knowing you have security measures in place. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

The Security Toolbox For Node

Milecia McGregor

Durante años, AWS ha ofrecido CloudFormation como un enfoque para la Infraestructura como Código (IaC). CloudFormation permite la provisión de pilas de aplicaciones a partir de plantillas en formato JSON o YAML. Desafortunadamente, debido a su tamaño y complejidad, las plantillas de CloudFormation han ganado una reputación de ser difíciles de manejar. El AWS Cloud Development Kit (CDK) mitiga parte de la complejidad asociada con CloudFormation, permitiendo a los desarrolladores definir programáticamente su arquitectura en la nube utilizando lenguajes de alto nivel familiares como JavaScript y TypeScript. Los proyectos de CDK luego pueden ser implementados a través de CloudFormation, manteniendo todos los beneficios de CloudFormation, como implementaciones repetibles y detección de desviaciones. Esta charla presentará el CDK en el contexto de Node.js y demostrará cómo se puede aprovechar para la provisión de arquitecturas nativas en la nube. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Introducción al AWS CDK: Infraestructura como Código

The AWS CDK is an infrastructure as code tool that supports multiple programming languages and helps mitigate concerns about vendor lock-in. It uses JSII to support different languages and allows you to write code once and get the same API across different languages. The CDK simplifies resource creation and management in AWS, addressing the verbosity and error-proneness of CloudFormation. CDK applications consist of apps and stacks, with stacks mapping to CloudFormation stacks. The CDK provides a more compact and familiar syntax compared to CloudFormation, making it easier for JavaScript developers to handle the entire stack.

For years AWS has offered CloudFormation as an approach to Infrastructure as Code (IaC). CloudFormation allows application stacks to be provisioned from JSON or YAML formatted templates. Unfortunately, due to their size and complexity, CloudFormation templates have earned a reputation as being unwieldy to work with. The AWS Cloud Development Kid (CDK) mitigates some of the complexity associated with CloudFormation allowing developers to programmatically define their cloud architecture using familiar high-level languages such as JavaScript and TypeScript. CDK projects can then be deployed via CloudFormation, while retaining all of the benefits of CloudFormation, such as repeatable deployments and drift detection. This talk will introduce the CDK in the context of Node.js and demonstrate how it can be leveraged to provision cloud native architectures. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Introduction to the AWS CDK: Infrastructure as Node

Colin Ihrig

InfluxDB es una base de datos de series temporales de código abierto que permite a los desarrolladores construir software de IoT, análisis y monitoreo. Está diseñado específicamente para manejar los volúmenes masivos y las innumerables fuentes de datos con marca de tiempo producidos por sensores, aplicaciones e infraestructura. En esta masterclass se presenta una aplicación de muestra completamente funcional llamada IoT Center que se basa en InfluxDB. Esta aplicación demuestra las capacidades de la plataforma InfluxDB para desarrollar una aplicación basada en series de tiempo habilitada para JavaScript. Recopila, almacena y muestra un conjunto de valores que incluyen temperatura, humedad, presión, concentración de CO2, calidad del aire, así como proporciona coordenadas GPS de un conjunto de dispositivos IoT. Con estos datos almacenados en InfluxDB, la aplicación puede consultar estos datos para mostrarlos y también escribir datos en la base de datos. En esta masterclass práctica, los estudiantes aprenderán cómo instalar este código de código abierto para aprender a consultar y escribir en InfluxDB utilizando el cliente JavaScript de InfluxDB, y familiarizarse con el lenguaje de consulta Flux que está diseñado para consultar, analizar y actuar sobre datos de series de tiempo. Y finalmente, recopilar y visualizar datos de rendimiento de la aplicación Node.js. Requisitos previos <ul><li>Cuenta gratuita registrada en InfluxDB Cloud en <a href="https://cloud2.influxdata.com/">https://cloud2.influxdata.com</a></li><li>Tres opciones disponibles (a través de cuenta de Google, a través de cuenta de Microsoft o a través de correo electrónico)</li><li>Probar inicio de sesión después del registro y guardar las credenciales para la masterclass</li><li>Instalación de la herramienta git (por ejemplo, desde <a href="https://git-scm.com/downloads">https://git-scm.com/downloads</a>)</li><li>Clonar IoT Center</li><li>Ejecutar: git clone <a href="https://github.com/bonitoo-io/iot-center-v2">https://github.com/bonitoo-io/iot-center-v2</a></li><li>Instalar nodejs (desde <a href="https://nodejs.org/en/download">https://nodejs.org/en/download</a>)</li><li>Instalar el gestor de paquetes yarn (desde <a href="https://classic.yarnpkg.com/en/docs/install">https://classic.yarnpkg.com/en/docs/install</a>)</li><li>Instalar los paquetes requeridos</li><li>En el directorio clonado</li><li>Ejecutar: cd app</li><li>Ejecutar: yarn install</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Masterclass de IoT Center por InfluxData

This Workshop introduces IoT Center, a monitoring application based on InfluxDB. It covers installation, UI, libraries, and monitoring Node.js applications. InfluxDB is a scalable time series platform suitable for monitoring, analytics, and IoT applications. The IoT Center includes a virtual device emulator and supports temperature, humidity, pressure, CO2 level, and GPS coordinates. The Workshop also explores querying data, managing configuration entities, and adding geovisualization to the dashboard.

InfluxDB is an open source time series database that empowers developers to build IoT, analytics and monitoring software. It is purpose-built to handle the massive volumes and countless sources of time-stamped data produced sensors, applications and infrastructure. This workshop showcases a fully functional sample application called IoT Center that is built on InfluxDB. This application demonstrates the capabilities of the InfluxDB platform to develop a JavaScript-enabled time-series-based application. It collects, stores and displays a set of values that include temperature, humidity, pressure, CO2 concentration, air quality, as well as provide GPS coordinates from a set of IoT devices. With this data stored in InfluxDB, the application can query this data for display as well as write data back into the database. This hands-on workshop will show students how to install this open source code to learn how to query and write to InfluxDB using the InfluxDB JavaScript client, and gain familiarity with the Flux lang query language which is designed for querying, analyzing, and acting on time series data. And finally, collect and visualize performance data of the Node JS application. Prerequisites <ul><li>Registered free InfluxDB Cloud account at <a href="https://cloud2.influxdata.com/">https://cloud2.influxdata.com</a></li><li>Three options available (via Google account, via Microsoft account or via email)</li><li>Test login after the registration and save credentials for the workshop</li><li>Installation of the git tool (e.g. from <a href="https://git-scm.com/downloads">https://git-scm.com/downloads</a>)</li><li>IoT Center clone</li><li>Run: git clone <a href="https://github.com/bonitoo-io/iot-center-v2">https://github.com/bonitoo-io/iot-center-v2</a></li><li>Installed nodejs (from <a href="https://nodejs.org/en/download">https://nodejs.org/en/download</a>)</li><li>Installed yarn package manager (from <a href="https://classic.yarnpkg.com/en/docs/install">https://classic.yarnpkg.com/en/docs/install</a>)</li><li>Installed required packages</li><li>In the cloned directory</li><li>Run: cd app</li><li>Run: yarn install</li></ul> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

IoT Center Workshop by InfluxData

Miroslav Malecha

Panel Discussion: Node.js in the Cloud

Ali Spittel

Eran Hammer

Los beneficios de Node.js para desarrollar aplicaciones en tiempo real a gran escala son muy conocidos. A medida que las arquitecturas de Node.js se vuelven más complejas, la visualización de su arquitectura basada en microservicios es crucial. Sin embargo, la visualización de los microservicios es increíblemente compleja dada la escala y las transacciones entre ellos. No solo necesitas visualizar tus aplicaciones de Node.js, sino también analizar la salud, el flujo y el rendimiento de las aplicaciones para tener una solución de observabilidad completa. En esta charla, repasaremos los desafíos de escalar tus aplicaciones de Node.js y las herramientas (como el rastreo distribuido) disponibles para escalar con confianza. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Observabilidad Integral a través del Rastreo Distribuido en Node.js

Welcome to the session on comprehensive observability via distributed tracing on Node.js. We'll explore the challenges of microservices and troubleshoot distributed applications using an example. Correlation is the missing piece in troubleshooting distributed applications. Distributed tracing helps pinpoint issues that logging or metrics may miss, reducing mean time to resolution. It provides visualization of microservices architecture, actionable data, and enables code optimization.

The benefits of Node.js to develop real-time applications at scale are very well known. As Node.js architectures get more and more complex, visualization of your microservice-based architecture is crucial. However, the visualization of microservices is incredibly complex given the scale and the transactions across them. You not only need to visualize your Node.js applications but also analyze the health, flow, and performance of applications to have a complete observability solution. In this talk, we'll go over the challenges of scaling your Node.js applications and tools (such as distributed tracing) available to you to scale with confidence. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Comprehensive Observability via Distributed Tracing on Node.js8

Chinmay Gaikwad

Durante años, AWS ha ofrecido CloudFormation como un enfoque para la Infraestructura como Código (IaC). CloudFormation permite provisionar pilas de aplicaciones a partir de plantillas en formato JSON o YAML. Desafortunadamente, debido a su tamaño y complejidad, las plantillas de CloudFormation han ganado una reputación de ser difíciles de manejar.El AWS Cloud Development Kit (CDK) mitiga parte de la complejidad asociada con CloudFormation, permitiendo a los desarrolladores definir programáticamente su arquitectura en la nube utilizando lenguajes de alto nivel familiares como JavaScript y TypeScript. Los proyectos de CDK pueden ser implementados a través de CloudFormation, manteniendo todos los beneficios de CloudFormation, como despliegues repetibles y detección de desviaciones. Esta charla presentará el CDK en el contexto de Node.js y demostrará cómo se puede aprovechar para provisionar arquitecturas nativas en la nube. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Introducción al AWS CDK: Infraestructura como Node

The CDK is an AWS-specific infrastructure as code tool that supports multiple languages and allows you to maintain state about your application and update it without going through the same checks as making direct API calls. The CDK allows developers to write their infrastructure as well as their applications using JavaScript and TypeScript, leveraging their existing skills. It introduces an API using TypeScript and constructs to simplify building and composing CDK applications. The CDK can be used to create a variety of resources, including a static S3 site, and offers first-class support from AWS.

For years AWS has offered CloudFormation as an approach to Infrastructure as Code (IaC). CloudFormation allows application stacks to be provisioned from JSON or YAML formatted templates. Unfortunately, due to their size and complexity, CloudFormation templates have earned a reputation as being unwieldy to work with.The AWS Cloud Development Kit (CDK) mitigates some of the complexity associated with CloudFormation allowing developers to programmatically define their cloud architecture using familiar high-level languages such as JavaScript and TypeScript. CDK projects can then be deployed via CloudFormation, while retaining all of the benefits of CloudFormation, such as repeatable deployments and drift detection. This talk will introduce the CDK in the context of Node.js and demonstrate how it can be leveraged to provision cloud native architectures. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Lightning Talks QnA, Day 1, Node Congress

Antony Bello

El masterclass "APIs web con Sails" se centra en la creación de APIs web con Node.js utilizando el framework Sails.El masterclass comienza con una introducción para principiantes al framework Sails, abordamos cómo empezar con Sails, instalar Sails en tu máquina, y luego profundizamos en la filosofía, conceptos y características del framework Sails.Continuamos con la construcción práctica de una API web en Sails desde cero y probamos los endpoints con Postman. Finalizamos escribiendo pruebas para los endpoints, configurando una acción de GitHub para ejecutar nuestras pruebas cuando hacemos push a GitHub, y desplegando nuestra API web en la nube de Heroku. Prerrequisitos:Un buen entendimiento de los fundamentos de JavaScript y Node.js. Prefiero usar VS Code para editar el código, pero puedes usar el editor que desees. Se espera que tengas Node.js y NPM preinstalados. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

APIs web con Sails

This workshop introduces the Sales framework for building web APIs with Node.js. Sales provides a clear structure for codebases and includes building blocks for real-time functionality. It is used by companies like Microsoft and Amazon. The workshop covers topics such as building endpoints, creating models, handling user authentication, and creating and retrieving suites. The workshop concludes with next steps and resources for further learning.

The "Web APIs with Sails" workshop focuses on creating Node.js web APIs with the Sails framework.The workshop begins with a beginner's introduction to the Sails framework, we touch on getting started with Sails, installing Sails in your machine, then touch on Sails framework philosophy, concepts, and features.We continue with the hands-on building of a Web API in Sails from Scratch and test the endpoints with Postman. We round up writing tests for the endpoints, setting up a GitHub action to run our tests when we push to GitHub then deploy our Web API to Heroku cloud. Prerequisites:A good understanding of JavaScript and Node.js fundamentals. I prefer to use VS Code for code editing but you can use and editor you want. I expect a preinstall of Node.js and NPM <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Web APIs with Sails

Kelvin Omereshone

Lightning Talks, Day 2, Node Congress

Want to master Fullstack: JS Backend, DevOps, Architecture? Join a two-day conference on all things Node.js, gathering Back-end and Full-stack engineers across the globe in the cloud is here to help you staying up-to-date on the latest Node.js tech.

Node Congress

I’m attending @NodeCongress, the biggest conf on #JavaScript backends – by clicking the badge you may get a free remote ticket & join me there with 5k other #nodejs devs & 15 great speakers #deno #cloudflare #awscloud

EXPLORE THE NEW FRONTIER OF BATTLE TESTED BACKENDS

A two-day conference on all things Node.js, gathering Back-end and Full-stack engineers across the globe in the cloud. Stay up-to-date on the latest Node.js tech and watch the talks from the biggest virtual event for the Node.js community.

Node Congress 2021

Master Fullstack: JS Backends, DevOps, Architecture