Name: DevOps.js Conf 2021
Start: 2021-03-27T23:00:00.000Z
End: 2021-03-29T22:00:00.000Z

Los microservicios presentan muchas ventajas para ejecutar software moderno, pero también traen nuevos desafíos tanto para las tareas de despliegue como operativas. Esta sesión discutirá las ventajas y desafíos de los microservicios y revisará las mejores prácticas para desarrollar una arquitectura basada en microservicios.Discutiremos cómo la orquestación de contenedores usando Kubernetes o Red Hat OpenShift puede ayudarnos y lo uniremos todo con un ejemplo de tuberías de Integración Continua y Entrega Continua (CI/CD) en OpenShift.

Cómo construir tuberías de CI/CD para una aplicación de microservicios

This Talk discusses the benefits of microservices and containers for building CI-CD pipelines. It explains how container technology enables portability and scalability. The challenges of microservices include network communication and testing in isolation. The Talk introduces Tacton, a cloud-native CICD pipeline for Kubernetes, and highlights the use of GitOps and Argo CD. It also discusses the importance of maintaining referential integrity between microservices and the evolving role of operators in the DevOps world.

Microservices present many advantages for running modern software, but they also bring new challenges for both Deployment and Operational tasks. This session will discuss advantages and challenges of microservices and review the best practices of developing a microservice-based architecture.We will discuss how container orchestration using Kubernetes or Red Hat OpenShift can help us and bring it all together with an example of Continuous Integration and Continuous Delivery (CI/CD) pipelines on top of OpenShift.

How to Build CI/CD Pipelines for a Microservices Application

Sasha Rosenbaum

En los últimos años, la comunidad de aplicaciones web de JS ha visto un creciente enfoque y conciencia en cuanto a rendimiento y escalabilidad. Los días en que los sitios de producción prominentes servían páginas completamente en blanco esperando paquetes monolíticos de megabytes de JavaScript están (¡en su mayoría!) detrás de nosotros.Una gran parte de esto ha sido una integración más profunda con las CDNs, después de todo, la latencia de ida y vuelta es uno de los principales determinantes del rendimiento para una audiencia global. Pero los frameworks, y las compañías que los respaldan, tienen enfoques diferentes en cómo pueden ser utilizados, y las complejidades operativas que sus estrategias introducen tienen consecuencias reales.Pero ¿qué pasaría si, en lugar de un origen dinámico que envía instrucciones a una CDN estática, pudieras ejecutar tu aplicación directamente en el borde? Resulta que eso no solo mejora el rendimiento, sino que también simplifica enormemente nuestras vidas en cuanto a implementación y mantenimiento.

El Auge del Borde Dinámico

The Talk discusses the rise of the dynamic edge and the past, present, and future of frontend hosting. It emphasizes the impact of latency on CDN usage and the relevance of CDNs in JavaScript application development. The use of CDNs for rapidly changing content and the benefits of the Jamstack approach are explored. The future of the dynamic edge lies in platforms like Cloudflare Workers. The Talk also highlights the performance benefits of running Frontend Application Bundles (FABs) on the edge and the challenges faced in achieving optimal performance.

Over the last few years, the JS web app community has seen a growing awareness and focus on performance &amp; scalability. The days when prominent production sites serve entirely-blank pages waiting on monolithic bundles of megates of JavaScript are (mostly!) behind us.A big part of that has been deeper integration with CDNs, after all, round-trip latency is one of the primary determiners of performance for a global audience. But frameworks, and the companies that support them, have different approaches to how they can be used, and the operational complexities their strategies introduce have real consequences.But what if, instead of a dynamic origin sending instructions to a static CDN, you could run your application directly on the edge? As it turns out, that doesn't just improve performance, it also vastly simplifies our deployment and maintenance lives too.

The Rise of the Dynamic Edge

Glen Maddern

En esta masterclass, demostraré cómo crear un pipeline de CI/CD para una aplicación React en AWS. Extraeremos el código fuente de GitHub y ejecutaremos pruebas contra la aplicación antes de desplegarla en un bucket de S3 para alojamiento de sitios estáticos. Luego, distribuiremos el sitio utilizando CloudFront, que apuntará al bucket de S3. Toda la infraestructura se construirá utilizando Terraform. Además, utilizaré Terragrunt para mostrar cómo crear esta configuración para múltiples entornos. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Automatizar Despliegues de Sitios React desde GitHub a S3 y CloudFront

This Talk focuses on automating React deployments to S3 and CloudFront using a CICD pipeline in AWS. It covers setting up the pipeline, sourcing code from GitHub, and configuring infrastructure with Terraform and Terragrunt. The Talk also demonstrates the process of building and deploying a React application using AWS CodeBuild and CodePipeline. Overall, it provides a comprehensive overview of the tools and techniques involved in automating React deployments in AWS.

