|
| 1 | +--- |
| 2 | +title: "TerminusDB: At a glance" |
| 3 | +nextjs: |
| 4 | + metadata: |
| 5 | + title: "TerminusDB: At a glance" |
| 6 | + description: "Description of the key technical features and capabilities of TerminusDB at a glance with links to the documentation" |
| 7 | + openGraph: |
| 8 | + images: https://assets.terminusdb.com/docs/technical-documentation-terminuscms-og.png |
| 9 | + alternates: |
| 10 | + canonical: https://terminusdb.org/docs/at-a-glance |
| 11 | +--- |
| 12 | + |
| 13 | +TerminusDB is a [versatile graph database](/docs/terminusdb-explanation/) for [model-based hierarchically structured records](/docs/documents-explanation/), designed as a [flexible headless content management system](/docs/document-graph-api/). |
| 14 | + |
| 15 | +It offers both [model-based JSON](/docs/schema-reference-guide/), [logical reasoning](/docs/woql-explanation/) and [RDF graphs](/docs/graphs-explanation/) in one package with [git-for-data](/docs/git-for-data-reference/) and [immutable history](/docs/graphs-explanation/) built in. |
| 16 | + |
| 17 | +Technical and linked data professionals need a solution for [complex content](/docs/python-woql-customer-data-processing-example/), [taxonomy/knowledge handling](/docs/cookbook-taxonomy-inheritance/) and [collaborative semantic infrastructure](/docs/branch-a-project/). Existing solutions don't have the comprehensive set of features required to handle complex content, taxonomyies and ontologies, nor do they provide collaborative semantic infrastructure with easy commit, roll-back and non-destructive branches for both schema and content. |
| 18 | + |
| 19 | +If you are contemplating building a rules engine or configurator in prolog, try TerminusDB! |
| 20 | + |
| 21 | +Where [logic reasoning on information models](/docs/woql-basics/) for the facts prolog becomes too complex to handle, TerminusDB offers the perfect balance as a [rules-engine for complex document-oriented graphs](/docs/path-queries-in-woql/) with a modelling environment. |
| 22 | + |
| 23 | +It is a [graph database with ACID transactions](/docs/acid-transactions-explanation/), with [full immutable history](/docs/immutability-explanation/), a [very advanced type model](/docs/schema-reference-guide/) with inheritance, [schema migration](/docs/schema-migration-reference-guide/), and [XML Datatypes for its data structures](/docs/terminuscms-data-types/), [git-for-data (including push, pull clone and branching)](/docs/git-for-data-reference/), and plays well with others using both [REST (OpenAPI Reference)](/docs/openapi/), the [WOQL datalog query language](/docs/woql-explanation/) for both read and write and a [Rust-based high performance GraphQL Engine](/docs/graphql-query-reference/). |
| 24 | + |
| 25 | +TerminusDB is an open source platform maintained by [DFRNT®](https://dfrnt.com?utm_source=terminusdb&utm_medium=referral&utm_campaign=terminusdb_docs_at_a_glance) in collaboration with the community, sitting at the convergence of content, logic and graphs. |
| 26 | + |
| 27 | +## Overview of the system |
| 28 | + |
| 29 | +* [A versatile document graph database](/docs/terminusdb-explanation/) |
| 30 | +* [flexible headless content management system](/docs/document-graph-api/) |
| 31 | + |
| 32 | +### Document graph paradigm |
| 33 | + |
| 34 | +* [model-based](/docs/schema-reference-guide/) and [structured JSON records](/docs/documents-explanation/) |
| 35 | +* [git-for-data](/docs/git-for-data-reference/) |
| 36 | +* [complex content](/docs/python-woql-customer-data-processing-example/) |
| 37 | + |
| 38 | +### ACID RDF graph database with history and branches |
| 39 | + |
| 40 | +* [RDF graph database with immutable history](/docs/graphs-explanation/) |
| 41 | +* [graph database with ACID transactions](/docs/acid-transactions-explanation/) |
| 42 | +* [full immutable history](/docs/immutability-explanation/) |
| 43 | +* [advanced type model with inheritance](/docs/schema-reference-guide/) |
| 44 | +* [taxonomies with both inherited fieldsets and values](/docs/cookbook-taxonomy-inheritance/) |
| 45 | + |
| 46 | +### RDF semantics with a Closed World Assumption (rules engine) |
| 47 | + |
| 48 | +* [collaborative semantic infrastructure](/docs/branch-a-project/) |
| 49 | +* [logic reasoning on information models](/docs/woql-basics/) |
| 50 | +* [rules-engine for complex digital twin graphs](/docs/path-queries-in-woql/) |
| 51 | + |
| 52 | +### Datalog query engine |
| 53 | + |
| 54 | +* [logical reasoning](/docs/woql-explanation/) |
| 55 | +* [immutable history](/docs/graphs-explanation/) built in |
| 56 | +* [WOQL Abstract Syntax Tree (AST)](/docs/woql-class-reference-guide/) |
| 57 | +* [how to query with WOQL](/docs/how-to-query-with-woql/) |
| 58 | +* [Javascript WOQL Client](/docs/run-woql-query/) |
| 59 | +* [Python WOQL Client](/docs/woql-query-with-python-client/) |
| 60 | + |
| 61 | +### Data model and schema management |
| 62 | + |
| 63 | +* [schema migration](/docs/schema-migration-reference-guide/) |
| 64 | +* [XML Datatypes for its data structures](/docs/terminuscms-data-types/) |
| 65 | +* [schema reference](/docs/schema-reference-guide/) |
| 66 | + |
| 67 | +### Git-for-data |
| 68 | + |
| 69 | +* [git-for-data (including push, pull clone and branching)](/docs/git-for-data-reference/) |
| 70 | + |
| 71 | +### Interoperability |
| 72 | + |
| 73 | +* [REST (OpenAPI Reference)](/docs/openapi/) |
| 74 | +* [WOQL datalog query language](/docs/woql-explanation/) |
| 75 | +* [Rust-based high performance GraphQL Engine](/docs/graphql-query-reference/) |
| 76 | +* [Javascript Client](/docs/use-the-javascript-client/) |
| 77 | +* [Python Client](/docs/use-the-python-client/) |
| 78 | + |
| 79 | +### Complete User Interface |
| 80 | + |
| 81 | +The [DFRNT Studio for TerminusDB](https://dfrnt.com/solutions-studio-demo) offers a commercially packaged solution, with hosting API tokens and collaborative environments, modelling environment and document UI that help you go from idea to prototype and production in a few hours or a few days. |
0 commit comments