Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Demystifying DX with Node, TypeScript and Prisma

Avatar for Ryan Dsouza Ryan Dsouza
October 12, 2019

Demystifying DX with Node, TypeScript and Prisma

Creating a developer friendly Node environment with modern tooling and a strong type system to help accelerate development.

The link to the slides with GIF's and links is here: https://docs.google.com/presentation/d/1oJFYfSU6RLfM_rXCPNzxLcqc4rAAAFDklfvtkOYEpdE/edit?usp=sharing

Avatar for Ryan Dsouza

Ryan Dsouza

October 12, 2019
Tweet

Other Decks in Technology

Transcript

  1. REST Pain Points for developers - Managing multiple endpoints for

    the multiple clients(Web, Mobile, and all)
  2. REST Pain Points for developers - Managing multiple endpoints for

    the multiple clients(Web, Mobile, and all) - Navigating back and forth to your database and codebase.
  3. REST Pain Points for developers - Managing multiple endpoints for

    the multiple clients(Web, Mobile, and all) - Navigating back and forth to your database and codebase. - Getting little to no help to see the structure/schema/type of your data of your code in your code-editor.
  4. REST Pain Points for developers - Managing multiple endpoints for

    the multiple clients(Web, Mobile, and all) - Navigating back and forth to your database and codebase. - Getting little to no help to see the structure/schema/type of your data of your code in your code-editor. - Example
  5. GraphQL There’s nothing better than official site of graphql for

    its quick introduction. So here we go, https://graphql.org/
  6. GraphQL Galore! 1. Analytics: A GraphQL request is a query

    that can be tracked to see how many times it was used in a single day. You know what data is used - and deprecate what isn’t 2. Decoupling: The frontend has been liberated from the backend. Gone are the days of back-and-forth with backend teams to build the queries needed to surface data in the UI. Front-end teams can specify the exact shape of the data they get back, making them more nimble and efficient. 3. Single Endpoint: GraphQL operates from a single /graphql endpoint. No discovery issues. No separate web and mobile URLs. Reduced complexity. 4. Interactive Documentation: Documentation is always in sync with implementation. Developers using GraphiQL or Playground get “just in time” documentation for the query they are building. No more neck pain from looking at API docs on one monitor and code on the other.