In this talk, I will demonstrate how to create a CI/CD pipeline for a React application in AWS. We'll pull the source code from GitHub and run tests against the application before deploying it to an S3 bucket for static site hosting. The site will then be distributed using CloudFront which will point to the S3 bucket. All of the infrastructure will be built using Terraform. In addition, I'll make use of Terragrunt to show how to create this setup for multiple environments. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Automate React Site Deployments from GitHub to S3 & CloudFront

Lukonde Mwila

Las Acciones de GitHub ofrecen una solución conveniente y completa para construir pipelines de CI. Las acciones consisten en pasos componibles controlados por archivos YAML que se guardan en tu repositorio de código. Ven y aprende cómo realizar tareas que son comúnmente requeridas en bases de código Node.js modernas, como la instalación de paquetes, el linting, la ejecución de pruebas como parte de las solicitudes de extracción, la construcción de imágenes Docker y la implementación cuando el código se fusiona en la rama principal.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Acciones de GitHub para aplicaciones Node.js

GitHub Actions allow for continuous integration tasks, defined in YAML files, that can be versioned and reviewed through pull requests. Workflows can be triggered by events such as pull requests or merges, and steps can refer to external GitHub repositories. Docker containers can be built and deployed using GitHub Actions, with configuration setup and deployment defined in YAML files. Values can be used and shared between GitHub Actions, and Node.js internals can be instrumented for performance monitoring.

GitHub Actions offer a convenient, feature-rich solution for building CI pipelines. Actions consist of composable steps controlled YAML files checked into your code repo. Come learn how to perform tasks that are commonly required of modern Node.js codebases, such as package installation, linting, running tests as part of pull requests, building Docker images, and deploying when code is merged into the main branch. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

GitHub Actions for Node.js Apps

Thomas Hunter II

Panel Discussion: Mono-repo Vs. Multi-repo Vs. Hybrid

Angel Rivera

Julie Ng

Victor Savkin

La entrega de software es una prioridad para las organizaciones que poseen software, sin embargo, sigue siendo uno de los problemas más desafiantes a los que se enfrentan las empresas hoy en día. La integración continua (CI) y la entrega continua (CD) son prácticas de software que permiten a las organizaciones y equipos entregar código a los clientes de manera rápida, segura y repetida. Ya sea para mejorar el desarrollo, las operaciones o la seguridad, los pipelines de CI/CD brindan a los ingenieros y equipos más tiempo para trabajar en cosas que importan y menos tiempo luchando con el riesgo, los estándares y la velocidad de las implementaciones. Únete a esta sesión para aprender sobre los componentes de CI/CD y cómo construir y escalar pipelines para el futuro. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Cómo hacer CI/CD correctamente en 2021: Una guía para CI y CD

This talk provides an introduction to CI/CD, discussing its key components and how to succeed with it. It emphasizes the importance of speed, safety, and scaling in CI/CD, highlighting the need for unit tests, value stream management, metrics, and addressing deployment challenges. The talk also emphasizes the continuous nature of DevOps and the importance of gathering feedback and releasing changes to a subset of users.

Software delivery is a top priority for organizations that own software, yet it remains one of the most challenging problems enterprises face today. Continuous integration (CI) and continuous delivery (CD) are software practices that allow organizations and teams to deliver code to customers quickly, safely, and repeatedly. Whether it's to improve development, operations, or security, CI/CD pipelines give engineers and teams more time to work on things that matter and less time struggling with the risk, standards, and velocity of deployments. Join this session to learn about the components of CI/CD and how to build and scale pipelines for the future. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How to Get CI/CD Right in 2021: A Guide to CI and CD

Tiffany Jachja

Durante los últimos 10 años, hemos aplicado diligentemente los principios de DevOps a nuestros servicios de Backend, pero ¿qué pasa con el Frontend? ¿Podemos transferir parte de ese conocimiento entre estos mundos tan diferentes, pero a la vez muy similares? La respuesta es sí, y en esta charla te mostraré cómo los principios de DevOps nos ayudaron en DAZN a construir nuestras aplicaciones web para Smart TV y consolas de juegos. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

DevOps para Frontend: más allá de los navegadores de escritorio

Today's Talk discusses DevOps for frontend beyond desktop browsers, focusing on the challenges and journey to DevOps, the importance of abstractions, maximizing flow and enabling team autonomy, applying DevOps principles beyond web applications, running automated tests on consoles and TVs, investing in tooling for TV testing, and the challenges of TV testing in the lab.

For the past 10 years we diligently applied DevOps principles to our Backend services, but what about the Frontend? Can we transfer some of that knowledge between these very different, yet very similar, worlds? The answer is yes, and in this talk I'll show you how DevOps principles helped us at DAZN to build our web applications for Smart TV &amp; Gaming Consoles. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

