Name: DevOps.js Conf 2024
Start: 2024-02-15T14:45:00.000Z
End: 2024-02-16T18:00:00.000Z

Lera

Seungho Park

Naman Goel

Jamal Sinclair O'Garro

Adrian Hajdin

Thibault Van den Broecke

Varun

John Nguyen

Zoltan Kochan

Charles

Rosario Terranova

Georgi

Oscar Pagani

Robert

Goran

Bernie Green

Mathieu Habegger

Nils BUntenbeck

Ian Sutherland

JDog

Prabhdeep

Mel Moe

Svetlana Smirnova

Ivan Almasi

Missy

Martin Jensen

Denis Radin

Pagal3

Natalia Sabadysh

Alla Kaplia

Norm Crandall

En esta masterclass, discutimos los méritos de la arquitectura sin servidor y cómo se puede aplicar al espacio de la IA. Exploraremos opciones para construir aplicaciones RAG sin servidor para un enfoque más lambda-esque a la IA. A continuación, nos pondremos manos a la obra y construiremos una aplicación CRUD de muestra que te permite almacenar información y consultarla utilizando un LLM con Workers AI, Vectorize, D1 y Cloudflare Workers.

IA a demanda: IA sin servidor

The workshop explores the intersection of serverless and AI, discussing the basics, benefits, scalability, and challenges of serverless. It also delves into AI architecture components, vector databases, and the use of context in querying. The workshop demonstrates the building process using HonoJS and Linkchain, setting up Cloudflare Workers and Wrangler, and loading data into a vector database. It also covers the creation of a chatbot with Cloudflare Workers AI and the use of API tokens and environment variables. The workshop concludes with information on pricing and recommendations for further questions.

In this workshop, we discuss the merits of serverless architecture and how it can be applied to the AI space. We'll explore options around building serverless RAG applications for a more lambda-esque approach to AI. Next, we'll get hands on and build a sample CRUD app that allows you to store information and query it using an LLM with Workers AI, Vectorize, D1, and Cloudflare Workers.

AI on Demand: Serverless AI

Nathan Disidore

Un recorrido por la evolución de SSR en los últimos doce años. Cubriremos cómo cambiaron las técnicas, los problemas típicos, las herramientas que puedes usar y varias soluciones, todo desde el punto de vista de mi experiencia personal como consumidor y mantenedor.

You Don’t Know How to SSR

The Talk covers the speaker's personal journey into server-side rendering (SSR) and the evolution of web development frameworks. It explores the use of jQuery for animations in SSR, the challenges faced in integrating React with Umbraco, and the creation of a custom SSR framework. The Talk also discusses the benefits of Next.js and the use of serverless artifacts for deployment. Finally, it highlights the features of Astro, including its function per route capability.

A walk-through of the evolution of SSR in the last twelve years. We will cover how techniques changed, typical problems, tools you can use and various solutions, all from the point of view of my personal experience as a consumer and maintainer.

Emanuele Stoppa

Escalar bases de código grandes, especialmente monorepos, puede ser una pesadilla en los sistemas de Integración Continua (CI). El panorama actual de las herramientas de CI tiende a ser orientado a máquinas, de bajo nivel y exigente en términos de mantenimiento. Lo peor es que a menudo están desconectadas de las necesidades y el flujo de trabajo real del desarrollador.¿Por qué es un obstáculo el CI? Porque los sistemas de CI actuales son comodines, sin una comprensión específica de tu base de código. No pueden aprovechar el contexto en el que operan para ofrecer optimizaciones.En esta charla, exploraremos el futuro del CI, diseñado específicamente para bases de código grandes y monorepos. Imagina un sistema de CI que comprenda la estructura de tu espacio de trabajo, paralelice dinámicamente las tareas en máquinas utilizando datos históricos, y haga todo esto con una configuración mínima y de alto nivel. Repensemos el CI, haciéndolo más inteligente, eficiente y alineado con las necesidades del desarrollador.

Poner fin al dolor: Repensando CI para Monorepos Grandes

Today's Talk discusses rethinking CI in monorepos, with a focus on leveraging the implicit graph of project dependencies to optimize build times and manage complexity. The use of NX Replay and NX Agents is highlighted as a way to enhance CI efficiency by caching previous computations and distributing tasks across multiple machines. Fine-grained distribution and flakiness detection are discussed as methods to improve distribution efficiency and ensure a clean setup. Enabling distribution with NX Agents simplifies the setup process, and NX Cloud offers dynamic scaling and cost reduction. Overall, the Talk explores strategies to improve the scalability and efficiency of CI pipelines in monorepos.

Scaling large codebases, especially monorepos, can be a nightmare on Continuous Integration (CI) systems. The current landscape of CI tools leans towards being machine-oriented, low-level, and demanding in terms of maintenance. What's worse, they're often disassociated from the developer's actual needs and workflow.Why is CI a stumbling block? Because current CI systems are jacks-of-all-trades, with no specific understanding of your codebase. They can't take advantage of the context they operate in to offer optimizations.In this talk, we'll explore the future of CI, designed specifically for large codebases and monorepos. Imagine a CI system that understands the structure of your workspace, dynamically parallelizes tasks across machines using historical data, and does all of this with a minimal, high-level configuration. Let's rethink CI, making it smarter, more efficient, and aligned with developer needs.

End the Pain: Rethinking CI for Large Monorepos

Juri Strumpflohner

