OwlTail

Cover image of Tanmai Gopal

Tanmai Gopal Podcasts

Read more

10 of The Best Podcast Episodes for Tanmai Gopal. A collection of podcasts episodes with or about Tanmai Gopal, often where they are interviewed.

Read more

10 of The Best Podcast Episodes for Tanmai Gopal. A collection of podcasts episodes with or about Tanmai Gopal, often where they are interviewed.

Updated daily with the latest episodes

Episode artwork

Tanmai Gopal of Hasura - Instant GraphQL APIs for your data

Play
Read more

I speak with Tanmai Gopal about Hasura, an open source and hosted platform that brings instant GraphQL APIs to your data.

Also features my weekly round up of geeky news including the best game consoles ever, GPT-3, and more.

Aug 12 2020 · 49mins
Episode artwork

JSJ 401: Hasura with Tanmai Gopal

Play
Read more

Tanmai is one of the founders at Hasura. Hasura gives you instant graphQL APIs on top of a Postgres database. The eventual idea is to make data access secure and easy. Tanmai explains the challenges of doing this in the cloud. He talks about some of the difficulties with the tooling around using GraphQL and its bias towards working well with a monolith. Since GraphQL is basically a shared type system that describes your API, that means all your types need to be in the same code base. This is at odds with the folks who want to do microservices and serverless functions, because since their API is split across multiple services they have different types, and forcing these types to work together defeats the purpose of using microservices. Also, storing state across requests doesn’t work well with serverless and cloud native stuff. In short, learning to live without state is one of the general challenges with going serverless. 

This is where Hasura comes into play, and Tanmai explains how it works. Hasura is metadata driven, and each instance of the server can leverage multiple calls and exhibit a high amount of concurrency. It’s designed to be a little more CPU bound than memory bound, which means that configuring auto scaling on it is very easy and allows you to utilize the elasticity of cloud native applications. Tanmai clarifies his usage of the word ‘cloud native’, by which he means microservices. He explains that when you have a metadata based engine, this metadata has a language that allows you to bring to bring in types from multiple upstream microservices, and create a coherent graphQL API on top of that. Hasura is a middle man between the microservices and the consumer that converts multiple types into a single coherent graphQL API.

Next, Tanmai explains how Hasura handles data fetching and a high volume of requests. They also invented PostgresQL, RLS-like semantics within Hasura. He explains the process for merging your microservices into a single graphQL interface. Back on data fetching, Tanmai explains that when the product is an app, preventing an overabundance of queries becomes easier because during one of the staging processes that they have, they extract all of the queries that the app is actually making, and in the production version it only allows the queries that it has seen before. Hasura is focused on both the public interface and private use cases, though private is slightly better supported. 

Tanmai talks about the customizations available with Hasura. Hasura supports two layers. One is an aliasing layer that lets you rename tables, columns, etc as exposed by PostgresQL. The other is a computer column, so that you can add computer columns so you can extend the type that you get from a data model, and then you can point that to something that you derive. 

The panelist discusses the common conception of why it is a bad idea to expose the data models to the frontend folks directly. They discuss the trend of ‘dumbing down’ available tooling to appeal to junior developers, at the cost of making the backend more complicated. They talk about some of the issues that come from this, and the importance of tooling to solve this concern. 

Finally, Tanmai talks about the reasons to use Hasura over other products. There are 2 technologies that help with integrating arbitrary data sources. First is authorization grammar, their version of RLS that can extend to any system of types and relationships, The second is the data wrapper, part of the compiler that compiles from the graphQL metadata AST to the actual SQL AST. That is a generic interface, so anyone can come in and plug in a Haskell module that has that interface and implement a backend compiler for a native query language. This allows us to plug in other sources and stitch microservices together. The show concludes with Tanmai talking about their choice to use Haskell to make Hasura. 

Panelists

  • AJ O’Neal

  • Dan Shapir

  • Steve Edwards

  • Charles Max Wood

With special guest: Tanmai Gopal

Sponsors

Links

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

Dan Shapir:

Steve Edwards:

Charles Max Wood:

Tanmai Gopal: 

Oct 17 2019 · 1hr 10mins

Similar People

Johannes Schickling

Charles Lowell