DevOps for Frontend: beyond Desktop Browsers

Max Gallo

En esta sesión utilizaré una demostración en vivo para mostrar lo fácil que es agregar calidad de código y seguridad de código a tu proyecto con SonarCloud, no solo por ahora, sino para cada confirmación en el futuro.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Estás a 5 minutos de calidad de código y seguridad de código

Sonar Cloud makes it easy to set up projects for code quality and security analysis. It automatically analyzes code and provides insights into bugs, vulnerabilities, and other issues. The UI helps understand vulnerability flow across functions and files. Sonar Cloud supports multiple languages and offers rule descriptions and code samples for best practices. Overall, it simplifies code analysis and helps developers improve code quality.

In this session I'll use a live demo to show how effortless it is to add Code Quality and Code Security to your project with SonarCloud - not just for now but for every commit going forward. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

You're 5 Minutes Away from Code Quality & Code Security

G. Ann Campbell

Introducir CI/CD en tu proyecto puede ser un proceso desafiante. En GitLab valoramos la iteración como uno de nuestros valores clave, y en espíritu de la iteración estaremos encantados de compartir cómo GitLab puede ayudarte a trabajar gradualmente en llevar tu proyecto al paraíso del CI/CD. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Construye tu Pipeline de JS de forma incremental con GitLab

GitLab supports the entire DevOps cycle and uses tools like YesLint, Jest, Docker, and Kubernetes. Cache and validation are major challenges in DevOps. GitLab's auto DevOps feature simplifies Docker, Kubernetes, and Helm. Customization and advanced options are available in GitLab. GitLab's pipeline allows for optimizing job dependencies and continuous improvement. The average duration of front-end build pipelines is under 10 minutes for most people. Running a build and pipeline process in GitLab involves job calculations, runner setup, and hidden logic. GitLab can help with running front-end in Kubernetes and has a DAG visualizer. Dealing with flaky tests in the frontend is a challenge in GitLab pipelines.

Introducing CI/CD to your project might be a challenging process. In GitLab we value iteration as one of our key values, and in spirit of iteration we will be happy to share how GitLab could help you to gradually work on bringing your project to CI/CD heaven. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Build your JS Pipeline in Incremental Fashion with GitLab

Illya Klymov

En este masterclass, aprenderás cómo depurar aplicaciones Node.js y cuáles son las mejores prácticas para aumentar la capacidad de depuración de tus aplicaciones Node.js.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Depurando Aplicaciones Node.js

Today's workshop focused on debugging Node.js applications using Chrome Developer Tools, Visual Studio Code, and other techniques. The main challenges in debugging Node.js applications are the asynchronous nature of the runtime and the event loop. The workshop covered topics such as debugging with log points, performance and memory debugging, using Visual Studio Code for debugging, and various debugging tools and modules. Participants learned how to create a PostgreSQL database on Heroku, run database migration and seeding, troubleshoot and run the project, and start the debugger. They also explored using breakpoints, lock points, CPU profiling, analyzing internal events, load testing, and hunting memory leaks. The workshop emphasized the importance of efficient code debugging and provided valuable insights and techniques for debugging Node.js applications.

In this workshop, you will learn how to Debug Node.js Applications and what best practices are important to increase the debuggability of your Node.js applications. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Let's Debug Node.js Applications

Julián Duque

¡Prepárate para un recorrido por el mundo de las Arquitecturas de Software! Todos los que trabajan en software han oído hablar de términos como 'pwa', 'monolitos', 'headless' , 'microservicios' e incluso 'arquitecturas orientadas a servicios'. Todos sabemos lo que son, pero ¿cuánto sabemos realmente sobre ellos? En esta charla, te mostraremos las diferencias, las similitudes, cuándo usarlos, cuándo no usarlos, las historias de éxito y, por supuesto, los fracasos masivos. Prepárate para media hora de comedia tecnológica: ¡la arquitectura va a ser rápida y divertida! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Arquitecturas de Software Descontroladas

The Talk discusses different software architectures and their challenges. It highlights the trend of decoupling the front-end from the back-end and embracing headless architecture and Progressive Web Apps (PWA). The benefits of a service-oriented architecture (SOA) are emphasized, including flexibility, reliability, and scalability. The Talk also explores breaking down monolithic architectures into microservices and the importance of addressing pain points first. Additionally, it mentions the challenges of testing in a QA environment and the choice between microservices and monoliths depending on project goals.

Get ready for a run through the world of Software Architectures! Everyone who works in software has heard of terms like ‘pwa’, ‘monoliths’, ‘headless’ , ‘microservices’ and even ’service oriented architectures’. We all know what they are, but how much do we really know about them? In this talk, we will show you the differences, the similarities, when to use them, when not to use them, the success stories and of course: the massive failures. Get ready for a half an hour of tech-comedy: architecture is going to be fast and fun! <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Software Architectures Gone Wild