Desplegar una aplicación no es un proceso fácil. Te encontrarás con muchos problemas y puntos de dolor que resolver para que funcione correctamente. Lo peor es: ahora que puedes desplegar tu aplicación en producción, ¿cómo no vas a poder desplegar también todas las ramas del proyecto para tener acceso a vistas previas en vivo? ¿Y poder hacer un revert rápido a pedido?Afortunadamente, el clásico conjunto de herramientas de DevOps tiene todo lo que necesitas para lograrlo sin comprometer tu salud mental. Al mezclar expertamente Git, herramientas de Unix y llamadas a API, y orquestar todo ello con JavaScript, dominarás el secreto de los despliegues atómicos seguros.No necesitarás depender de servicios comerciales: ¡conviértete en el maestro perfecto de las herramientas y netlifica tu aplicación desde casa!

Despliegue Atómico para Hipsters de JavaScript

This Talk discusses atomic deployment for JavaScript and TypeScript, focusing on automated deployment processes, Git hooks, and using hard links to copy changes. The speaker demonstrates setting up a bare repository, configuring deployment variables, and using the post-receive hook to push changes to production. They also cover environment setup, branch configuration, and the build process. The Talk concludes with tips on real use cases, webhooks, and wrapping the deployment process.

Deploying an app is all but an easy process. You will encounter a lot of glitches and pain points to solve to have it working properly. The worst is: that now that you can deploy your app in production, how can't you also deploy all branches in the project to get access to live previews? And be able to do a fast-revert on-demand?Fortunately, the classic DevOps toolkit has all you need to achieve it without compromising your mental health. By expertly mixing Git, Unix tools, and API calls, and orchestrating all of them with JavaScript, you'll master the secret of safe atomic deployments.No more need to rely on commercial services: become the perfect tool master and netlifize your app right at home!

Atomic Deployment for JS Hipsters

m4dz 

En esta sesión, comparto contigo cómo AWS CDK y AWS Toolkit pueden simplificar la experiencia del desarrollador para ejecutar cargas de trabajo sin servidor en la nubeUna sesión sin diapositivas, solo un IDE y una CLI para implementar una API en la nube, actualizarla rápidamente y recuperar registros sin salir de tu IDE favorito!

Desmitificar la DX para funciones Lambda

Welcome to this session on Lambda Developer Experience. Learn about using AWS Cloud Development Kit (CDK) to write code in your favorite language and automatically generate CloudFormation templates. Test locally with the SAM CLI and deploy with CDK. Accelerate testing and updates with CDK flags. Use the AWS Toolkit to invoke Lambda functions, analyze logs, and generate code with Application Composer.

In this session, I share with you how AWS CDK and AWS Toolkit can simplify the developer experience to run serverless workloads in the cloudA session with no slides, just an IDE and a CLI for deploying an API in the cloud, update it quickly, and retrieve logs without leaving your favourite IDE!

Demystify the  DX for Lambda functions

Luca Mezzalira

Aprende a publicar paquetes npm como un profesional utilizando el poder de Nx. Partiendo de un repositorio básico con varios paquetes, estableceremos una estrategia de versionado, una estructura de registro de cambios y un flujo de trabajo de publicación. Después, exploraremos las numerosas características y opciones de Nx Release que te permiten adaptarte a los procesos de tu organización.

Versionado y Publicación de Paquetes con Nx Release

In this Talk, Austin Faisal introduces Nx Release and demonstrates how to improve versioning and publishing processes with it. The tool allows for a dry run to preview changes, keeps packages in sync, and generates changelogs. It also automates staging, committing, tagging, and publishing changes to the registry. Nx Release offers additional features such as independent versioning, automatic versioning with conventional commits, creating GitHub releases, customizable changelog rendering, and a programmable API.

Learn to publish npm packages like a pro using the power of Nx. Starting from a basic repo with several packages, we'll establish a versioning strategy, changelog structure, and publishing workflow. Afterwards, we'll explore the many features and options of Nx release that allow you to adapt to your organization's processes.

Versioning and Publishing Packages with Nx Release

Austin Fahsl

Muchas empresas están adoptando completamente AWS y, por lo tanto, están adoptando su conjunto completo de herramientas de código para sus procesos de CI/CD. Sin embargo, aunque CodePipeline es la plataforma para este proceso, puede que no sea la más fácil de usar. En una configuración de Monorepo, es típico crear múltiples pipelines de CI/CD para cada paquete. Sin embargo, hay varias precauciones que debes tener en cuenta. Por ejemplo, es posible que te encuentres con escenarios en los que se activan múltiples pipelines incluso si solo modificaste un archivo, o puedes cuestionar la necesidad de crear múltiples ramas para cada pipeline. En esta charla, proporcionamos consejos valiosos para construir un sofisticado CodePipeline utilizando CDK en un entorno de Monorepo. Las técnicas discutidas en esta charla también son aplicables a otras herramientas de CI/CD.

Construyendo un sofisticado CodePipeline con CDK en una configuración de Monorepo

Imagine starting as an AWS DevOps engineer in a small company. Your boss wants an all-in AWS approach, with CICD entirely on AWS for automated deployments. Use AWS CDK for creating a pipeline, stages, and actions. Learn how to handle multiple pipelines for different accounts and handle manual approval for staging and production environments. Discover how to trigger pipelines with EventBridge and Lambda, and create sophisticated pipelines for different scenarios.

