Merge branch 'master' into patch-1

concepts/actors/actors_features.md

@@ -28,6 +28,7 @@ To use actors, your state store must support multi-item transactions.  This mean
 
 - Redis
 - MongoDB
+- PostgreSQL
 - SQL Server
 - Azure CosmosDB
 

concepts/state-management/README.md

@@ -49,6 +49,7 @@ The following table summarizes the capabilities of existing data store implement
 Store | Strong consistent write | Strong consistent read | ETag|
 ----|----|----|----
 Cosmos DB | Yes | Yes | Yes
+PostgreSQL | Yes | Yes | Yes
 Redis | Yes | Yes | Yes
 Redis (clustered)| Yes | No | Yes
 SQL Server | Yes | Yes | Yes
@@ -110,6 +111,7 @@ SELECT AVG(value) FROM StateTable WHERE Id LIKE '<app-id>||<thermometer>||*||tem
 * [Spec: Dapr actors specification](../../reference/api/actors_api.md)
 * [How-to: Set up Azure Cosmos DB store](../../howto/setup-state-store/setup-azure-cosmosdb.md)
 * [How-to: Query Azure Cosmos DB store](../../howto/query-state-store/query-cosmosdb-store.md)
+* [How-to: Set up PostgreSQL store](../../howto/setup-state-store/setup-postgresql.md)
 * [How-to: Set up Redis store](../../howto/setup-state-store/setup-redis.md)
 * [How-to: Query Redis store](../../howto/query-state-store/query-redis-store.md)
 * [How-to: Set up SQL Server store](../../howto/setup-state-store/setup-sqlserver.md)

howto/setup-state-store/README.md

@@ -55,6 +55,7 @@ kubectl apply -f statestore.yaml
 * [Setup Hazelcast](./setup-hazelcast.md)
 * [Setup Memcached](./setup-memcached.md)
 * [Setup MongoDB](./setup-mongodb.md)
+* [Setup PostgreSQL](./setup-postgresql.md)
 * [Setup Redis](./setup-redis.md)
 * [Setup Zookeeper](./setup-zookeeper.md)
 * [Setup Azure CosmosDB](./setup-azure-cosmosdb.md)

howto/setup-state-store/setup-postgresql.md

@@ -0,0 +1,58 @@
+# Setup PostgreSQL
+
+This article provides guidance on configuring a PostgreSQL state store.
+
+## Create a PostgreSQL Store
+Dapr can use any PostgreSQL instance. If you already have a running instance of PostgreSQL, move on to the [Create a Dapr component](#create-a-dapr-component) section.
+
+1. Run an instance of PostgreSQL. You can run a local instance of PostgreSQL in Docker CE with the following command:
+
+     This example does not describe a production configuration because it sets the password in plain text and the user name is left as the PostgreSQL default of "postgres".  
+
+     ```bash
+     docker run -p 5432:5432 -e POSTGRES_PASSWORD=example postgres
+     ```
+
+2. Create a database for state data.
+Either the default "postgres" database can be used, or create a new database for storing state data.
+
+    To create a new database in PostgreSQL, run the following SQL command:
+
+    ```SQL
+    create database dapr_test
+    ```
+
+## Create a Dapr component
+
+Create a file called `postgres.yaml`, paste the following and replace the `<CONNECTION STRING>` value with your connection string. The connection string is a standard PostgreSQL connection string. For example, `"host=localhost user=postgres password=example port=5432 connect_timeout=10 database=dapr_test"`. See the PostgreSQL [documentation on database connections](https://www.postgresql.org/docs/current/libpq-connect.html), specifically Keyword/Value Connection Strings, for information on how to define a connection string.
+
+If you want to also configure PostgreSQL to store actors, add the `actorStateStore` configuration element shown below.
+
+```yaml
+apiVersion: dapr.io/v1alpha1
+kind: Component
+metadata:
+  name: statestore
+spec:
+  type: state.postgresql
+  metadata:
+  - name: connectionString
+    value: "<CONNECTION STRING>"
+  - name: actorStateStore
+    value: "true"
+```
+The above example uses secrets as plain strings. It is recommended to use a secret store for the secrets as described [here](../../concepts/secrets/README.md).
+
+## Apply the configuration
+
+### In Kubernetes
+
+To apply the SQL Server state store to Kubernetes, use the `kubectl` CLI:
+
+```yaml
+kubectl apply -f postgres.yaml
+```
+
+### Running locally
+
+To run locally, create a `components` dir containing the YAML file and provide the path to the `dapr run` command with the flag `--components-path`.

howto/setup-state-store/supported-state-stores.md

@@ -11,6 +11,7 @@
 | Hazelcast  | :white_check_mark:  | :x: |
 | Memcached | :white_check_mark: | :x: |
 | MongoDB | :white_check_mark: | :white_check_mark: |
+| PostgreSQL | :white_check_mark:  | :white_check_mark: |
 | Redis | :white_check_mark:  | :white_check_mark: |
 | Zookeeper | :white_check_mark: | :x: |
 | Azure CosmosDB | :white_check_mark: | :white_check_mark: |

overview/README.md

@@ -35,7 +35,7 @@ Each of these building blocks is independent, meaning that you can use one, some
 | Building Block | Description |
 |----------------|-------------|
 | **[Service Invocation](../concepts/service-invocation)** | Resilient service-to-service invocation enables method calls, including retries, on remote services wherever they are located in the supported hosting environment.
-|  **[State Management](../concepts/state-management)** | With state management for storing key/value pairs, long running, highly available, stateful services can be easily written alongside stateless services in your application. The state store is pluggable and can include Azure CosmosDB, AWS DynamoDB or Redis among others.
+|  **[State Management](../concepts/state-management)** | With state management for storing key/value pairs, long running, highly available, stateful services can be easily written alongside stateless services in your application. The state store is pluggable and can include Azure CosmosDB, Azure SQL Server, PostgreSQL, AWS DynamoDB or Redis among others.
 | **[Publish and Subscribe Messaging](../concepts/publish-subscribe-messaging)** | Publishing events and subscribing to topics | tween services enables event-driven architectures to simplify horizontal scalability and make them | silient to failure. Dapr provides at least once message delivery guarantee.
 | **[Resource Bindings](../concepts/bindings)** | Resource bindings with triggers builds further on event-driven | chitectures for scale and resiliency by receiving and sending events to and from any external | source such as databases, queues, file systems, etc.
 | **[Distributed Tracing](../concepts/observability/traces.md)** | Dapr supports distributed tracing to easily diagnose and | serve inter-service calls in production using the W3C Trace Context standard.