Jamie Maria Schouren

Parcel 1 fue creado a partir de la frustración de configurar empaquetadores heredados lentos y difíciles de configurar como Webpack, y a su vez inició una tendencia de herramientas de configuración cero. Desafortunadamente, Parcel 1 tenía algunos defectos de diseño importantes que llevaron a la creación de Parcel 2, una reescritura completa de Parcel que tiene como objetivo resolver esos defectos de diseño y crear un empaquetador que pueda escalar al tamaño de empresas como Atlassian y Adobe, y más allá. Un nuevo sistema de complementos, objetivos de empaquetado, configuración opcional, cachés estables, mejora del scope-hoisting, mejor experiencia de desarrollo y mejor rendimiento son solo algunas de las cosas en las que hemos estado trabajando durante los últimos 3 años. En esta charla echaré un vistazo a cómo funciona Parcel y hablaré sobre un par de las características más grandes y emocionantes de Parcel 2. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Parcel 2: el Empaquetador Automágico

Parcel 2 is a ground-up rewrite of Parcel 1, a fast and scalable zero-configuration web application bundler used by large companies like Atlassian and Adobe. It offers a zero-config approach with good defaults, making it production-ready out of the box. The new features include a revamped plugin system, a configuration file, transformers for file conversion, optimizers for code compression, target support for different browsers, diagnostics for error debugging, and named pipelines for data and JavaScript in different formats. Parcel 2 also supports different import scenarios, such as importing JSON files with named pipelines and using query parameters for image optimization. It includes various performance improvements, stable caches, optimized data structures, enhanced code splitting and bundling, improved scope hosting, and better support for monorepos and libraries. A React example is provided to showcase the simplicity of Parcel and how to use it with React.

Parcel 1 was created out of the frustration from configuring slow and hard to configure legacy bundlers like Webpack and in turn started a trend of zero-config tooling. Unfortunately, Parcel 1 had some major design flaws that led to the creation of Parcel 2, a ground-up rewrite of Parcel which aims to resolve those design flaws whilst also creating a bundler that can scale to the size of companies like Atlassian and Adobe and beyond. A new plugin system, bundler targets, optional configuration, stable caches, improved scope-hoisting, improved developer experience and better performance are just a few of the things we’ve been working on for the last 3 years. In this talk I’ll glance over how Parcel works and talk about a couple of the largest and most exciting new features in Parcel 2. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Parcel 2: the Automagical Bundler

Jasper De Moor

La CLI de npm ha sido y sigue siendo una herramienta fundamental para los desarrolladores del ecosistema de Node.js/JavaScript. El año pasado, npm@7 se convirtió en Generalmente Disponible, introduciendo una gran cantidad de cambios y nuevas capacidades, incluyendo: mejoras en el archivo de bloqueo, soporte para espacios de trabajo, instalación de dependencias pares por defecto, npm diff, npm explain, npm exec, npm set-script y mucho más. Nos sumergiremos en este trabajo y compartiremos algunas noticias emocionantes sobre lo que se espera en las próximas semanas y meses.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

¿Qué hay de nuevo en npm?

Welcome to my talk on what's new in the NPM CLI. NPMv7 introduced many new capabilities, including installing peer dependencies by default. npm v7 also introduced support for workspaces, allowing the definition of projects within your root project. The NPM team is continuously improving the CLI with weekly releases and is working on exciting features in collaboration with GitHub. NPM is not an acronym for Node Package Manager, and the CLI will continue to improve with the support of the growing team.

The npm CLI has been, &amp; continues to be, a core developer tool of the Node.js/JavaScript ecosystem. This past year npm@7 became Generally Availble, introducing with it a wealth of changes &amp; net-new capabilities including: lockfile upgrades, workspace support, installing peer dependencies default, npm diff, npm explain, npm exec, npm set-script &amp; much, much more. We'll dive into this work as well as share some exciting news about what to expect in the weeks &amp; months to come. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

What's New in npm?

Darcy Clarke

AWS ha introducido un nuevo panorama para implementar aplicaciones JavaScript utilizando Node.js alojado en AWS Lambda, y desde entonces la simplicidad de gestión que proporciona ha hecho que las aplicaciones y APIs sin servidor crezcan exponencialmente tanto en popularidad como en casos de uso. Sin embargo, operativamente, para muchos que están comenzando, solucionar problemas puede ser doloroso. Explicaré algunas técnicas para facilitar esto y proporcionaré una evolución de cómo podemos llegar a una mejor solución con consejos y herramientas que puedes utilizar en tus implementaciones sin servidor de inmediato.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Solucionar problemas con tu Node.js sin servidor no tiene por qué ser doloroso

