Name: GraphQL Galaxy 2020
Start: 2020-11-03T03:00:00.000Z
End: 2020-11-04T16:59:59.000Z

Shivay Lamba

Lera

Lucas Estevão

Gina Chiodo

Dom Sipowicz

Gwenan Spearing

Ioannis Theodosiou

Eugene Fidelin

Liad Yosef

Costi Diaconita

Andres Pineda

Valerio Francescangeli

Lazar Djordjevic

Mehdi Mtir

Michael Paterson

Anastasiia Lysenko

Varun

Teona Mushambadze

Ángel Fernández-Paniagua

Murtaza Bagwala

Gift Egwuenu

Jorge Ossa

Michal Taszycki

Wesley Mendes

Ronak Joshi

Arkar Min Tun

davide

Diana

Matej

Elena Dumitrescu

Lukas Taegert-Atkinson

Yulia Litvinchuk

<p>En esta masterclass profundizaremos en el modelado de datos. Comenzaremos con una discusión sobre varios tipos de bases de datos y cómo se mapean a GraphQL. Una vez que se haya establecido esa base, el enfoque se desplazará a tipos específicos de bases de datos y cómo construir modelos de datos que funcionen mejor para GraphQL en varios escenarios.</p><p><br /></p><p><u>Índice de contenidos</u></p><p>Parte 1 - Hora 1</p><p>      a. Modelado de Datos de Bases de Datos Relacionales</p><p>      b. Comparando Bases de Datos Relacionales y NoSQL</p><p>      c. GraphQL con la Base de Datos en mente</p><p>Parte 2 - Hora 2</p><p>      a. Diseño de Modelos de Datos Relacionales</p><p>      b. Relación, Construcción de Tablas Multijoin</p><p>      c. Complejidades de Consulta de Modelado de Datos Relacionales y GraphQL</p><p><br /></p><p><u>Prerrequisitos</u></p><p>      a. Herramienta de modelado de datos. El formador utilizará <a href="https://dbdiagram.io/">dbdiagram</a></p><p>      b. Postgres, aunque no es necesario instalar esto localmente, ya que estaré utilizando una <a href="https://hub.docker.com/_/postgres">imagen de Dicker de Postgres</a>, de <a href="https://hub.docker.com/">Docker Hub</a> para todos los ejemplos</p><p>      c. <a href="https://hasura.io/">Hasura</a></p><p><br /></p>

Modelado de Bases de Datos Relacionales para GraphQL

This workshop covers relational modeling with GraphQL, including building a database schema, designing relationships, and using tools like dbDiagram and Hasura. It explores the concepts of relational databases, tables, and relationships, as well as the use of UUIDs and auto increments. The workshop also covers tracking foreign key relationships, setting up migrations, and optimizing queries for performance. Additionally, it discusses the capabilities of Postgres, tips for database design, and the use of schemas. Overall, the workshop provides valuable insights into relational modeling and database development with GraphQL.

<p>In this workshop we'll dig deeper into data modeling. We'll start with a discussion about various database types and how they map to GraphQL. Once that groundwork is laid out, the focus will shift to specific types of databases and how to build data models that work best for GraphQL within various scenarios.</p><p><br /></p><p><u>Table of contents</u></p><p>Part 1 - Hour 1</p><p>      a. Relational Database Data Modeling</p><p>      b. Comparing Relational and NoSQL Databases</p><p>      c. GraphQL with the Database in mind</p><p>Part 2 - Hour 2</p><p>      a. Designing Relational Data Models</p><p>      b. Relationship, Building MultijoinsTables</p><p>      c. GraphQL &amp; Relational Data Modeling Query Complexities</p><p><br /></p><p><u>Prerequisites</u></p><p>      a. Data modeling tool. The trainer will be using <a href="https://dbdiagram.io/">dbdiagram</a></p><p>      b. Postgres, albeit no need to install this locally, as I'll be using a <a href="https://hub.docker.com/_/postgres">Postgres Dicker image</a>, from <a href="https://hub.docker.com/">Docker Hub</a> for all examples</p><p>      c. <a href="https://hasura.io/">Hasura</a></p><p><br /></p>

Relational Database Modeling for GraphQL

Adron Hall

<div><div><div><div><div><p>Exploraremos cómo surgió el cliente GraphQL urql y qué lo hace destacar. Exploraremos cómo se resolvieron varios desafíos de nuevas formas desde los principios fundamentales. Espera ver características estándar futuras como el soporte sin conexión, una visión general de pequeñas opciones de diseño que están integradas en urql, y algunas características que ya son estándar y tienen soporte de primera parte, como la autenticación y la carga de archivos.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

¿Pero puede tu cliente GraphQL hacer esto? - Una inmersión profunda en urql