Many companies are going all-in AWS and thus adopting their complete CodeSuite for their CI/CD processes. However, while CodePipeline is the platform for this process, it may not be the most user-friendly. In a Monorepo setup, it's typical to create multiple CI/CD pipelines for each package. However, there are several caveats to be aware of. For instance, you may encounter scenarios where multiple pipelines get triggered even if you just modified one file, or you may question the need to create multiple branches for each pipeline. In this talk, we provide valuable tips for building a sophisticated CodePipeline using CDK in a Monorepo environment. The techniques discussed in this talk are also transferrable to other CI/CD tools.

Building a sophisticated CodePipeline with CDK in a Monorepo Setup

CI/CD ha sido esencial para cualquier desarrollo y lanzamiento de productos web productivos. Sin embargo, aunque la accesibilidad siempre es un aspecto importante para cualquier producto web que incluya una interfaz de usuario, a menudo se pasa por alto o se considera como un paso manual que consume mucho tiempo, fuera del flujo de CI/CD. ¿Cómo podemos automatizar las pruebas de accesibilidad dentro de nuestro CI/CD para mejorar la experiencia del desarrollador y la colaboración en equipo? ¿Qué herramientas podemos utilizar para integrar y aprovechar el cumplimiento de accesibilidad en nuestro CI/CD? Únete a mi charla y descubrámoslo.

CI/CD accesible

Maya Min, a senior software engineer at Microsoft Industry AI, discusses the importance of accessibility testing and its relation to CIDI. WCAG provides guidelines for accessibility compliance, covering various aspects such as color contrast, navigation, and content layout. Maya explores automating accessibility testing through UI components and different testing levels. They recommend xCore and Playwright for end-to-end browser testing and integrating accessibility testing into CI/CD workflows using tools like GitLab and Azure Pipeline.

CI/CD has been essential for any productive web product development and release. However, while accessibility is always an important aspect for any Web product included UI, it is often overlooked or considered as a time-consuming manual step, outside of the CI/CD flow. How can we automate accessibility testing within our CI/CD for better developer experience and team collaboration? What tools can we use to integrate and leverage accessibility compliance in our CI/CD? Join my talk and let's find out.

Accessible CI/CD 

Maya Shavin

Hablaremos sobre algunos de los puntos problemáticos y exploraremos recetas para una gestión de paquetes efectiva en Monorepos. Discutiremos cómo funciona la gestión de paquetes con npm, pnpm y Yarn. Además, te mostraré una nueva herramienta que es menos conocida pero mejora mucho la experiencia del desarrollador.

Gestión de paquetes en Monorepos

This Talk discusses pain points and effective package management in monorepos, including the use of hoisted or isolated layouts and the challenges of working with peer dependencies. It introduces the tool Bit, which addresses these issues and handles dependency management and version control. Bit enables automatic installation and management of dependencies, supports multiple versions of a peer dependency, and seamlessly updates components across different environments.

We’ll talk about some of the pain points and look into recipes for effective package management in monorepos.  We’ll discuss how package management works with npm, pnpm, and Yarn. Furthermore, I’ll show you a new tool that is less known but improves developer experience by a lot.

Package Management in Monorepos

Este taller te permite aprender cómo desarrollar aplicaciones React y luego desplegarlas en la nube (o construirlas en la consola) junto con un backend completamente abstracto, sin una configuración de backend compleja, simplificando la construcción y el despliegue de aplicaciones frontend y web en la nube.

Masterclass de Frontend en la Nube Hecho Fácil - Un Taller de ReactJS + AWS

We will be building a simple React application using Wig, a toolchain for JavaScript, React, and Wing lang. The Wing compiler allows us to compile applications into Terraform JSON files that can be deployed on AWS. We can handle events on the cloud bucket, connect the backend and frontend using Vite, and use environment variables to expose the API gateway URL. We can create a REST API interface for the application and connect it to a DynamoDB for data storage. Lastly, we can use WebSockets to synchronize the counter with the backend and deploy the application to AWS using Terraform and AWS CLI.

This workshop enables you to learn how to develop React applications, and then deploy them to the cloud (or building them to the console) coupled with a backend, fully abstracted, with no complex backend configuration, simplifying the building and deployment of frontend &amp; web apps to the cloud.

Frontend to the Cloud Made Easy - A ReactJS + AWS Workshop

Eyal Keren

En esta masterclass descubriremos qué significa Infraestructura Declarativa y cómo puede funcionar en TypeScript para expresar de manera natural conceptos de sistemas distribuidos de alto nivel (como servicios backend, llamadas a API, consultas a bases de datos, mensajería Pub/Sub, almacenamiento en caché y más), a través del poder del análisis estático y la generación de código.El resultado es un proceso de DevOps completamente reinventado, con aprovisionamiento automático de infraestructura y observabilidad integrada, que se implementa directamente en tu propia nube. Tabla de contenidos:- Introducción- Evolución del desarrollo backend, desde servidores hasta el mundo nativo de la nube actual impulsado por DevOps y GitOps- ¿Qué es Cloud Native y cómo construimos aplicaciones backend modernas? (Mostrando una arquitectura de microservicios impulsada por Express.js y Terraform)- ¿Qué es Infraestructura Declarativa? ¿Cómo se ve el espacio?- ¿Qué problemas resuelve en comparación con las prácticas tradicionales de DevOps?- ¿Cómo se relaciona con Terraform/AWS CDK para el aprovisionamiento de infraestructura?- ¿Cuáles son las desventajas?- Construyendo un backend Cloud Native con Infraestructura Declarativa

Infraestructura Declarativa: Repensando Cloud Native para JS

Today's workshop focused on DevOps and infrastructure, highlighting the importance of declarative infrastructure and quality in software. Encore, an open source SDK, was introduced as a solution to automate DevOps and improve workflow. It offers a seamless local development experience, automatic provisioning of cloud infrastructure, and integration with observability providers. Encore enables building and deploying applications with built-in DevOps automation, features like PubSub and authentication support, and a Cloud Dashboard for monitoring and management. It also allows for fast building of additional services, such as an analytics backend, and provides a complete system solution without the need for manual infrastructure setup.

In this talk we uncover what Declarative Infrastructure means, and how it can work in TypeScript to naturally express higher-level distributed systems concepts (such as backend services, API calls, database queries, Pub/Sub messaging, caching and more), through the power of static analysis and code generation.The outcome is a fully reimagined DevOps process, with automatic infrastructure provisioning and built-in observability, that deploys straight to your own cloud. Table of contents:- Introduction- Evolution of backend development, from servers to today's cloud-native world powered by DevOps and GitOps- What is Cloud Native, and how do we build modern backend applications? (Showing a microservices architecture powered by Express.js and Terraform)- What is Declarative Infrastructure? What does the space look like?- What problems does it solve compared to traditional DevOps practices?- How does it relate to Terraform/AWS CDK for infrastructure provisioning?- What are the downsides?- Building a Cloud Native backend with Declarative Infrastructure

Declarative Infrastructure: Rethinking Cloud Native for JS

André Eriksson

Hablemos sobre la hidratación y los problemas que crea. La resumibilidad es una alternativa a la hidratación que no obliga a la ejecución ansiosa del código del lado del cliente, lo que resulta en aplicaciones instantáneas incluso a medida que la aplicación se vuelve más compleja.

Qwik: El Enfoque Sin Hidratación para Sitios de Alto Rendimiento

Builder.io is a headless visual CMS that allows drag and drop of UI components. Core Web Vitals are important for improving website performance. Hydration in frameworks affects performance and interaction with the app. Qwik offers a different approach to hydration, eliminating the need for downloading unnecessary code. Qwik's resumability feature improves performance by starting with HTML and avoiding the re-execution of code.

Let's talk about hydration and the problems it creates. Resumability is an alternative to hydration which does not force eager execution of client side code resulting in instant on applications even as the application scales in coplexity.

Qwik - The No Hydration Approach to Performant Sites

Miško Hevery

La velocidad de iteración es la clave para desbloquear el potencial de tus equipos técnicos y de negocio. En esta masterclass, construiremos los cimientos para un monorepo altamente escalable utilizando Turborepo y hablaremos sobre las filosofías detrás de la arquitectura de bases de código para equipos de todas las escalas. A través del poder del almacenamiento en caché remoto, nunca haremos el mismo trabajo dos veces y entregaremos tus aplicaciones a la velocidad de Turbo.

Envía tu interfaz de usuario más rápido con Turborepo

The Turboverse focuses on making the development process faster and more efficient. TurboPak is an incremental bundler with function-level caching, and TurboRepo is a high-performance build system with features like incremental building, remote caching, and parallel execution. TurboRepo can optimize task runners, set up monorepos, and speed up development time. vclink-repo enables seamless integration with the Vercel remote cache, and Conformance and Codoners provide static analysis and automated code reviews. TurboPak and TurboRepo offer faster CI processes and exciting advancements in web bundling.

Iteration velocity is the key to unlocking the potential of your technical teams and business. In this talk, we'll build the groundwork for a highly scalable monorepo using Turborepo and talk about the philosophies behind architecting codebases for teams of all scales. Through the power of Remote Caching, we'll never do the same work twice and we'll deliver your applications at the speed of Turbo.

Ship Your UI Faster With Turborepo

Anthony Shew

Todo comenzó con la fisión del monolito en microservicios. Esto estableció límites lógicos y físicos, fusionando las dimensiones de infraestructura y software. Si bien los microservicios simplificaron cómo los equipos desarrollan de forma independiente, agregaron complejidades adicionales en torno al rendimiento, la corrección, la gestión general y, en última instancia, un ciclo de desarrollo más lento. En esta charla, profundizaremos en cómo diseñar e implementar un monolito componible basado en Fastify, la comunicación sin red entre servicios y cómo manejar un desarrollo eficiente entre equipos al implementar un único artefacto en Kubernetes. ¿Suena como magia? ¡Descubramos el truco juntos!

Construyendo y Operando un Monolito Componible Moderno

In this talk, Luca introduces the concept of the modern composable monolith and discusses the challenges of microservices. He emphasizes the importance of developing modular monoliths and introduces Fastify and the Platformatic Runtime as tools for this approach. The Platformatic Runtime simplifies running modular, monolithic applications, and standardizing interfaces and communication is crucial in this context. Lastly, Luca introduces Meraki as a UI-driven tool for building composable monoliths and invites developers to join their marketplace for revolutionizing the operational experience of microservices.

