Event Stores

The Syntasa platform includes a Type of Datastore called ID Store, which consists of databases and file directories for Syntasa app data storage.

Event stores serve as a useful way to organize your apps on the backend and determine where your data is stored. They also help distinguish between your development and production data. It's important to note that Event stores are only created and become active when data is stored within them. They are required for app creation, so make sure you have at least one before attempting to create an app.

 

To define an Event Store Type of Datastore you may select the Event Store Type while creating new Datastore. 

All apps require a store, either an event store or an ID store, to be specified. It is recommended to have one event store per Synthesizer app, but it is not necessary.

Most event stores will have the following three databases and three file storage directories:

  • Development (dev) - Within the development environment, the user is able to test new configurations and settings before deploying to production.
  • Production (prod) - Within the production environment live data is processed and stored.
  • Snapshot (snap) - Snapshots of configurations are stored in case a rollback to an earlier configuration is needed.

Adding a New Datastore of Event Store Type

  1. Open the DataStores page.
  2. Click the plus icon (Plus_Icon.png) to add a new Datastore. 
  3. A Datastore creation box will appear.
  4. Provide the new store with a unique name.
  5. Select Type to Event Store in the Type Filter
  6. Fill out the path and database details for each environment.
  7. It is recommended to name database values after the key and dev/prod/snap respectively, e.g. KEY_prod, or above adobe_summit_prod.
  8. Click 'Create'.
  9. A new Data Store entry will appear in the list on the screen and available to use.

Configurations

  • Name - Distinct name of the event store.
  • Key - Auto-populated from the event store name; suggested leaving as is.
  • Type - This filter defines the Datastore as per the selected Datastore Type i.e., Event Store, ID Store or Intelligence Hub 
  • Edit Paths - This checkbox gives control to edit Path and Database name,
  • Development - Location where app testing data gets written.
    • Path - File location where any resultant files are stored from processing.
    • Database - Name of the database where processed data is stored.
  • Production - Location where production data gets written.
    • Path - File location where any resultant files are stored from processing.
    • Database - Name of the database where processed data is stored.
  • Snapshot - Location where snapshots allowing for rollbacks get written.
    • Path - File location where any resultant files are stored from processing.
    • Database - Name of the database where processed data is stored.

Expected Output

An entry gets created in the Data Store screen with a Name, Created At time, and Updated At time.

You can use the Datastore Event Store Type reference with any Synthesizer, Composer, or Orchestrator template types. Once an app has been processed, the data will be available in the specified locations. If you're searching for the Datastore (Event Store Type) in its storage location, it won't appear until an app writes data to it. Creating the event store doesn't allocate storage or create a database beforehand. The database name determines where your data is stored in BigQuery and Athena.