JSFoo 2019

Annual conference of 800+ front-end, backend and fullstack engineers

Participate micPropose a session

Not everything can fit in rows and columns

Submitted by Ashok Vishwakarma (@ashokvishwakarma) on Tuesday, 9 April 2019

videocam_off
Section: Full talk (40 mins) Technical level: Intermediate

Vote on this proposal

Login to vote

Total votes:  +15

Abstract

The Graph Database is there since a long time but very restricted adaption rate and there are some rumours about where it fits. The way the web is moving forward data is becoming more unstructured which are very hard to fit in row and columns. We have adapted NoSQL databases which pose several challenges when it comes to relationships. The dgraph team is trying to fill the gaps and minimize the time required to get started with the Graph Database.

Outline

I have created a JavaScript ORM (for NodeJS) for dgraph, similar to the ones we are familiar (mongoose, sequilize). The talk will have the following contents

Database problems.
Introduction to Dgraph and its basics.
dgraph-orm and how to use it.

Requirements

NA

Speaker bio

GDE - Web Technologies & Angular | AVP-Engineering, Naukri.com | Ex. PayTM, PayU | 13+ yrs of Experience

Links

Slides

https://speakerdeck.com/avishwakarma/not-everything-can-fit-in-rows-and-columns

Comments

  • 1
    Abhishek Balaji (@booleanbalaji) Reviewer 8 days ago

    Hi Ashok,

    Thank you for submitting a proposal and for adding the slides. Please add a preview video asap talking about what you intend to cover in your talk as well as the intended audience. Additionally do update your slides to make sure your slides must cover the following:

    • Problem statement/context, which the audience can relate to and understand. The problem statement has to be a problem (based on this context) that can be generalized for all.
    • What were the tools/frameworks available in the market to solve this problem? How did you evaluate these, and what metrics did you use for the evaluation? Why did you pick the option that you did?
    • Explain how the situation was before the solution you picked/built and how it changed after implementing the solution you picked and built? Show before-after scenario comparisons & metrics.
    • What compromises/trade-offs did you have to make in this process?
    • What is the one takeaway that you want participants to go back with at the end of this talk? What is it that participants should learn/be cautious about when solving similar problems?

    We need your updated slides and preview video by 28 May to evaluate your proposal. If we do not receive an update, we’d be moving your proposal for evaluation under a future event.

Login with Twitter or Google to leave a comment