Welcome to the DevOpsJS conference where Jeff Hopper introduces his Slack bot called LGTM ReplyGIF for posting GIFs on his behalf. He troubleshoots issues with the serverless Node code, uses CloudWatch logs and stack traces for debugging, and ships logs to Elasticsearch for analysis. Jeff explores troubleshooting options with Rollbar and discusses serverless deployment recommendations. The audience is invited to contribute to the Slack bot project, and the session concludes with thanks from Jeff.

AWS ushered in a new landscape for deploying JavaScript applications using Node.js hosted in AWS Lambda, and since then the management simplicity that it provides has made serverless applications and APIs grow exponentially in both popularity and use cases. However, operationally for many starting out, troubleshooting issues can be painful. I'll walk through some techniques to make this easier and provide an evolution of how we can get to a better solution with tips and tools you can use in your serverless deployments right away. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Troubleshooting your Serverless Node.js doesn't have to be a Pain

Jeff Hoffer

La automatización de una única aplicación monolítica es bastante sencilla. Divídela en una parte frontal y una parte trasera y aún es manejable. Agrega más componentes o infraestructura y de repente te estarás rascando la cabeza preguntándote por qué se ejecutó o no se ejecutó una compilación. ¿Cuántos pipelines necesito? ¿Cuántos repositorios de git debería tener? Vamos a revisar casos de uso desde equipos pequeños que poseen toda su pila hasta organizaciones con unidades de TI centralizadas que administran infraestructura compartida. Aprende qué escenarios y criterios determinan cómo dividir pero no convertir en espagueti tus pipelines. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Infra vs Apps: ¿Dónde están mis Pipelines?

This Talk on CICD covers various use cases, challenges, and best practices. It emphasizes the importance of people and learning in CICD, as well as the complexity of coordinating teams and managing infrastructure. The speaker shares insights on frontend development, microservices, and security considerations. The Talk concludes with discussions on Jenkins files, bash scripts, and the challenges of DevOps in organizations.

Automation of a single monolithic app is pretty straight-forward. Split it into a frontend and backend and it's still manageable. Throw in more components or infrastructure and suddenly you're scratching your head at why a build ran - or didn't run. How many pipelines do I need? How many git repos should I have? Let's walkthrough use cases from small teams who own their entire stack to organizations with central IT units that manage shared infrastructure. Learn which scenarios and criteria determine how to slice but not spaghettify your pipelines. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Infra vs Apps – Where are my Pipelines?

Kubernetes es ahora el estándar de facto para la orquestación de contenedores. A pesar de ser una de las plataformas más queridas, puede resultar intimidante al principio. ¿Por dónde empezar para implementar tus aplicaciones? En este laboratorio práctico, aprenderás sobre los componentes básicos utilizados para implementar tu aplicación en un clúster de Kubernetes. Una vez que se hayan cubierto los conceptos básicos, comprenderás cómo construir e implementar aplicaciones nativas de la nube en Kubernetes. Al final de este masterclass, estarás implementando, escalando y automatizando soluciones distribuidas basadas en JS utilizando contenedores, Kubernetes y otras herramientas populares de código abierto para la computación distribuida. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Kubernetes para Desarrolladores de JS

Today's workshop covers Kubernetes and deploying a Node.js application. It includes hands-on exercises, explanations of containers and Docker, creating pods and services, managing deployments, and using ingresses for external access. The speaker provides tips for debugging, scaling applications, and shares additional resources for learning Kubernetes.

Kubernetes is now the defacto standard for container orchestration. Despite being one of the most loved platforms out there, it can be intimidating at first. Where do you even get started to deploy your applications? In this hands-on lab, you will learn about the basic components used to deploy your application into a Kubernetes cluster. Once the basics have been covered, you will understand how to build and deploy cloud-native applications on Kubernetes. By the end of this workshop, you’ll be deploying, scaling, and automating JS-based distributed solutions using containers, Kubernetes, and other popular open-source tools for distributed computing. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Kubernetes for JS Developers

Joel Lord

Desde que JavaScript se convirtió en un lenguaje para escribir aplicaciones, las herramientas de construcción y especialmente los bundlers han estado presentes. Resuelven la discrepancia entre escribir código que sea fácil de mantener y escribir código que se cargue eficientemente en un navegador. Pero hay ventajas en el empaquetamiento del código JavaScript que van más allá del navegador, desde funciones en la nube hasta servidores y herramientas de línea de comandos. RollupJS es especial porque siempre fue diseñado desde cero para ser un bundler de propósito general en lugar de una herramienta específica para el frontend. En esta charla, veremos de qué manera otros escenarios pueden beneficiarse del empaquetamiento. Pero lo más importante, te mostraré cómo RollupJS no solo genera una salida superior en muchas situaciones, sino lo fácil que es adaptar su salida a requisitos personalizados y escenarios no estándar. Veremos cómo parchear código, simular y reemplazar dependencias, inyectar elegantemente información de construcción y controlar la generación de fragmentos al dividir el código, todo con solo unas pocas líneas de código. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Dominando tu paso de construcción - Dominando tu código