Nader Dabit

Sean Grove

Charles Max Wood

Charlie Cheever

Gant LaBorde

Lee Byron

Taras Mankovski

Matt Hernandez

Peggy Rayzis

Mike Grabowski

Jared Palmer

Gil Tayar

Henrik Joreteg

Episode artwork

JSJ 401: Hasura with Tanmai Gopal

Play
Read more

Tanmai is one of the founders at Hasura. Hasura gives you instant graphQL APIs on top of a Postgres database. The eventual idea is to make data access secure and easy. Tanmai explains the challenges of doing this in the cloud. He talks about some of the difficulties with the tooling around using GraphQL and its bias towards working well with a monolith. Since GraphQL is basically a shared type system that describes your API, that means all your types need to be in the same code base. This is at odds with the folks who want to do microservices and serverless functions, because since their API is split across multiple services they have different types, and forcing these types to work together defeats the purpose of using microservices. Also, storing state across requests doesn’t work well with serverless and cloud native stuff. In short, learning to live without state is one of the general challenges with going serverless. 

This is where Hasura comes into play, and Tanmai explains how it works. Hasura is metadata driven, and each instance of the server can leverage multiple calls and exhibit a high amount of concurrency. It’s designed to be a little more CPU bound than memory bound, which means that configuring auto scaling on it is very easy and allows you to utilize the elasticity of cloud native applications. Tanmai clarifies his usage of the word ‘cloud native’, by which he means microservices. He explains that when you have a metadata based engine, this metadata has a language that allows you to bring to bring in types from multiple upstream microservices, and create a coherent graphQL API on top of that. Hasura is a middle man between the microservices and the consumer that converts multiple types into a single coherent graphQL API.

Next, Tanmai explains how Hasura handles data fetching and a high volume of requests. They also invented PostgresQL, RLS-like semantics within Hasura. He explains the process for merging your microservices into a single graphQL interface. Back on data fetching, Tanmai explains that when the product is an app, preventing an overabundance of queries becomes easier because during one of the staging processes that they have, they extract all of the queries that the app is actually making, and in the production version it only allows the queries that it has seen before. Hasura is focused on both the public interface and private use cases, though private is slightly better supported. 

Tanmai talks about the customizations available with Hasura. Hasura supports two layers. One is an aliasing layer that lets you rename tables, columns, etc as exposed by PostgresQL. The other is a computer column, so that you can add computer columns so you can extend the type that you get from a data model, and then you can point that to something that you derive. 

The panelist discusses the common conception of why it is a bad idea to expose the data models to the frontend folks directly. They discuss the trend of ‘dumbing down’ available tooling to appeal to junior developers, at the cost of making the backend more complicated. They talk about some of the issues that come from this, and the importance of tooling to solve this concern. 

Finally, Tanmai talks about the reasons to use Hasura over other products. There are 2 technologies that help with integrating arbitrary data sources. First is authorization grammar, their version of RLS that can extend to any system of types and relationships, The second is the data wrapper, part of the compiler that compiles from the graphQL metadata AST to the actual SQL AST. That is a generic interface, so anyone can come in and plug in a Haskell module that has that interface and implement a backend compiler for a native query language. This allows us to plug in other sources and stitch microservices together. The show concludes with Tanmai talking about their choice to use Haskell to make Hasura. 

Panelists

  • AJ O’Neal

  • Dan Shapir

  • Steve Edwards

  • Charles Max Wood

With special guest: Tanmai Gopal

Sponsors

Links

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

Dan Shapir:

Steve Edwards:

Charles Max Wood:

Tanmai Gopal: 

Oct 17 2019 · 1hr 10mins
Episode artwork

JSJ 401: Hasura with Tanmai Gopal

Play
Read more

Tanmai is one of the founders at Hasura. Hasura gives you instant graphQL APIs on top of a Postgres database. The eventual idea is to make data access secure and easy. Tanmai explains the challenges of doing this in the cloud. He talks about some of the difficulties with the tooling around using GraphQL and its bias towards working well with a monolith. Since GraphQL is basically a shared type system that describes your API, that means all your types need to be in the same code base. This is at odds with the folks who want to do microservices and serverless functions, because since their API is split across multiple services they have different types, and forcing these types to work together defeats the purpose of using microservices. Also, storing state across requests doesn’t work well with serverless and cloud native stuff. In short, learning to live without state is one of the general challenges with going serverless. 