It all started with the monolith’s fission into microservices. This set logical and physical boundaries, fusing the infrastructure and software dimensions. While microservices simplified how teams develop independently, it added extra complexities around performance, correctness, general management, and ultimately a slower development cycle. In this talk, we will dive deep into how to architect and implement a Fastify-based composable monolith, cross-service network-less communication, and how to handle efficient development across teams while deploying a single artifact in Kubernetes. Does it sound like magic?Let's discover the trick together!

Building and Operating a Modern Composable Monolith

Luca Maraschi

JavaScript ya no es un lenguaje limitado a los navegadores. Nuevos estándares están permitiendo entornos de ejecución totalmente portátiles y livianos, para hacer de JavaScript el lenguaje definitivo para aplicaciones isomórficas.Exploraremos casos de uso, algunos experimentales, otros consolidados, para llevar nuestro juego de Wasm con JavaScript al siguiente nivel.

JavaScript a Wasi Habilitado Wasm: Composición Portátil de JavaScript

JavaScript code is converted to low-level binaries by JavaScript engines like MV8, Chakra, and SpiderMonkey. WebAssembly allows writing code in other languages and compiling it to run on a JavaScript engine. External functions can be imported in WebAssembly using the import statement. WebAssembly can run in non-browser scenarios with additional interfaces like WASI and provides memory isolation. The Jco toolchain is an experimental tool for componentizing JavaScript code into WASM modules.

JavaScript is no longer a language confined to the browsers. New standards are enabling fully portable, lightweight runtimes, to make JavaScript the definitive language for isomorphic applications. Let's explore use-cases, some experimental, some consolidated, to take our Wasm game with JavaScript, to the next level.

JavaScript to Wasi Enabled Wasm: Portable JavaScript Composition

Natalia Venditto

Descubre técnicas avanzadas para rastrear y resolver errores en aplicaciones JavaScript, utilizando Sentry como un poderoso aliado. Esta sesión explorará el arte de identificar problemas antes de que afecten a los usuarios, optimizando tu proceso de manejo de errores y mejorando el rendimiento de la aplicación.

Seguimiento de errores de JavaScript de próximo nivel con Sentry

We're going to be talking about next level JavaScript error tracking with Sentry. Error tracking is the process of identifying, recording, and managing errors in a web application. Traditional JavaScript error tracking methods have disadvantages and lack context about the device and user. You can automate error tracking with Sentry, an open source error tracking tool that helps developers monitor and fix crashes in real time. Setting up Sentry is simple using the Sentry SDK and configuring with the DSN.

Discover advanced techniques to track and resolve errors in JavaScript applications, using Sentry as a powerful ally. This session will explore the art of pinpointing issues before they hit users, streamlining your error-handling process, and enhancing application performance.

Next-Level JavaScript Error Tracking with Sentry

Ebenezer Don

Una inmersión profunda en cómo generamos automáticamente definiciones de TypeScript para el tiempo de ejecución basado en V8 que impulsa a los trabajadores de Cloudflare. Daremos una visión general de cómo utilizamos la API del compilador de TypeScript, cómo mejoramos las definiciones auto-generadas con anulaciones escritas por el usuario para mejorar la ergonomía, y cómo creamos un servicio para construir tipos para las configuraciones de compatibilidad específicas de los usuarios.

Generando TypeScript con TypeScript

This talk discusses how TypeScript definitions are automatically generated for CloudFlare workers using runtime type information. The encoding and transformation of type information is explained, with runtime API types being encoded in C++ and further processed in TypeScript. The process of improving type definitions and achieving compatibility is also covered, including fixing problems with iterators and using human input to improve developer ergonomics. The talk concludes with a plan to build Types as a Service, a Cloudflare worker that dynamically generates NPM packages containing TypeScript definition files.

A deep-dive into how we automatically generate TypeScript definitions for the V8-based runtime that powers Cloudflare Workers. We'll give an overview of how we use the TypeScript compiler API, how we enhance auto-generated definitions with user-written overrides to improve ergonomics, and how we created a service to build types for users' specific compatibility settings.

Generating TypeScript with TypeScript

Brendan Coll

En esta charla, repasaremos las diversas iteraciones por las que pasó el equipo de Yarn al diseñar uno de los software más críticos en el ecosistema de JavaScript. Discutiremos algunas de las principales decisiones, compensaciones, errores y éxitos que enfrentamos, y reflexionaremos sobre las evoluciones futuras y los desafíos que nos esperan. Al final de esta charla, tendrás una mejor comprensión del trabajo que realizan los equipos de código abierto a gran escala detrás del equipo, y esperamos que tengas una mejor comprensión de lo que hace que el código abierto sea tan especial.

Yarn: De Diseño a Implementación

Today we'll discuss the evolution and implementation of YARN, which focuses on determinism and stability. YARN Modern was re-architected to support projects with multiple packages and embraced Monorepos. YARN 2 improved workspace implementation, codebase partitioning, and stability. Dependency resolution and linking in YARN are handled by different resolvers and fetchers. YARN has a plugin system, a constraint engine, and a redesigned website. It prioritizes compatibility, performance, testing, and contributions to other projects.

In this talk, we'll go over the various iterations the Yarn team went through designing one of the most critical software in the JavaScript ecosystem. We'll discuss some of the main choices, trade-offs, errors, and successes we faced, and think about evolutions to come and future challenges that await us. By the end of this talk you'll have a better understanding of the work large-scale open-source teams do behind the team, and hopefully a better understanding of what makes open-source so special.

Yarn: From Design to Implementation

