What you suggest then would be to pass the bytes or Any, this would not involve an extra serialization / deserialization step?
pass the bytes of the types involved to the Rust webassembly functions*
Cool, enjoy :)
Hi @otunoluwaseyi_twitter, can you explain us your usecase? Cloudstate, depending on the state model, provides you with every command you handle with the current state. With the eventsourcing state model you therefore get your state as snapshots and event " automagically".
5 replies
https://cloudstate.io/docs/concepts/eventsourced.html and https://cloudstate.io/docs/javascript/eventsourced.html are the relevant documentation.
😊
@ralphlaude I want to try running the js-shopping cart example with Postgresql. First I deploy PostgreSQL in GKE using Statefulset. Then create the statefulstore and service. the sidecar container reports error
2021-01-20 08:30:01.054 ERROR akka.actor.OneForOneStrategy - db - Connection is not available, request timed out after 5000ms.
java.sql.SQLTransientConnectionException: db - Connection is not available, request timed out after 5000ms. I guess I apply the wrong statefulstore config
@ralphlaude this is my store :
apiVersion: cloudstate.io/v1alpha1
kind: StatefulStore
metadata:
name: postgres
spec:
postgres:
host: postgres-demo.default.svc.cluster.local
credentials:
usernameKey: demopostgresadmin
passwordKey: demopostgrespwd
databaseKey: demopostgresdb
@LunaYin, you should changed the properties here (https://github.com/cloudstateio/cloudstate/blob/master/proxy/postgres/src/main/resources/application.conf) or set those properties as ENV variables for your statefulset. You have some hints here (https://github.com/cloudstateio/cloudstate/blob/master/bin/install-postgres.sh). I hope it hepls
helm install postgres bitnami/postgresql --version 9.1.4 --set persistence.enabled=false --set postgresqlUsername=cloudstate --set postgresqlPassword=cloudstate --set postgresqlDatabase=cloudstate
I also tried to modify my statefulset
template:
metadata:
labels:
app: postgres
spec:
containers:
- name: postgres
image: postgres:latest
env:
- name: POSTGRES_DATABASE
value: postgredemo
- name: POSTGRES_USERNAME
value: postgredemo
- name: POSTGRES_USERNAME
value: postgredemobut the env variables are not passed into the cloudstate sidecar, it still use "cloudstate" as user name
2 replies
based on a proxy docker image, is there a way to find out what revision of the code it is running? It seems to be '0.0.0' in cloudstate-proxy-dev-mode:latest :D
1 reply
or is that image no longer the right one to use? it doesn't seem to have been updated for the last 4 months.
@raboof:matrix.org the image is superfluous now, see link above.
I can join again if you're interested in chatting.