Urql is a GraphQL client for React, React Native, and other frameworks, with first-party support for Next.js, Preact, Svelte, and Vue. It offers flexibility and extensibility through exchanges, including dedupe, cache, and fetch exchanges. Caching, retrying, and authentication are also supported. Urql uses document caching by default but offers a graph cache for normalized caching. It has a small bundle size and a responsive community for support and collaboration.

<div><div><div><div><div><p>Let’s explore how the urql GraphQL client came to be and what makes it stand out. We will explore how various challenges were solved in new ways from first principles. Expect a look at future standard features such as Offline Support, an overview of small design choices that are baked into urql, and some features that are already standard and have first-party support such as authentication and file upload.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

But Can Your GraphQL Client Do This? — A Deep-Dive Into urql

Kadi Kraman

<p>En este masterclass, comenzaremos con un servidor Apollo completamente funcional, que llama a múltiples fuentes de datos. Gradualmente introduciremos GraphQL Mesh en ese código, viendo todos los diferentes beneficios. En cada commit, agregaremos seguridad de tipos y eliminaremos código manual hasta el último commit, donde eliminaremos todo el código manual y nos quedaremos solo con una configuración simple. De esta manera, aprenderás sobre todas las diferentes formas en las que podrías usar GraphQL Mesh y decidir dónde y cómo puede servirte mejor en tus aplicaciones existentes.</p><p><a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

De un servidor Apollo completamente funcional a GraphQL Mesh sin código con la misma funcionalidad

GraphQL Mesh is a powerful library that allows you to convert existing schemas and generate GraphQL from various sources. It provides a fully typed GraphQL experience and acts as a service mesh, handling the complexity of merging data from multiple sources. With GraphQL Mesh, you can automate API processes, replace old data sources, and create a fully functional server that can query data from multiple sources. It also offers caching capabilities, middleware integration, and the ability to connect different APIs in a single query. GraphQL Mesh can be used as an API gateway, SDK on the client, or even in non-JavaScript environments, making it a versatile tool for software development.

<p>In this workshop, we will start with a fully featured Apollo Server, that calls multiple data sources. We’ll gradually introduce GraphQL Mesh into that code, seeing all the different benefits. Commits  commit we will add type-safety and remove manual code until the last commit, where we will remove all the manual code and stay with just a simple configuration. That way you’ll learn about all the different ways you could use GraphQL Mesh and decide where and how it can best serve you in your existing applications.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

From a fully featured Apollo Server into no-code GraphQL Mesh with the same functionality

Uri Goldshtein

<div><div><div><div><div><p>Durante nuestro trabajo con muchos clientes diferentes de todas las formas y tamaños, The Guild tuvo que idear todo tipo de soluciones innovadoras para ayudar a los clientes a aprovechar al máximo GraphQL y ayudar a su adopción de manera más fácil. Durante esa charla mencionaré cómo puedes usar GraphQL en lugares donde pensabas que no era posible, compartiré herramientas de código abierto para ayudarte y proporcionaré nuevas perspectivas sobre por qué GraphQL es una gran tecnología.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL en cualquier lugar - Nuestro viaje con GraphQL Mesh y Schema Stitching

The Guild has developed various tools for GraphQL, including the GraphQL Code Generator, GraphQL Inspector, GraphQL Modules, GraphQL Tools, and GraphQL Mesh. They have joined the GraphQL Foundation and migrated GraphQLJS to TypeScript. Exciting developments in the GraphQL community include new libraries and directives, such as the GraphQL Web Socket library and the stream and defer directives. GraphQL Mesh allows for converting and merging various sources into GraphQL, providing a distributed solution. The GraphQL Hive registry allows for centralized management of schemas. The talk emphasizes a distributed and gradual approach to adopting GraphQL and the option to choose between schema stitching and Apollo Federation.

<div><div><div><div><div><p>During our work with many different clients from all shapes and sizes, The Guild had to come up with all kinds of innovative solutions to help customers achieve the most out of GraphQL and help adopt it more easily. During that talk I will mention how you could use GraphQL in places you though it wasn’t possible, share open source tools to help you and provide new perspectives about why GraphQL is a great technology.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL Anywhere - Our Journey With GraphQL Mesh and Schema Stitching

<p>GraphQL es una herramienta inmensamente poderosa y aunque hay toneladas de recursos disponibles sobre cómo aprovecharla, parece que no hay mucha discusión abierta sobre las operaciones del día 2 (mantenimiento en producción) de GraphQL. En esta charla, nos centraremos en la observabilidad y las diversas técnicas y herramientas que podemos utilizar para comprender mejor cómo se están ejecutando nuestros servicios de GraphQL en producción. Más específicamente, nos centraremos en combinar ApolloServer y OpenTelemetry.</p>

Observabilidad en GraphQL

This Talk discusses how to tool Apollo server with open tracing for observability. OpenTracing is a vendor-agnostic format that works well with distributed systems in microservices. It allows for converting GraphQL tracing data to a vendor-agnostic format and enriching information from GraphQL servers. If providers support OpenTracing, it can be easily integrated.

<p>GraphQL is an immensely powerful tool and while there are tons of resources out there on how to leverage it, there doesn't seem to be much open discussion around Day 2 (maintenance in production) operations of GraphQL. In this talk, we'll be focusing around observability and the various techniques and tools we can use to get a better understanding of how our graphQL services are running in production. More specifically we'll be focusing on combining ApolloServer and OpenTelemetry.</p>

GraphQL Observability

Ashley Narcisse

<p>Desarrollar una aplicación full-stack del mundo real a menudo implica un tedioso enhebrado de datos a través de múltiples capas del stack. Esto es particularmente indeseable durante las fases de prototipado donde el objetivo principal puede ser simplemente demostrar una idea o diseño. También es arriesgado cuando se va a producción, ya que las inconsistencias de datos entre las capas pueden provocar errores.</p><p>Nexus Schema es una biblioteca para construir APIs de GraphQL de manera code-first y type-safe, y puede ayudar enormemente con este dilema de velocidad y type-safety. En esta charla, veremos cómo construir APIs de GraphQL más rápido y con los beneficios de la type safety utilizando Nexus Schema.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Construye tus APIs de GraphQL más rápido con Nexus Schema

This Talk discusses the benefits of a code-first approach to building GraphQL APIs using Nexus Schema. It explores how the code-first approach simplifies the development process by allowing the GraphQL schema to be defined in code, providing flexibility and easy modularization. The integration of a real database with Prisma is demonstrated, showcasing the type-safe way to access the database and generate schema definition language and types as artifacts. The Talk also highlights the maturity and growth of GraphQL as a technology and the excitement it brings to the developer community.

<p>Developing a real-world full-stack app often involves tedious threading of data across multiple layers of the stack. This is particularly undesirable during prototyping phases where the main goal may be just to demonstrate an idea or design. It’s also risky when going to production since data inconsistencies between the layers can lead to bugs.</p><p>Nexus Schema is a library for building code-first, type-safe GraphQL APIs and can greatly help with this velocity and type-safety dilemma. In this talk, we'll look at how to build GraphQL APIs faster and with the benefits of type safety using Nexus Schema.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Build Your GraphQL APIs Faster with Nexus Schema

Ryan Chenkie

<p>A medida que GraphQL entra en su sexto año, hemos avanzado mucho como comunidad y ecosistema. Pero aún queda mucho trabajo por hacer para que GraphQL se vuelva completamente popular y mantenga su impulso. En esta charla, destacaré los principales desafíos técnicos y de herramientas que enfrentan los profesionales al adoptar GraphQL y espero generar nuevas ideas y discusiones sobre lo que necesitamos especificar, construir y mejorar.</p><p>Estoy emocionado de compartir una lista de oportunidades e ideas que abarcan a) las cosas aburridas que deben hacerse (por ejemplo, ¡verificación de salud y manejo de errores!), b) los problemas difíciles que deben resolverse (por ejemplo, límites de velocidad y seguridad) y c) los desafíos emocionantes (por ejemplo, GraphQL y wasm) que enfrentamos como comunidad de GraphQL.</p><p>Espero que al final de la charla tengamos una idea clara de cuáles son los principales desafíos y por qué, y que estemos entusiasmados por discutir estos desafíos y construir posibles soluciones en 2021.</p>

Lista de deseos de GraphQL 2021: Las principales oportunidades y desafíos de GraphQL para 2021

GraphQL has not yet reached mainstream adoption and there are still inflection points to cross. Fragments in GraphQL clients need improvement, and non-GraphQL approaches like SWR and Vulkane offer alternatives for automating data fetching. GraphQL clients beyond UI frameworks present challenges, but tools like the GraphQL code generator and Juke offer solutions. Using GraphQL as an intermediate representation and bridging the gap between GraphQL and REST are appealing concepts. Joining graphs and data in different use cases is a challenge, but solutions like a common GraphQL model or programmable API gateway are emerging. Unifying the entire API ecosystem may not be necessary in large enterprises, focusing on specific API endpoints can be more beneficial.

<p>As GraphQL enters its 6th year, we've come a long way as a community and an ecosystem. But there's still a lot of work to be done for GraphQL to go totally mainstream and retain its momentum. In this talk, I'll highlight the top cross-cutting technical and tooling challenges that practitioners face in getting GraphQL adopted and hope to spark new ideas and discussions around what we need to spec out, what we need to build and what need to improve!</p><p>I'm excited to share a list of opportunities and ideas that encompass a) the boring things that need to be done (eg: health-check &amp; error handling!), b) the hard problems that need to be solved (eg: rate-limiting &amp; security) and c) the exciting challenges (eg: GraphQL &amp; wasm) facing us as a GraphQL community.</p><p>I hope that at the end of the talk we have a real sense of what the top challenges are and why, and that we're excited about going into 2021 discussing these challenges and building potential solutions.</p>

GraphQL 2021 Wishlist- The top GraphQL Opportunities & Challenges for 2021

Tanmai Gopal

<div><div><div><div><div><p>Los datos son conocimiento y el conocimiento es poder. Uno de los mayores poderes que tenemos como desarrolladores es la capacidad de acceder y manipular datos en bruto con facilidad. Pero se necesita mucho contexto para saber cómo escribir una consulta SQL o usar una API o hacer una solicitud CURL. Gran parte de nuestra energía en la comunidad de GraphQL se dedica a avanzar en la especificación y mejorar las herramientas para desarrolladores, pero no dedicamos mucho tiempo a hablar de lo que GraphQL puede hacer para ayudar a las personas en nuestras organizaciones más allá de nuestros desarrolladores: nuestros diseñadores, gerentes de producto, líderes empresariales, ingenieros de éxito del cliente, etc. En esta charla, compartiré los resultados de algunas investigaciones que realizamos en Apollo sobre la accesibilidad de GraphQL y mi visión de cómo GraphQL puede conectar a los humanos con datos que les impactan de manera mucho más efectiva, dándoles la capacidad de responder sus propias preguntas.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL para Todos - Danielle Man

GraphQL can be the standard way to model and query business data, and it has the potential to go beyond just helping developers. Optimizing GraphQL queries involves mapping them to performant database queries. Translating Druid queries to GraphQL provides flexibility but has challenges with data formatting and query execution. Directives and tools like GraphQL LowDash can transform arrays of objects and provide support for applying functions to queries. Making GraphQL more accessible and integrating it into tools like Tableau can unlock its full potential.

<div><div><div><div><div><p>Data is knowledge and knowledge is power. One of the greatest powers we have as developers is the ability to access and manipulate raw data with ease. But it takes a lot of context to know how to write a SQL query or use an API or make a CURL request. A lot of our energy in the GraphQL community is spent moving the specification forward and improving developer tools around it, but we don't spend much time talking about what GraphQL can do to help people in our organizations beyond our developers –– our designers, product managers, business leaders, customer success engineers, etc. In this talk, I will share the outcomes of some research we did at Apollo on GraphQL accessibility, and my vision for how GraphQL can connect humans to data that impacts them much more effectively, there giving them an ability to answer their own questions.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL for Everyone - Danielle Man

Danielle Man

<div><div><div><div><div><p>Nuevas características en TypeScript que pueden mejorar nuestro flujo de trabajo de GraphQL.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

La próxima generación de GraphQL y TypeScript

The CTO of the Guild discusses the importance of keeping the GraphQL schema and TypeScript code in sync. They introduce GraphQL Cogen, a tool that generates TypeScript types and code to improve developer experience and type safety. The tool also generates ready-to-use React hooks based on Apollo Client and supports multiple languages and integration with various tools. They also discuss the introduction of Type Document Node, which generates a document node from GraphQL operations. They mention the new string manipulation features in TypeScript 4.1 and the ability to parse GraphQL type definitions with a lexer. They express the need for community help to overcome limitations in TypeScript with parsing complex and multiline strings.

<div><div><div><div><div><p>New features in TypeScript that can improve our GraphQL workflow.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

The Next Generation of GraphQL and TypeScript

Dotan Simha

<p>Últimamente, las cargas de trabajo de GraphQL están siendo ampliamente adoptadas en cargas de trabajo empresariales, ya que GraphQL proporciona una forma consistente y flexible para que la interfaz de usuario consuma datos de las API. Para desarrolladores de API como yo, ver cómo los servidores GraphQL abstraen el filtrado de datos y los patrones de acceso asociados con las API backend es un cambio de paradigma completo. ¿Las tareas tradicionales de diseño de API, como el modelado de datos y los patrones de acceso necesarios para implementar API de datos de alto rendimiento, siguen siendo relevantes al implementar aplicaciones GraphQL?</p><p>Esta charla te guiará a través de los aprendizajes como desarrollador de API backend al construir una aplicación GraphQL de hola mundo para implementar una API GraphQL distribuida globalmente para una aplicación de comercio electrónico del mundo real. Analizaremos la escalabilidad y la resiliencia necesarias para construir API GraphQL de alto rendimiento. También veremos cómo las capacidades de la base de datos desempeñan un papel esencial en la implementación de una aplicación GraphQL exitosa.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

De Cero a Construir Aplicaciones GraphQL Multi-Región

GraphQL is gaining rapid adoption, providing autonomy for UX developers to retrieve only the data they need. The use of GraphQL subscriptions allows for real-time updates without constant data polling. These features were evaluated in real-world use cases like e-commerce and order management systems.

<p>Off late GraphQL workloads see wide adoption in enterprise workloads as GraphQL provides a consistent and flexible way for UI to consume data from the APIs. For API developers like me, seeing GraphQL servers abstracting away the data filtering and the access patterns associated with backend APIs is a complete paradigm shift. Traditional API design tasks, like data modeling, access patterns required to implement high-performance Data APIs, are still relevant when implementing GraphQL applications?</p><p>This talk will walk you through the learnings as a backend API developer building a hello world GraphQL application to implement a globally distributed GraphQL API for a real-world e-commerce application. We will look into scaling and resiliency required for building high-performance GraphQL APIs. Also, look into how database capabilities play an essential role in implementing a successful GraphQL application.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Going from Zero to Building Multi-Region GraphQL Applications

Nikhil Chandrappa

<div><div><div><div><div><p>WordPress ha estado presente durante mucho tiempo y es el CMS más popular en la web. Sin embargo, consumir su API REST para construir sitios estáticos modernos deja mucho que desear. En esta charla, codificaremos en vivo un sitio que consume WordPress a través de GraphQL y veremos el poder de GraphQL al hacer que los servicios maduros y familiares sean fáciles de consumir.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Usando GraphQL en WordPress

WordPress, powering 30% of all websites, faces issues with overfetching and underfetching when using its REST API. WPGraphQL, a plugin for WordPress, solves this problem by using GraphQL, reducing API calls and improving scalability. By installing WPGraphQL and writing queries, developers can easily fetch data and transform it for rendering. WPGraphQL has been used by popular websites like qz.com and apollographql.com, and it recently hit 1.0. Gatsby Source WordPress is a faster version of Gatsby that works well with WPGraphQL, and Gatsby can handle building large sites. WPGraphQL does not currently support data subscriptions, but community contributions are welcome. The new Gatsby-sourced WordPress plugin offers benefits like real-time preview and incremental builds.

<div><div><div><div><div><p>WordPress has been around for a really long time and is the most popular CMS on the web. Consuming its REST API however to build modern static sites leaves a lot to be desired. In this talk, we’ll live code a site that consumes WordPress over GraphQL and see the power of GraphQL in making mature and familiar services, easy to consume.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Using GraphQL on WordPress

Sid Chatterjee

<p>Un taller práctico sobre cómo manejar la autenticación y autorización en GraphQL. Durante este taller de 3 horas, aprenderás cómo agregar autenticación a un servidor GraphQL utilizando JWTs y manejar las respuestas de las consultas con roles de usuario. Como bono, agregaremos un servidor de autenticación con Auth0.</p><p>Los contenidos:</p><ul><li>        - Autenticación con JWTs</li><li>        - Manejo de respuestas de consultas y roles de usuario</li><li>        - Auth0</li></ul><p>Prerrequisitos:</p><ul><li>        - JavaScript (preferiblemente TypeScript)</li><li>        - GraphQL</li></ul><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Autenticación del lado del servidor en GraphQL

This Workshop on GraphQL Authentication covers topics such as JSON Web Tokens (JWTs), OAuth flows, and different approaches to handling authentication in GraphQL, including resolvers, context, and schema. The use of custom directives for schema authentication is highlighted as a more complex approach. The importance of token validation and the benefits of using an authentication service like Auth0 are emphasized. The Workshop includes exercises that build upon each other, allowing participants to practice implementing authentication in GraphQL.

<p>A hands-on workshop about handling authentication and authorization in GraphQL. During this 3 hour workshop you’ll learn how to add authentication to a GraphQL server using JWTs, and handle query responses with user roles. As a bonus we’ll be adding an authentication server with Auth0.</p><p>The contents:</p><ul><li>        - Authentication with JWTs</li><li>        - Handling query responses and user roles</li><li>        - Auth0</li></ul><p>Prerequisites:</p><ul><li>        - JavaScript (preferably TypeScript)</li><li>        - GraphQL</li></ul><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Server-side Authentication in GraphQL

Roy Derks

<div><p>GraphQL originalmente no fue diseñado como un lenguaje de base de datos, pero rápidamente se está convirtiendo en una opción popular para interactuar con bases de datos. ¿Qué pasa si las bases de datos admiten nativamente GraphQL de forma predeterminada? ¿Cuáles son las ventajas de tener soporte nativo de GraphQL? ¿Cómo se maneja una consulta GraphQL detrás de escena en FaunaDB y qué garantías de base de datos ofrece este enfoque?</p></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL nativo, GraphQL como lenguaje de consulta de base de datos