Maël Nison

La gestión de incidentes puede ser desafiante y lanzarte bolas curvas con problemas inesperados, lo que resulta en pérdida de datos, tiempos de inactividad y en general, pérdida de dinero y horas de sueño, ¡PERO! Hay cosas prácticas que podrías hacer para que sea un proceso más fluido y manejarlo mejor. ¿Recuerdas cuando estábamos en la escuela y la gente decía: "Escuchar activamente en clase garantiza el 50% de preparación para el próximo examen"? Lo mismo ocurre con ser proactivo en el trabajo de maneras que te prepararán instantáneamente para gestionar incidentes mejor (por la noche o en general). En esta charla, cubriré las formas proactivas que podrías tomar e incorporar en tu rutina diaria, para prepararte para un proceso de gestión de incidentes más fluido y eficiente. También mostraré las mejores prácticas que he finalizado a lo largo de los años y que me han ayudado a tener una visión clara de cómo gestionar incidentes de producción de la manera más rápida y eficiente posible. Abrazar los consejos que te daré te garantizará que no solo hables, sino que también actúes cuando se trata de la gestión de incidentes.

Navegando el Caos: Un Enfoque Holístico para la Gestión de Incidentes

This talk covers the importance of a structured process for incident management and the need for a business mindset. It outlines a five-pillar structured process and emphasizes the importance of staying calm and asking the right questions during incidents. The talk also highlights the importance of effectively identifying, categorizing, and investigating incidents, as well as prioritizing root causes and communicating incident resolutions. Additionally, it discusses the role of incident managers, proactive measures for continuous improvement, and the importance of preparation and a proactive mindset.

Incident management can be challenging and throw you curveballs with unexpected issues, resulting in data loss, downtimes, and overall money &amp; hours of sleep going to waste, BUT! There are practical things you could do to make it a smoother process and handle it better. Remember when we were at school, and people said - "Actively listening in class guarantees 50% prep for the upcoming test"? The same goes for being proactive at work in ways that will instantly prepare you to manage incidents better (at night or in general). In this talk, I'll cover the proactive ways you could take and incorporate into your day-to-day routine, in order to prepare you for a smoother and more efficient incident management process. I will also show the best practices I've finalized over the years that helped me get a clear vision of how to manage production incidents in the quickest &amp; efficient way possible. Embracing the tips I'll give you will guarantee you'll not only talk the talk but also walk the walk when it comes to incident management.

Navigating the Chaos: A Holistic Approach to Incident Management

Hila Fish

Durante casi una década, el proyecto de Investigación y Evaluación de DevOps (DORA) ha estudiado los comportamientos de miles de equipos de desarrollo de software y ha descubierto las capacidades clave que predicen de manera confiable el éxito. DORA ha encontrado consistentemente que no solo los mejores intérpretes lideran sus industrias tanto en velocidad de lanzamiento como en confiabilidad del servicio, sino que también logran mejores resultados comerciales y tienen empleados más satisfechos.En esta sesión, desglosaremos los hallazgos de la investigación y delinearemos los pasos clave que su equipo puede tomar hacia la mejora continua.Combinaremos estos hallazgos con historias "del campo" sobre cómo los equipos están poniendo en práctica estas ideas.

Estado de DevOps: Una historia de mejora continua

This Talk discusses the story of continuous improvement in software development. It emphasizes the importance of measuring software delivery performance using metrics such as lead time, deployment frequency, change fail rate, and time to restore. Code reviews play a significant role in improving software delivery, and exploring the potential impact of AI on code reviews is recommended. Focusing on documentation and proper utilization of the cloud can improve organizational performance. Finally, a good culture, user focus, and collaborative platform team are crucial for success in software development.

For nearly a decade, the DevOps Research and Assessment (DORA) project has studied the behaviors of thousands of software development teams and discovered the key capabilities that reliably predict success. DORA has consistently found that not only do top performers lead their industries in both release velocity and service reliability, they achieve better business outcomes and have more satisfied employees.In this session, we’ll unpack the research findings and outline key steps your team can take toward continuous improvement.We will couple these findings with stories "from the field" about how teams are putting these ideas into practice.

State of DevOps - A Continuous Improvement Story

Amanda Lewis

Nathen Harvey

A pesar de la emergencia de DevOps para unir los equipos de desarrollo, soporte y SRE mediante el uso de procesos comunes, todavía enfrentamos desafíos culturales y de herramientas que crean silos entre el desarrollo y SRE. Específicamente, a menudo utilizamos diferentes herramientas para lograr pruebas similares: por ejemplo, validar la experiencia del usuario en producción utilizando Monitorización Sintética y en desarrollo utilizando pruebas de extremo a extremo. Al unir fuerzas en torno a herramientas comunes, podemos utilizar la misma herramienta tanto para la monitorización en producción como para las pruebas dentro de CI. En esta charla, discutiré cómo la Monitorización Sintética y las Pruebas de Extremo a Extremo son dos caras de la misma moneda. Además, mostraré cómo se pueden lograr la monitorización en producción y las pruebas en desarrollo para aplicaciones basadas en JavaScript utilizando Playwright con Typescript, GitHub Actions y Elastic Synthetics.

Monitorización Sintética y Pruebas de Extremo a Extremo: Dos Caras de la Misma Moneda