This is where Hasura comes into play, and Tanmai explains how it works. Hasura is metadata driven, and each instance of the server can leverage multiple calls and exhibit a high amount of concurrency. It’s designed to be a little more CPU bound than memory bound, which means that configuring auto scaling on it is very easy and allows you to utilize the elasticity of cloud native applications. Tanmai clarifies his usage of the word ‘cloud native’, by which he means microservices. He explains that when you have a metadata based engine, this metadata has a language that allows you to bring to bring in types from multiple upstream microservices, and create a coherent graphQL API on top of that. Hasura is a middle man between the microservices and the consumer that converts multiple types into a single coherent graphQL API.

Next, Tanmai explains how Hasura handles data fetching and a high volume of requests. They also invented PostgresQL, RLS-like semantics within Hasura. He explains the process for merging your microservices into a single graphQL interface. Back on data fetching, Tanmai explains that when the product is an app, preventing an overabundance of queries becomes easier because during one of the staging processes that they have, they extract all of the queries that the app is actually making, and in the production version it only allows the queries that it has seen before. Hasura is focused on both the public interface and private use cases, though private is slightly better supported. 

Tanmai talks about the customizations available with Hasura. Hasura supports two layers. One is an aliasing layer that lets you rename tables, columns, etc as exposed by PostgresQL. The other is a computer column, so that you can add computer columns so you can extend the type that you get from a data model, and then you can point that to something that you derive. 

The panelist discusses the common conception of why it is a bad idea to expose the data models to the frontend folks directly. They discuss the trend of ‘dumbing down’ available tooling to appeal to junior developers, at the cost of making the backend more complicated. They talk about some of the issues that come from this, and the importance of tooling to solve this concern. 

Finally, Tanmai talks about the reasons to use Hasura over other products. There are 2 technologies that help with integrating arbitrary data sources. First is authorization grammar, their version of RLS that can extend to any system of types and relationships, The second is the data wrapper, part of the compiler that compiles from the graphQL metadata AST to the actual SQL AST. That is a generic interface, so anyone can come in and plug in a Haskell module that has that interface and implement a backend compiler for a native query language. This allows us to plug in other sources and stitch microservices together. The show concludes with Tanmai talking about their choice to use Haskell to make Hasura. 

Panelists

  • AJ O’Neal

  • Dan Shapir

  • Steve Edwards

  • Charles Max Wood

With special guest: Tanmai Gopal

Sponsors

Links

Follow DevChatTV on Facebook and Twitter

Picks

AJ O’Neal:

Dan Shapir:

Steve Edwards:

Charles Max Wood:

Tanmai Gopal: 

Oct 17 2019 · 1hr 10mins

Most Popular

Elon Musk

Barack Obama

Bill Gates

LeBron James

Mark Cuban

Michelle Obama

Melinda Gates

Arnold Schwarzenegger

Kevin Hart

Terry Crews

Mike Tyson

Episode artwork

S06E2 Modern Web Podcast - What's Up With GraphQL 2019 with Tracy Lee, Rob Ocel, Tanmai Gopal, and Uri Goldshtein

Play
Read more

In this modern web podcast, Rob Ocel and Tracy Lee speak to Tanmai Gopal and Uri Goldshtein about GraphQL.

Uri Goldshtein - Founder The Guild -@UriGoldshteinTanmai Gopal - Founder @Hasura - @tanmaigoTracy Lee - @ladyleetRob Ocel - @robocell

Topics covered:Why is GraphQL exploding in popularityWhy GraphQL isn't a fadHow to get started with GraphQLWhat are the full-stack benefits of GraphQLHow to sell GraphQL to your teamHow to migrate to GraphQLWhat happens to clients that still use your REST APIsHow does GraphQL help front-end component-based architecturesHow can GraphQL help with real-time dataHow can you get involved in the GraphQL community

Show Notes:Immutable User Interfaces (Lee Byron) - Full Stack Fest 2016https://www.youtube.com/watch?v=pLvrZPSzHxo

https://github.com/chentsulin/awesome-graphql

This episode is sponsored by NativeScript & This Dot Labs.

Feb 04 2019 · 17mins
Episode artwork

Ep. #35, GraphQL Querying with Hasura’s Tanmai Gopal

Play
Read more

In episode 35 of JAMstack Radio, Brian talks to Tanmai Gopal, CEO and Co-Founder of Hasura, about what makes GraphQL popular and how you can start using it instantly with Hasura.

The post Ep. #35, GraphQL Querying with Hasura’s Tanmai Gopal appeared first on Heavybit.

Jan 08 2019 · 26mins
Episode artwork

112 - Hasura feat. Tanmai Gopal and Rishichandra Wawhal

Play
Read more

The team from Hasura join us to talk about building GraphQL APIs for React Native applications using Hasura & why you may want to use GraphQL for a mobile application.

Dec 17 2018 · 31mins
Episode artwork

112 - Hasura feat. Tanmai Gopal and Rishichandra Wawhal

Play
Read more

The team from Hasura join us to talk about building GraphQL APIs for React Native applications using Hasura & why you may want to use GraphQL for a mobile application.

Dec 17 2018 · 31mins
Episode artwork

RRU 023: High-Performance GraphQL on Postgres with Hasura Tanmai Gopal

Play
Read more

Panel:

  • Nader Dabit
  • Sia Karamalegos

Special Guests: Tanmai Gopal

In this episode, the React Round Up panelists talk to Tanmai Gopal. Tanmai is the founder at Hasura, where they have been building a GraphQL tooling that helps accelerate being able to use GraphQL for app developers. They talk about what Hasura is and what inspired him to build it, what Haskell does to Postgres, and query variables in GraphQL. They also touch on the importance of being aware of the database, how authorization works, and more!

In particular, we dive pretty deep on:

  • Tanmai intro
  • Founder of Hasura
  • Has been building applications for about a decade
  • Focus on functional programming
  • How did you get into React?
  • Using Redux and GaphQL
  • How long has Hasura been around?
  • What inspired you to build Hasura?
  • Eliminating the middle layer
  • The elevator pitch of Hasura
  • Do you offer a database as a service?
  • Slightly different than writing your own resolvers
  • What Haskell does to Postgres
  • Query variables in GraphQL
  • Prepared statements in Postgres
  • Making queries from aps
  • GraphQL ORM for apps
  • Being aware of the database
  • How does authorization work?
  • PostGraphile, Prisma, and Hasura
  • How do PostGraphile and Prisma compare to Hasura?
  • And much, much more!

Links:

Sponsors

Picks:

Nader

Sia

Tanmai

  • Building a new tool
Aug 07 2018 · 42mins
Episode artwork

RRU 023: High-Performance GraphQL on Postgres with Hasura Tanmai Gopal

Play
Read more

Panel:

  • Nader Dabit
  • Sia Karamalegos

Special Guests: Tanmai Gopal

In this episode, the React Round Up panelists talk to Tanmai Gopal. Tanmai is the founder at Hasura, where they have been building a GraphQL tooling that helps accelerate being able to use GraphQL for app developers. They talk about what Hasura is and what inspired him to build it, what Haskell does to Postgres, and query variables in GraphQL. They also touch on the importance of being aware of the database, how authorization works, and more!

In particular, we dive pretty deep on:

  • Tanmai intro
  • Founder of Hasura
  • Has been building applications for about a decade
  • Focus on functional programming
  • How did you get into React?
  • Using Redux and GaphQL
  • How long has Hasura been around?
  • What inspired you to build Hasura?
  • Eliminating the middle layer
  • The elevator pitch of Hasura
  • Do you offer a database as a service?
  • Slightly different than writing your own resolvers
  • What Haskell does to Postgres
  • Query variables in GraphQL
  • Prepared statements in Postgres
  • Making queries from aps
  • GraphQL ORM for apps
  • Being aware of the database
  • How does authorization work?
  • PostGraphile, Prisma, and Hasura
  • How do PostGraphile and Prisma compare to Hasura?
  • And much, much more!

Links:

Sponsors

Picks:

Nader

Sia

Tanmai

  • Building a new tool
Aug 07 2018 · 42mins