This repository has been archived by the owner on Mar 16, 2022. It is now read-only.
-
Notifications
You must be signed in to change notification settings - Fork 97
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
4 changed files
with
41 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,26 @@ | ||
# Deployment spec for a journal. A journal is a logical abstraction over a database | ||
# deployment, and captures how to deploy and connect to that database. Multiple | ||
# StatefulServices's would use a single journal. | ||
apiVersion: cloudstate.io/v1alpha1 | ||
kind: Journal | ||
metadata: | ||
name: cassandra | ||
spec: | ||
|
||
# The type of Journal - valid values would come from an enum of supported databases. | ||
type: Cassandra | ||
|
||
# The deployment type, ie, how this Journal is deployed. Valid values would depend on | ||
# the Journal type, but all types would support "Unmanaged", which indicates that the | ||
# operator doesn't manage/deploy the database itself, ie, the user has to deploy | ||
# the database themselves. For Cassandra, future supported values might include | ||
# "GoogleCloudMarketplace", which would deploy Cassandra using Google's Application | ||
# CRD, or "InstaclustrOperator", which would deploy Cassandra using Instaclustr's | ||
# Cassandra operator. | ||
deployment: Unmanaged | ||
|
||
# Type and deployment specific configuration for the journal. | ||
config: | ||
|
||
# The name of the unmanaged Cassandra service to connect to. | ||
service: cassandra-cassandra-0.cassandra-cassandra-svc.cassandra.svc.cluster.local |
4 changes: 2 additions & 2 deletions
4
samples/js-shopping-cart/journal.yaml → ...s/js-shopping-cart/journal-in-memory.yaml
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,13 +1,13 @@ | ||
# Deployment spec for a journal. A journal is a logical abstraction over a database | ||
# deployment, and captures how to deploy and connect to that database. Multiple | ||
# EventSourcedFunction's would use a single journal. | ||
# StatefulService's would use a single journal. | ||
apiVersion: cloudstate.io/v1alpha1 | ||
kind: Journal | ||
metadata: | ||
name: inmemory | ||
spec: | ||
|
||
# The type of Journal - valid values would come from an enum of supported databases. | ||
# Currently, Cassandra is the only supported database. | ||
# This is the InMemory journal, which obviously should not be used in production. | ||
type: InMemory | ||
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters