<?xml version="1.0" encoding="UTF-8"?>
<?xml-stylesheet href="/feed.rss.xml" type="text/xsl" media="screen"?>
<rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:media="http://search.yahoo.com/mrss/" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>Rakesh Menon</title>
    <description/>
    <link>https://speakerdeck.com/rakeshmenon</link>
    <atom:link rel="self" type="application/rss+xml" href="https://speakerdeck.com/rakeshmenon.rss"/>
    <lastBuildDate>2017-09-20 00:24:41 -0400</lastBuildDate>
    <item>
      <title>DDA with GraphQL and React</title>
      <description>Modern web applications rely heavily on the REST API backends. Monoliths are being further broken down into individual microservices to speed up development &amp; deployment, to make frequent releases hassle free.

With the number of client devices accessing the API services increasing exponentially, we run into issues such as each client requesting for new changes and API teams getting into what we call the “version hell” and maintenance nightmares.

Clients, in most of the cases, need to invoke multiple APIs and join resources for different use-cases and soon we run into issues of under/over delivering data in most of the cases. We have traditionally solved this problem with orchestration layers, designed to deliver exactly the data required for the view.

But can we do better? Yes, and the answer to that is Demand Driven Architecture!

Who uses it? Facebook, Netflix and others!

Topics we explore:

1. Need for Demand driven architecture.
2. Principles of demand driven architecture
3. Introduction to GraphQL and core concepts
4. Architecting your application – example using React &amp; GraphQL
5. Libraries involved to help make this happen!</description>
      <media:content url="https://files.speakerdeck.com/presentations/22b0cf1e2da9485c9c4b4ff63d914f3b/preview_slide_0.jpg?8595341" type="image/jpeg" medium="image"/>
      <content:encoded>Modern web applications rely heavily on the REST API backends. Monoliths are being further broken down into individual microservices to speed up development &amp; deployment, to make frequent releases hassle free.

With the number of client devices accessing the API services increasing exponentially, we run into issues such as each client requesting for new changes and API teams getting into what we call the “version hell” and maintenance nightmares.

Clients, in most of the cases, need to invoke multiple APIs and join resources for different use-cases and soon we run into issues of under/over delivering data in most of the cases. We have traditionally solved this problem with orchestration layers, designed to deliver exactly the data required for the view.

But can we do better? Yes, and the answer to that is Demand Driven Architecture!

Who uses it? Facebook, Netflix and others!

Topics we explore:

1. Need for Demand driven architecture.
2. Principles of demand driven architecture
3. Introduction to GraphQL and core concepts
4. Architecting your application – example using React &amp; GraphQL
5. Libraries involved to help make this happen!</content:encoded>
      <pubDate>Sat, 09 Sep 2017 00:00:00 -0400</pubDate>
      <link>https://speakerdeck.com/rakeshmenon/dda-with-graphql-and-react</link>
      <guid>https://speakerdeck.com/rakeshmenon/dda-with-graphql-and-react</guid>
    </item>
  </channel>
</rss>