The Talk introduces NativeGraphQL, which translates a GraphQL query into one FQL query, offering advantages over traditional GraphQL resolvers. The VANA approach to NativeGraphQL avoids the n plus one problem and provides several benefits. FQL is a good fit for NativeGraphQL as it solves the tree traversal problem and offers the same advantages as the rest of the native FQL language. Native GraphQL also provides multi-region scalability, ACID, and transactionality out-of-the-box.

<div><p>GraphQL was originally not designed as a database language yet it's quickly becoming a popular choice to interact with databases. What if databases natively support GraphQL  default? What are the advantages of native GraphQL support? How is a GraphQL query handled behind the scenes in FaunaDB and what database guarantees does such an approach provide?</p></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Native GraphQL, GraphQL as a Database Query Language

Brecht De Rooms

Introduction to GraphQL at Scale panel and the various aspects of scalability in technology, product, and team dimensions. Discussion on the impact of GraphQL on scalability and the introduction of top minds in GraphQL for scaling solutions. Importance of GraphQL in scaling technology efficiently and addressing common challenges in large-scale projects. Significance of GraphQL in enabling efficient scaling and formalizing interactions for technology teams to address common challenges. Discussion on the organizational scale aspect of GraphQL and its appeal for metadata management in enterprise contexts. Critical integration of GraphQL within existing abstractions at Facebook and fostering relationships between different types of engineers for successful scaling. Flexibility and power of GraphQL in abstractly defining data models and structuring GraphQL for varied use cases. Importance of Federation in scaling GraphQL graphs by defining entities and optimizing approaches for varied use cases. Challenges in aligning enterprise APIs with a unified graph and balancing interrelated microservices in GraphQL implementations. Proposal for 'GraphQL Lite' to simplify the spec for platform-centric use cases and challenges with error handling in GraphQL, along with innovative approaches in GraphQL directives. Expressing gratitude for the engaging conversation and shared wisdom during the panel.

GraphQL at Scale - Panel Discussion

Nick Schrock

Dan Schafer

Taz Singh

<div><p>Si tienes APIs de GraphQL existentes o planeas construirlas en el futuro, únete a nosotros para una sesión de 5 minutos en la que te mostraremos cómo asegurarlas rápidamente utilizando Tyk.</p></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Asegura tus puntos finales de GraphQL con Tyk en 5 minutos

This lightning talk explores how to secure GraphQL endpoints using Tyke, addressing problems such as authorization, schema security, and protection against denial of service attacks. Tyke provides comprehensive security features without the need for additional plugins. It supports various authentication modes, rate limiting, throttling, and query depth limiting. The demonstration shows how Tyke and GraphQL can easily secure APIs by adding authorization headers, restricting access to specific fields, and enforcing query depth limits.

<div><p>If you have existing GraphQL APIs or plan on building them in the future, join us for a 5-minute session to show you how to quickly secure them using Tyk.</p></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Secure Your GraphQL Endpoints With Tyk in 5 Minutes

Matt Tanner

<div><div><div><div><div><p>Las aplicaciones son lo suficientemente difíciles de construir sin tener que preocuparse por capas y capas que se encuentran entre sus usuarios y la base de datos. En esta charla examinamos las tendencias en la computación sin servidor y su impacto en las bases de datos modernas y las capas de API.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

La Capa API en Disminución

The Talk discusses the evolution of code and data coupling, the challenges of managing code and API complexity, and the rise of GraphQL as a solution. It explores the power of directives in GraphQL and their ability to preprocess and post-process requests and responses. The at lambda directive is highlighted as a way to implement fields in JavaScript. The Talk also touches on the benefits of working from home and the flexibility of placing directives in various parts of a GraphQL schema.

<div><div><div><div><div><p>Apps are hard enough to build without having to worry about layers and layers that sit between your users and the database. In this talk we examine trends in serverless computing, and their impact on modern databases and API layers.</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

The Diminishing API Layer

Tejas Dinkar

