How to build graph-powered applications with Node.js and Typescript
Details are as follows!
AgensGraph Webinar (1 hour session)
- Topic: Building highly scalable graph-powered applications with Node.js and Typescript
- Presenter: Jasper Blues, CEO of Liberation Data
- Date: November 5, 2019 (TUE)
- Time:
- PST : 6:00AM – 7:00AM (UTC-08)
- EST : 9:00AM – 10:00AM (UTC-05)
- UTC : 2:00PM – 3:00PM
- GMT: 2:00PM – 3:00PM (UTC 00)
- CET : 3:00PM – 4:00PM (UTC+01)
- IST : 7:30PM – 8:30PM (UTC+05:30)
- KST : 11:00PM – 12:00AM (UTC+09)
- Language: English
- Participation Link: REGISTER
Who is our speaker?
Jasper is an open-source veteran. He was a contributor to the Spring Framework, which revolutionized enterprise Java, including Spring Data Neo4j. He created Typhoon, which powers thousands of iOS applications, including Audible.com, Etihad Airlines, Singapore Airlines, and others.
He has been working with graph databases since 2016, when he built Vampr, a social network for musicians and music lovers, on behalf of a client. Vampr has grown a community of 500,000 users and expanding. It serves hundreds to thousands of transactions per second.
Jasper consults and trains internationally on graph databases topics, previously with GraphAware and now with his own company Liberation Data.
Agenda
- Introduction
- Graph Databases – the opportunities
- Node.js & Typescript – Strengths & Weaknesses
- Introducing Drivine
- Managing Connections
- Declarative Transaction Management
- Implementing Repositories
- Object Mapping
- Streaming
- Review and Q&A
What is the 7th Session about?
All around the world, companies are gaining a competitive edge by using a graph database. What was achieved by the likes of Twitter, Google, Facebook, and others through massive investment in proprietary graph technology, can now be achieved with a fractional amount of initial capital, simply by leveraging a graph database. The last decade has seen the commodification of this technology. Use-cases in social network applications, recommendation engines, fraud detection, and content management have been proven, with more being uncovered every day.
Now the pace is picking up, with Gartner predicting a graph database market size of $8 billion by 2022. If you haven’t gotten on board yet, now is the time.
Your company has teams specializing or interested in Node.js and TypeScript. But how do you build scalable, well-architected graph-powered applications that can service hundreds or thousands of transactions per second? How do you ensure such applications are built on a robust foundation, so as to keep up with rapidly evolving requirements?
Don’t miss it!
Are you interested in this event? REGISTER NOW! Thank you!
Tags: AgensGraph , Bitnine , Data , Graph , Graph Database , node.js , typescript , webinar
Leave a Reply Cancel reply
Your email address will not be published.
Notify me of follow-up comments by email.
Notify me of new posts by email.
Common questions
Do I need a graph-specific ORM to use a graph database from Node.js?
No. Official drivers such as neo4j-driver or a standard PostgreSQL client for Apache AGE return plain records, and most teams map those to typed interfaces by hand. Graph ORMs exist but add an abstraction layer that can hide the traversal cost a query actually incurs.
Can I add graph queries to an existing PostgreSQL database instead of running a separate graph database?
Yes. Apache AGE is an open-source PostgreSQL extension that adds node and edge tables plus an openCypher-style query language, queried from Node.js through a normal SQL client. It fits teams that want graph traversal without operating a second database.
Should I use Cypher or Gremlin from a TypeScript backend?
It depends on the database. Neo4j uses Cypher, Apache AGE supports an openCypher-compatible dialect, and engines like Amazon Neptune support both Gremlin and openCypher. Pick based on the database you choose first, since the query language is tied to the engine, not to Node.js or TypeScript.
Is a graph database always faster than a relational database?
No. Graph databases are faster for deep, variable-length traversals and pathfinding. For aggregate queries over large flat tables, a relational or columnar engine with proper indexing is usually faster and simpler to operate.
Sources
About this page
Last reviewed October 30, 2026 by the Nine Bits editors. Read our editorial policy or report an error.