TypeDB Blog
How we're building the future with TypeDB
The need for subtyping and polymorphism in databases
In this article, we’ll explain how a new revolution in databases overcomes the limitations of relational, document and graph databases by using subtyping and polymorphism — core object-oriented (OO) programming principles — to create higher abstractions and achieve greater expressivity.
·
Accelerating drug discovery with applied knowledge engineering and TypeDB
In this blog post, we’ll look at how TypeDB can be used to model complex biological relationships and accelerate the drug discovery processs as part of the open-source TypeDB Bio project.
·
Modeling collections in databases: Relational/SQL vs TypeDB
Databases excel at handling traditional data types such as numbers and strings, but they lack robust mechanisms for working with complex data structures like collections (e.g., lists and sets). In this blog post, we explore the difficulties encountered when storing data as collections in databases.
·
The age of AI is upon us — where are the smart databases?
What if you could ask sophisticated questions without having to tell the database how to answer them? In the same way AI-powered code generation tools can improve developer productivity, so can an AI-powered database.
·
Building a Cyber Threat Intelligence database with TypeDB
CTI (Cyber Threat Intelligence) plays a critical role in protecting sensitive data and digital assets in the ever-evolving battlefield of cybersecurity, where organizations must stay one step ahead of attackers. Organizations need strong, effective threat research databases in order to recognize and prevent attacks.
·
Inheritance and polymorphism: where the cracks in SQL begin to show
Polymorphism can be one of the most challenging things to model in a database. Not only do you want your database to be performant, you also want it to feel intuitive so that queries you write make sense and are simple to maintain, and polymorphic data can easily mess up that balance if you don’t take the time to consider how best to implement it.
·
Identity and access management with TypeDB: Part III, inference
In the last two blogs, we learned how to model polymorphic permissions and automate permission inheritance. Now, we’ll finish this blog series by explaining how to enforce policy compliance at the schema level.
·
Identity and access management with TypeDB: Part II, transitivity
Previously, we learned how to model polymorphic permissions. Here, we’ll show you how to automate permission inheritance. Finally, in the third blog, we’ll explain how to enforce policy compliance at the schema level.
·
Identity and access management with TypeDB: Part I, polymorphism
Designing an IAM platform that can support a broad variety of applications, resources and permissions and enforce sophisticated business policies, both now and in the future, is a daunting task. In this blog series, we’re going to show how TypeDB can meet these requirements with a powerful yet lean data model and intuitive query design.
·
A New Era for TypeDB
When we started building TypeDB, we saw a continuously growing complexity of data in modern applications. Modern programming languages have evolved by introducing powerful abstractions and constructs to express more complex logic — JavaScript is succeeded by TypeScript, Python by Julia, Java by Kotlin, C/C++ by Rust, and Haskell emerging as the leader of functional languages. Modern languages all have a stronger and more expressive type system.
·
Inference in TypeDB
The Wikipedia interpretation of inference is “moving from premises to logical consequences”. This definition is so broad that we can actually identify two distinct types of inference TypeDB does: Rule inference and type inference. With TypeQL, we’ve combined both types of inference into a powerful query language. This forms the basis of a paradigm-shifting database that puts elegant modelling at your fingertips.
·