<p>Uno de los beneficios de GraphQL es que permite un único punto de entrada a cualquier número de servicios o bases de datos backend. Cada vez más empresas están adoptando tecnologías en la nube, lo que lleva a más empleos, más dinero y más oportunidades en la computación en la nube. Cuando GraphQL se integra con un backend en la nube, permitiendo un acceso seguro y directo a docenas de bases de datos y servicios administrados, las limitaciones son infinitas. El problema a menudo radica en construir estas implementaciones desde cero y hacerlo correctamente. En esta charla, mostraré cómo puedes construir backends GraphQL basados en la nube que se conecten a múltiples bases de datos (SQL y NoSQL), funciones sin servidor, servicios de aprendizaje automático y microservicios utilizando TypeScript, AppSync y AWS CDK, y hacerlo con menos líneas de código de las que esperarías. También veremos cómo se manejan las suscripciones, la seguridad, el almacenamiento en caché y la autenticación, lo que te permitirá construir APIs que puedan conectarse simultáneamente a decenas de millones de clientes a la vez para ofrecer aplicaciones en tiempo real a gran escala. Al final de la charla, deberías sentirte cómodo sabiendo que puedes convertirte en un ingeniero en la nube utilizando tus habilidades existentes en GraphQL.</p><p><a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Construyendo una Puerta de Enlace de API en la Nube Altamente Escalable

This Talk discusses building a highly scalable cloud API gateway with GraphQL using AWS AppSync. It covers the challenges of scalability, developer velocity, and cost in building APIs. The Talk provides a step-by-step guide on building a cloud API gateway using CDK and AppSync, including defining the schema, configuring data sources and permissions, creating resolvers, and deploying the API. It also highlights the flexibility and trade-offs of using AWS AppSync, testing GraphQL Lambdas, and the portability of the solution. The learning curve of AppSync has improved over time, and future updates are planned to further simplify the process.

<p>One of the benefits of GraphQL is that it enables a single entry point into any number of back end service or databases. More and more companies are adopting cloud technologies – leading to more jobs, more money, and more opportunities in cloud computing. When GraphQL is integrated with a cloud back end, enabling secure and direct access to dozens of databases and managed services, the limitations are endless. The problem is often that building out these implementations from scratch, and getting them right, is hard. In this talk, I’ll show how you can build cloud-based GraphQL back ends connecting to multiple databases (SQL and NoSQL), serverless functions, machine learning services, and microservices using TypeScript, AppSync, and AWS CDK – and do so in fewer lines of code than you’d expect. We’ll also look at how subscriptions, security, caching, and authentication are all handled, enabling you to build APIs that can simultaneously connect to tens of millions of clients at once to offer true real-time applications at scale. By the end of the talk, you should feel comfortable knowing that you can become a cloud engineer using an existing GraphQL skillset.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Building a Highly Scalable Cloud API Gateway

Nader Dabit

<p>Como con cualquier elección tecnológica, elegir GraphQL como estilo de API implica compromisos. Algunos nos dicen que GraphQL está aquí para reemplazar todo lo demás, otros nos dicen que usar GraphQL es un error. En esta charla, exploraremos por qué ambas cosas son falsas y cómo todo depende del contexto.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Depende: Examinando los mitos y suposiciones de GraphQL

Today's talk explores the nuances of GraphQL and how its effectiveness depends on the context. Caching is a polarizing subject in GraphQL, but there are tools available for caching. The trade-off for client-side flexibility in GraphQL affects performance predictability. GraphQL as a backend for frontend offers flexibility but limits true decoupling. It's important to consider the context and trade-offs when deciding whether to use GraphQL or REST. The speaker emphasizes the need for better conversations and understanding the nuances of GraphQL.

<p>As with any technology choice, choosing GraphQL as an API style involves tradeoffs. Some tell us GraphQL is here to replace everything else, others tell us using GraphQL is a mistake. In this talk, we'll explore why both these things are false, and how everything is context dependent.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

It Depends — Examining GraphQL Myths and Assumptions

Marc-André Giroux

An exciting panel on using GraphQL, focusing on durability of GraphQL APIs at scale. Introductions from GitHub, Apollo, and Netflix representatives. Diverse perspectives from top GraphQL-consuming companies. Discussion on the importance of testing GraphQL APIs for reliability and smooth operation, including unit testing, integration testing, and observability. Strategies for handling failures, enhancing resilience, and managing traffic spikes in GraphQL systems. Insights on caching strategies, innovative techniques, and error handling as data. Recommendations for building reliable APIs and leveraging resources like Site Reliability Engineering and domain-driven design.

<div><div><div><div><div><p>Kurt Kemple, Marc-André Giroux, Mandi Wise, Tejas Shikhare</p></div></div></div></div></div><div><div><div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Panel Discussion by Apollo Team: GraphQL Durability

Kurtis Kemple

Mandi Wise

Tejas Shikhare