This Talk explores JavaScript code optimization using Rollup, showcasing examples of improved load times and reduced server size. It delves into Rollup customization and plugin development, demonstrating how to write plugins and remove code using hooks. The Talk also covers module code loading, advanced code control, and importing/emitting files with Rollup. Additionally, it highlights the adoption of Rollup's plugin system by other tools and introduces a self-made terminal used in the presentation.

Ever since JavaScript has become a language for writing applications, build tools and especially bundlers have been around. They solve the discrepancy between writing code that is easy to maintain and writing code that loads efficiently in a browser. But there are advantages to bundling JavaScript code that go well beyond the browser, from cloud functions to servers to command line tools. RollupJS is special in that it was always designed from the ground up to be a general purpose bundler rather than a frontend specific tool. In this talk, we will have a look in what way other scenarios can profit from bundling. But more importantly, I will show you how RollupJS not only generates superior output in many situations, but how easy it is to tailor its output to custom requirements and non-standard scenarios. We will see how to patch up code, mock and replace dependencies, elegantly inject build information and control the chunk generation when code-splitting, all with a just few lines of code. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Owning your Build-step – Owning your Code

Lukas Taegert-Atkinson

El pipeline de CI/CD se ha convertido en la norma en el desarrollo de software. Lo mismo ocurre con el linting, que es una forma básica de análisis estático. En este masterclass me gustaría demostrar cómo puedes ir más allá del simple linting y mejorar tu pipeline para proporcionar información adicional sobre tu código y permitirte entregar aplicaciones más confiables y seguras. Prerrequisitos:Familiarizado con los conceptos de CI/CD. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Haz que tu pipeline de CI/CD sea más inteligente con análisis estático

Tibor Blenici, a languages developer since 2016, will be our speaker today. To start the presentation, a poll was conducted to determine if participants use static analysis in their CI/CD pipelines. Static analysis works by analyzing the syntax and semantics of code. Control flow analysis and graphs are used to detect bugs in code. Taint analysis is a form of data flow analysis that tracks how data flows through a program. SonarQube is a free service for 15 popular languages, while SonarCloud is free for 24 languages for open source projects.

CI/CD pipeline became the norm in software development. So is linting, which is a basic form of static analysis. In this webinar I would like to demonstrate how you can go beyond simple linting and improve your pipeline to provide additional insights into your code and allow you to deliver more reliable and safe applications. Prerequisites:Familiar with CI/CD concepts. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Make your CI/CD pipeline smarter with static analysis

Tibor Blenessy

Los conceptos de Integración Continua y Entrega/Despliegue Continuo (CI/CD) son cada vez más adoptados por muchas organizaciones y equipos tecnológicos. CI/CD permite a los equipos establecer procesos que aumentan la velocidad, colaboración y calidad de su código. CI/CD permite a los equipos de desarrollo y operaciones romper silos innecesarios y obtener un conocimiento más profundo de sus respectivas áreas. En este masterclass, los participantes serán introducidos a los fundamentos básicos de la Integración Continua y Entrega/Despliegue Continuo. Los participantes aprenderán los principios fundamentales de CI/CD y tendrán la oportunidad de reforzar lo que han aprendido en un taller práctico con la plataforma CircleCI. El taller demostrará la configuración de construcción de CI/CD, confirmaciones de código, construcción de confirmaciones, pruebas de código y empaquetado. Los participantes se irán con una experiencia práctica y comprensión de lo que implica CI/CD. Tabla de contenidos- Introducción al tema de CI/CD y motivación para ello- Cómo se construyen y despliegan diferentes tipos de proyectos JavaScript (desde sitios estáticos hasta APIs)- Resumen de los pasos manuales comunes y cómo podríamos automatizarlos- Implementación de un pipeline de CI/CD desde cero- Resumen de los orbs de CircleCI- Pruebas en múltiples versiones de Node- Depuración de construcciones con SSH- Caché de dependencias- Seguridad / escaneo de vulnerabilidades- Despliegue en diferentes salidas Requisitos previos- Código y git instalados- Cuenta de GitHub <a href="https://github.com/CircleCI-Public/cicd-workshop-js" target="_blank">github.com/CircleCI-Public/cicd-workshop-js</a> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

CI/CD 101 con CircleCI