The Talk discusses the relationship between synthetic monitoring and end-to-end testing, emphasizing the importance of using a common tool set and shifting monitors left as code. Challenges of collaboration and shifting left are addressed, including existing silos, cultural barriers, and different priorities. The process of converting a Playwright test into a monitor is explained, along with wrapping the test as a monitor using the Synthetics project. Running and deploying the monitor are covered, emphasizing the importance of setting parameters and environment variables correctly. The Talk concludes with the importance of monitoring, issue resolution, and collaboration across roles.

Despite the emergency of DevOps to unite development, support and SRE factions together using common processes, we still face cultural and tooling challenges that create the Dev and SRE silos. Specifically, we often use different tools to achieve similar testing: case in point validating the user experience in production using Synthetic Monitoring and in development using E2E testing. By joining forces around common tooling, we can use the same tool for both production monitoring and testing within CI. In this talk, I will discuss how Synthetic Monitoring and E2E Testing are two sides of the same coin. Furthermore, I shall show how production monitoring and development testing can be achieved for JavaScript-based applications using Playwright with Typescript, GitHub Actions and Elastic Synthetics.

Synthetic Monitoring and e2e Testing: 2 Sides of the Same Coin

Carly Richmond

Esta charla desentraña las complejidades de Semantic Versioning (SemVer) mientras se adentra en las complejidades prácticas del mundo real de navegar por el infierno de las dependencias. Obtén nuevos conocimientos sobre el origen y los desafíos de la versiones, descubre los poderes ocultos del esquema de versiones semánticas existente y vislumbra el futuro de la gestión de paquetes. Ya seas un desarrollador experimentado que vive y respira commits convencionales o un recién llegado ansioso por comprender este aspecto esencial de nuestro ecosistema de paquetes, esta charla promete elevar tu comprensión de todo lo relacionado con las especificaciones.

Espec-tacular - SemVer y Más Allá

Welcome to DevOpsJS 2024! We'll be discussing semantics and versioning schemas, particularly semantic versioning (SEMVR). There are concerns about the flaws in SEMVR and the need to embrace change in software development. Dependency hell in the JavaScript ecosystem has been addressed through semantic versioning and new capabilities. However, there are still issues with the SEMBR spec, including absent definitions and problems with build metadata. To improve versioning, we need to address missing definitions and consider a new spec for the future.

This talk unravels the intricacies of Semantic Versioning (SemVer) while delving into the real-world, practical complexities of navigating dependency hell. Gain new insights into the origin of &amp; challenges with versioning, discover the hidden powers of the existing semantic version schema, and catch a glimpse of the future of package management. Whether you're a seasoned developer who lives &amp; breathes conventional commits or a newcomer eager to understand this essential aspect of our package ecosystem, this talk promises to level up your understanding of everything spec.

Spec-tacular - SemVer & Beyond

Darcy Clarke

Esta charla explora el caso de uso de los SLOs y las transformaciones durante la migración al ecosistema sin servidor. La charla comienza presentando las razones por las cuales los SLOs son importantes en el marco de SRE/DevOps. Luego analiza casos de uso específicos de los SLOs, las herramientas utilizadas para medir la eficiencia de los SLOs y presenta los principales obstáculos encontrados al definir y cumplir con los SLOs en el proceso de migración a un ecosistema sin servidor, especialmente al lidiar con las tasas de consumo y las transformaciones.Al final de la charla, la audiencia podrá suscribirse a los siguientes puntos clave:Los SLOs son importantes en un marco de SRE/DevOps y existen numerosas ventajas al implementarlos siempre y cuando se adhieran a un proceso de mejora continua.Adoptar las herramientas y métricas adecuadas es fundamental en la implementación de los SLOs.La migración a un entorno sin servidor añade presión al sistema de observabilidad y es posible que las tasas de consumo y las transformaciones tengan efectos negativos. Nuestro caso de uso mostrará cómo es posible mitigar estos desafíos y aprender de situaciones similares.

Observabilidad sin servidor: Donde se encuentran los SLOs y las transformaciones

This Talk provides an introduction to Serverless Observability and SLOs, explaining the concept of SLOs and their dependency on transforms. It highlights the codependency between SLOs, SLAs, and SLIs and discusses the importance of well-defined SLOs. The Talk also demonstrates how to create and monitor SLOs and alert rules, emphasizing the benefits of burn rate alerting in reducing alert fatigue and improving user experience.

This talk explores the use case of SLOs and transforms whilst migration to the serverless ecosystem. The talk starts by presenting the reasons why SLOs are important in the SRE/DevOps framework. It then analyses specific use cases of SLOs, the tools used for measuring the efficiency of SLOs and presents the main bottlenecks encountered when defining and adhering to SLOs in the process of migrating to a serverless ecosystem, especially when dealing with burn rates and transforms.By the end of the talk, the audience will be able to subscribe to the following takeaways:SLOs are important in a SRE/DevOps framework and there are numerous advantages for implementing them as long as they adhere to a process of continuous improvement.Adopting the right tools and metrics are paramount in the implementation of SLOs.Migrating to serverless adds pressure to the observability system and it is possible that burn rates and transforms will backfire. Our use case will show how it's possible to mitigate these challenges and learn from similar situations.

Serverless Observability: Where SLOs Meet Transforms

Virginia Diana Todea