<p>GraphQL es un lenguaje de consulta para APIs, pero ¿qué pasa si tu API no admite GraphQL? Hay mucha información sobre cómo puedes usar GraphQL para que tus APIs sean más legibles o incluso más contenido sobre cómo usar GraphQL como una capa de datos para tus APIs existentes. Todo esto tiene mucho sentido, pero ¿qué pasa si realmente quieres saber cómo transformar servicios existentes a GraphQL? En esta charla demostraré cómo puedes usar tus servicios existentes para crear esquemas de GraphQL utilizando Árboles de Sintaxis Abstracta y TypeScript.</p><p>Esta no es una charla para mostrar cómo envolver servicios con GraphQL, en esta charla mostraré modelos de datos para usar un AST para transformar servicios existentes a GraphQL. También se mostrarán patrones de pensamiento y enfoques de clase.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Hablemos de GraphQL con tus servicios

This talk explores the use cases for GraphQL with existing services and legacy code, focusing on an e-commerce platform. It discusses the challenges of using REST and the benefits of using GraphQL. The talk covers different approaches to implementing GraphQL with existing services, such as using libraries like GraphQL Mesh or creating a custom data layer. It also discusses the importance of mapping data specifications to a GraphQL schema and creating resolvers. The talk concludes by highlighting the benefits of using GraphQL for client-facing applications.

<p>GraphQL is a query language for APIs, but what if your API doesn't support GraphQL? There's a lot of information on how you can use GraphQL to make your APIs more readable or even more content on using GraphQL as a data layer for your existing APIs. This all makes perfect sense, but what if you actually want to know how to transform existing services to GraphQL? In this talk I'll demonstrate how you can use your existing services to create GraphQL schemas using Abstract Syntax Trees and TypeScript.</p><p>This is not a talk to show how to wrap services with GraphQL, in this talk I'll show data models to use an AST to transform existing services to GraphQL. Also, thinking patterns and best class approaches will be shown.</p><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Let's Talk GraphQL With Your Services

Lighting Talks - Day 1 - GraphQL Galaxy 2020

Ryan Severns

Lighting Talks - Day 2 - GraphQL

Alex Loberham introducing the topic of GraphQL and the JAMstack and inviting panelists to introduce themselves. Exploring the compatibility between GraphQL and Jamstack in enhancing performance and data retrieval efficiency. Discussing the benefits of using GraphQL with Jamstack for efficiency and unified data consumption. Discussing the benefits of GraphQL in connecting platforms and reducing application code complexity. Discussing the tradeoff between simplicity and time in adopting GraphQL, emphasizing the benefits of self-documentation and efficiency in data consumption. Discussing the benefits of GraphQL for self-documentation, efficient data consumption, and the differentiation of Gatsby from other static site generators. CMS considerations for supporting GraphQL and the balance between speed and data structure in Jamstack frameworks. Exploring the role of GraphQL clients in optimizing data delivery. Exploring the role of GraphQL in JAMstack sites, distinguishing between build time and runtime usage. Discussing recommendations for GraphQL users interested in exploring Jamstack, emphasizing Gatsby as an easy starting point for building a Jamstack site with GraphQL support. Discussing preferences for tools in Jamstack development, favoring Next.js for its full-stack framework capabilities and Gatsby for static sites with GraphQL support. Exploring resources for learning GraphQL, highlighting HowtographQL as a valuable resource. Emphasizing the importance of hands-on learning with GraphQL by building projects.

GraphQL + JAMStack - Panel Discussion

Alex Lobera

Scott Moss

<div><div><div><div><div><p>Con StackHawk, los equipos de ingeniería pueden realizar pruebas de seguridad en aplicaciones respaldadas por GraphQL para encontrar y solucionar vulnerabilidades antes de que lleguen a producción. Con pruebas automatizadas en cada PR, puedes estar seguro de que tu API de GraphQL es segura. Únete a Ryan Severns, cofundador de StackHawk, para obtener una breve descripción general de la seguridad de GraphQL con StackHawk.</p></div></div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

Pruebas de seguridad para aplicaciones respaldadas por GraphQL

I'm Ryan Severns, COO of StackHawk, an application security testing tool that focuses on GraphQL. StackHawk offers active automated testing of GraphQL endpoints to find potential security vulnerabilities. The tool integrates with developer tools like Slack and Jira for easy vulnerability management and bug fixing. It provides detailed information, including request, response, and curl command, for debugging. StackHawk offers free single user accounts and team trials, and visitors can find more information at their booth in GraphQL Galaxy.

<div><div><div><div><div><p>With StackHawk, engineering teams can run security tests against GraphQL backed applications to find and fix vulnerabilities before they hit production. With automated testing on every PR, you can be confident that your GraphQL API is secure. Join StackHawk co-founder Ryan Severns for a quick overview of GraphQL security with StackHawk.</p></div></div></div></div></div><p>  <a href="https://www.froala.com/wysiwyg-editor?pb=1"> </a></p>

GraphQL Galaxy 2020

The biggest GraphQL conference in the cloud