The Workshop covered the topic of CI/CD with CircleCI and included prize draws for participants. CircleCI is a platform for CI/CD that helps test JavaScript code for different browsers and provides configuration alongside the repository. The workshop covered forking repositories, setting up CircleCI, and creating real configurations. Debugging failed jobs with SSH and workflow orchestration were also discussed. Orbs were highlighted as a way to share common config sets and optimize pipelines. The workshop concluded with an assignment to interact with the CircleCI API and a prize draw for participants.

Continuous Integration and Continuous Delivery/Deployment (CI/CD) concepts are increasingly adopted many technology organizations and teams. CI/CD enables teams to establish processes that increase velocity, collaboration and quality of their codebase. CI/CD enables developer &amp; operations teams to break down unnecessary silos and gain a deeper knowledge of their respective arenas. In this workshop the participants will be introduced to the basic fundamentals of Continuous Integration and Continuous Delivery/Deployment. Participants will learn the core principles of CI/CD and have the opportunity to reinforce what they’ve learned in a hands on workshop featuring the CircleCI platform. The workshop will demonstrate CI/CD build configuration, code commits, commit builds, code testing and packaging. The participants will leave with a hands-on experience and understanding of what it takes to CI/CD. Table of contents- Introduction to the topic of CI/CD, and motivation for it- How different kinds of JavaScript projects are built and deployed (from static sites to APIs)- Overview of common manual steps &amp; how we might automate them- Implementing a CI/CD pipeline from 'scratch'- Overview of CircleCI orbs- Testing across multiple versions of Node- Debugging builds with SSH- Caching dependencies- Security / vuln scanning- Deploying to various outlets Prerequisites- Code and git installed- GitHub account <a href="https://github.com/CircleCI-Public/cicd-workshop-js" target="_blank">github.com/CircleCI-Public/cicd-workshop-js</a> <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

CI/CD 101 with CircleCI

Zan Markan

¿Cansado de conflictos de fusión y fallas del sistema después de un gran lanzamiento? ¡Las banderas de funciones pueden ser tu salvavidas! Nos esforzamos por poner nuevas funciones en manos de nuestros usuarios lo más rápido posible de manera sostenible. Algunas funciones pueden llevar más tiempo de desarrollo y afectar otras partes del sistema. Si no se manejan con cuidado, este tipo de funciones pueden resultar en conflictos de fusión que mantienen a los desarrolladores despiertos toda la noche, sin mencionar las temidas fallas del sistema después de un gran lanzamiento. Equipados con banderas de funciones, podemos evitar esta pesadilla y desplegar cambios de código de manera segura de forma continua. Esta charla consiste en consejos prácticos sobre cómo usar las banderas de funciones como interruptores de lanzamiento. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

El Arte de la Activación de Funciones

Feature flagging is an effective practice in software development to prevent unexpected impacts of code changes. Virtuflex offers a solution for continuous integration and deployment, allowing developers to serve random comics with different randomizer options. Feature flags are used to control the behavior of AI systems during development, enabling gradual deployment and automated testing. Once a feature is complete and tested, the code and flag can be safely removed.

Fed up with merge conflicts and system failures after a big release? Feature flags can be your lifesaver! We strive to get new features to the hands of our users as fast as we sustainably can. Some features can take longer to develop and touch other parts of the system. If not handled with care, these kinds of features can result in merge conflicts that keep developers up all night, not to mention the dreaded system failures following a big release. Equipped with feature flags, we can avoid this nightmare and continuously deploy code changes safely. This talk consists of practical tips on how to use feature flags as release toggles. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

The Art of Feature Flagging

Dianing Yudono

Nuestra aplicación web finalmente está lista para ser lanzada, pero ¿qué herramienta de implementación deberíamos usar? Con el auge de JAMstack, tenemos una multitud de opciones, desde Vercel, Netlify, hasta Firebase. Sin duda, el rendimiento es clave para nosotros, por lo que queremos saber cuál es el más rápido. En esta charla, haremos una prueba de rendimiento en el mundo real comparando las opciones de implementación de JAMstack más conocidas y discutiremos sus ventajas y desventajas.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Plataformas de Implementación JAM Stack y Comparación de Rendimiento

This is an introduction to the Jamstack Deploy project, which measures and tests popular cloud providers for the Jamstack architecture. The project focuses on performance and uses Checkly as a monitoring tool. The speaker plans to add more stats and tools for comparison and invites users to contribute to the project.

Our web app is finally ready to go live but which deployment tool should we use? With the rise of JAMstack, we have a multitude of options from Vercel, Netlify, to Firebase. Certainly, performance is key for us so we want to know which one is the fastest. In this talk, we will do a real-world benchmark comparing the most known JAMstack deployment options and discuss pros and cons. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

JAM Stack Deployment Platforms and Performance Comparison

Nacho Anaya