¿Alguna vez has tenido problemas con la monitorización en tus aplicaciones Node.JS? ¡Ya no más! Compartiendo lo bueno, lo malo y lo desesperante de nuestras propias experiencias, quiero ayudarte a evitar el caos en la monitorización. Veremos cómo conocer realmente cómo funcionan tus aplicaciones te ayuda a tener una monitorización más enfocada. Esto te permite evitar los agujeros negros que la monitorización basada en casillas de verificación puede tener, asegurándote de que las métricas y alertas importantes no se pasen por alto. Además, veremos cómo el registro estratégico y enfocado, la monitorización y las alertas con herramientas como Graylog, Grafana y Prometheus pueden potenciar la resistencia de tu aplicación. Únete para descubrir cómo los patrones y antipatrones de confiabilidad y monitorización pueden ayudar a mejorar la calidad de la aplicación. ¡Volverás armado con información valiosa que puede llevar tu juego de monitorización a otro nivel!

Guardianes de las Aplicaciones: Conquistando la Monitorización de Aplicaciones Node.JS

Monitoring and observability are important for catching bugs before they become noticeable. Examples of monitoring issues include confusion and frustration when monitoring leads to misunderstandings. Teamwork is essential for effective monitoring, automation can streamline processes and improve efficiency. Custom monitoring is necessary to prevent hazards and unnecessary alerts can hurt productivity. Challenges include relying too much on monitoring without addressing root issues and struggling with manual configuration.

Ever struggled with monitoring in your Node.JS apps? Not anymore! By sharing the good, the bad, and the hair-pulling from our own experiences, I want to help you steer clear of monitoring chaos. We’ll see how truly knowing how your apps work help you have more focused monitoring. This allows you to dodge black holes checkbox monitoring can have as you can make sure that important metrics and alerts are not swallowed. Additionally, we’ll see how strategic and focused logging, monitoring, and alerting with tools like Graylog, Grafana and Prometheus can supercharge your app’s resilience. Join to uncover how reliability and monitoring patterns and anti-patterns can help improve app quality. You will return armed with invaluable insights that can skyrocket your monitoring game!

Guardians of the Applications: Conquering Node.JS App Monitoring

Ante Tomić

Spinnaker es una plataforma de entrega continua de código abierto que proporciona gestión de aplicaciones y despliegue para ayudar a los equipos de ingeniería a lanzar cambios de software con confianza y a alta velocidad. Inicialmente fue desarrollado en Netflix y ahora es utilizado por muchos equipos de ingeniería a gran escala. En esta charla, exploraremos cómo podemos aprovecharlo para implementar aplicaciones JavaScript en múltiples proveedores de nube de manera repetible y escalable, aprovechando su conjunto de funciones robusto.

Spinnaker como una Solución de Entrega Continua para Aplicaciones JavaScript

Jamal Sinclair-O'Garro introduces himself as a senior software engineer at Netflix with experience in algorithmic and electronic trading. Spinnaker is a multi-platform continuous delivery platform used by companies like Grubhub, Airbnb, Google, Netflix, Chime, Box, and Target. It provides infrastructure management and deployment through pipelines, allowing gradual rollouts and canary analysis to ensure safe changes. Spinnaker improves velocity and is recommended for streamlining JavaScript applications across different providers.

Spinnaker is an open-source continuous delivery platform that provides application management and deployment to help engineering teams confidently release software changes at a high velocity. It was initially developed at Netflix and is now used by many large-scale engineering teams. In this talk, we will explore how we can leverage it to deploy JavaScript applications to multiple cloud providers in a repeatable and scalable fashion while taking advantage of its robust feature set.

Spinnaker as a Continuous Delivery Solution for JavaScript Apps

DevOps.js

DevOps.js is an event for all the developers and architects involved in building infrastructure and setting up pipelines and deployments for JavaScript applications.

DevOps.js Conf 2024

FocusReactive

Hygraph

Cloudflare

All new and existing Cloudflare account holders are eligible. &nbsp;Once you've created your Cloudflare account, submit your account ID for a chance to win! We're excited for you to get started with Cloudflare today!&nbsp;

Sign-up for a Cloudflare account for your change to win a 40 oz. travel mug

Build your next app on Cloudflare Pages. Deploy to over 300 global locations in a fraction of the time!

FocusReactive is an&nbsp;<meta charset="utf-8" id="isPasted">engineering-led <a href="https://focusreactive.com/services/headless-cms-expert-agency/">Headless CMS Agency</a>&nbsp;and&nbsp;<a href="https://focusreactive.com/next-js-expert-agency/">NextJS&nbsp;development experts</a>. Independent partners of Payload CMS, Sanity, Storyblok, Vercel and Shopify. Delivering&nbsp;<meta charset="utf-8" id="isPasted">Composable content platforms built for AI SEO, growing teams, and marketing velocity.

DevOps.js Conf 2024

The JavaScript DevOps Conference

Lera

Lera

Seungho Park

Naman Goel

Jamal Sinclair O'Garro

Adrian Hajdin

Thibault Van den Broecke

Varun

John Nguyen

Zoltan Kochan

Charles

Rosario Terranova

Georgi

Oscar Pagani

Robert

Goran

Bernie Green

Mathieu Habegger

Nils BUntenbeck

Ian Sutherland

JDog

Prabhdeep

Mel Moe

Svetlana Smirnova

Ivan Almasi

Missy

Martin Jensen

Denis Radin

Pagal3

Natalia Sabadysh

Alla Kaplia

Can

Norm Crandall

Total attendees