Tarmac
  • Introduction
  • Functions
    • Multi-Function Services
  • Writing Functions
    • Supported Languages
    • Go
    • Rust
  • Capabilities
    • Callbacks
    • Functions
    • Logger
    • Metrics
    • Key:Value Datastore
    • SQL Datastore
    • HTTP Client
  • Running Tarmac
    • Configuration
      • BoltDB
      • Redis
      • Cassandra
    • Datastores
      • Key:Value
      • SQL
    • Logging
    • Monitoring
    • Troubleshooting Performance
  • WebAssembly Developer Resources
    • Go SDK
    • Toolkit
    • GitHub
Powered by GitBook
On this page

Was this helpful?

Export as PDF
  1. Running Tarmac
  2. Datastores

SQL

Selecting a SQL Datastore

PreviousKey:ValueNextLogging

Last updated 1 year ago

Was this helpful?

Tarmac has support for multiple SQL datastore storage systems. These datastores can change with basic configuration options within Tarmac. As a WASM Function developer, you do not need to know the underlying datastore when writing the function. Callbacks for accessing the SQL datastore are generic across all supported datastores.

To start using a SQL datastore, set the enable_sql configuration to true and specify which supported platform to use with the sqlstore_type variable.

The below table outlines the different available options.

Datastore
Type option
Description
Useful for

MySQL

mysql

MySQL a widely used, open-source RDBMS

Strong Consistency, Well Known, Persistent Storage, Scales Well

PostgreSQL

postgres

PostgreSQL a widely used, open-source RDBMS

Strong Consistency, Well Known, Persistent Storage, Scales Well

For more detailed configuration options, check out the documentation.

Configuration