En esta sesión, mostraré contexto relevante sobre los fallos y problemas de rendimiento en mi aplicación web de JavaScript. Cubriré cómo investigar errores y señalar dónde se introduce la lentitud.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

¿Cómo está funcionando mi JavaScript?

Neil Manvar from Sentry discusses monitoring JS applications in deployed environments, focusing on error tracking and performance analysis. He explains how Sentry works, including its SDK integration and automatic error notification. The talk also covers analyzing errors and performance issues, and the benefits of integrating Sentry into applications. The summary concludes with a mention of a promotional offer for three free months of Sentry.

In this session, I’ll surface relevant context regarding crashes and performance issues in my JS-web-app. I’ll cover how to investigate errors and pinpoint where slowness is introduced. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

How is my JavaScript Doing?

Neil Manvar

¿Alguna vez has ejecutado código en CI/CD y los builds pasan solo para fallar durante la implementación? Esta presentación discutirá las ventajas de los patrones de Pruebas de Humo en los pipelines de CI/CD utilizando Infraestructura como Código (IaC). Aprende cómo los equipos pueden aprovechar la automatización para asegurarse de que las aplicaciones sean probadas en vivo en los entornos objetivo, lo cual proporciona información valiosa antes de la implementación. Angel demostrará cómo aprovechar IaC para aprovisionar infraestructura, implementar aplicaciones, probarlas y luego destruir todos los recursos creados en una sola ejecución del pipeline de CI/CD.<a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Aumentar la Confianza en la Aplicación Utilizando CI/CD e Infraestructura como Código

The Talk discusses how to increase app confidence using CICD and infrastructure as code. It explores different types of testing, including smoke tests, and the benefits of continuous deployment. Common post-deployment failure reasons are identified, and the importance of quick smoke tests is emphasized. The Talk also highlights the use of infrastructure as code to deploy and test applications, and the value of smoke testing Kubernetes deployments. The Q&A session covers the depth of smoke tests and the role of quick smoke tests in ensuring application functionality.

Ever run code in CI/CD and builds pass only to fail during deployment? This presentation will discuss the advantages of Smoke Test patterns in CI/CD pipelines using Infrastructure as Code (IaC). Learn how teams can leverage automation to ensure apps are tested live in target environments which provide valuable insights pre-deployment. Angel will demonstrate how to leverage IaC to provision infrastructure, deploy apps, test then destroy all the resources created in a single CI/CD pipeline run. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Increase App Confidence Using CI/CD and Infrastructure as Code

Dentro de ING hemos estado trabajando con JS/FE durante varios años. Comenzando desde cero, evaluamos el proceso de CI/CD para esto, pasando por múltiples etapas hasta llegar a lo que es ahora. Voy a repasar estas etapas para inspirarte a crear un proceso similar para tu propia empresa. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

El Viaje de ING en la Construcción e Implementación de Código Front-end

The Fruit Loops team at ING aims to simplify the lives of front-end engineers by introducing pipelines. They started with an Angular pipeline and then introduced a Polymer pipeline based on apps and web components. The ING web CLI and Azure DevOps were used to create pipelines that provided agility, freedom of choice, scaling, and autonomy to teams. The key takeaway is to choose the right drivers to fit your organization's needs when implementing pipelines.

Within ING we have been dealing with JS/FE for quite some years now. Starting with nothing we evaluated the CI/CD process for this, via multiple stages into what it is right now. I will go along these stages to inspire you to create a similar process for your own company. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

ING’s Journey in Building and Deploying Frond-end Code

Erik van der Voort

Desde 2017, Yarn se ha convertido en un pilar del desarrollo de JavaScript, incubando numerosas características en las que nuestro ecosistema ahora depende en gran medida. A medida que pasaron los años y los competidores mejoraron, también lo hizo Yarn, y ahora es el momento de adentrarnos en las características y compensaciones que hacen de Yarn una verdadera joya única en el ecosistema de JavaScript. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

Yarn en Profundidad: Por qué y Cómo

Yarn is not just a package manager, it intends to be a project manager with a focus on simplicity and a good developer experience. Yarn's impact on workflows and project management has been positive, improving scalability and release management. It offers features like local fixes, compressed packages, and sharing packages between projects. Yarn's infrastructure and extensive testing ensure compatibility and catch regressions. Yarn is modular, with plans for version 3 and a more powerful plugin ecosystem. The choice between npm and Yarn depends on the project's configuration.

Since 2017 Yarn proved itself a pillar of JavaScript development incubating numerous features our ecosystem now heavily relies on. As years passed, as competitors improved, so did Yarn, and it's now time today to dive into the features and tradeoffs that make Yarn a truly unique gem of the JavaScript ecosystem. <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a>

DevOps.js Conf 2021

The JavaScript DevOps Conference