This is an automated email from the ASF dual-hosted git repository.
apratim pushed a commit to branch resilient-app-blog
in repository https://gitbox.apache.org/repos/asf/incubator-resilientdb-blog.git
The following commit(s) were added to refs/heads/resilient-app-blog by this
push:
new 8d297fb Update 2025-03-13-ResVault.md
8d297fb is described below
commit 8d297fbc0d41948f897e28e560ba0873153a3653
Author: Apratim Shukla <[email protected]>
AuthorDate: Fri Mar 14 00:26:03 2025 -0700
Update 2025-03-13-ResVault.md
---
_posts/2025-03-13-ResVault.md | 50 +++----------------------------------------
1 file changed, 3 insertions(+), 47 deletions(-)
diff --git a/_posts/2025-03-13-ResVault.md b/_posts/2025-03-13-ResVault.md
index 411ae3a..f62d89e 100644
--- a/_posts/2025-03-13-ResVault.md
+++ b/_posts/2025-03-13-ResVault.md
@@ -280,7 +280,7 @@ Before syncing, ensure MongoDB is running and configure
your connection settings
- Node.js Configuration (`sync.js`)
-```JavaScript
+```javascript
const { WebSocketMongoSync } = require('resilient-node-cache');
const mongoConfig = {
@@ -370,7 +370,7 @@ Once transactions are synced to MongoDB, you can query them
efficiently using th
- Node.js Query (`fetchTransactions.js`)
-```JavaScript
+```javascript
const { MongoClient } = require('mongodb');
const mongoConfig = {
@@ -416,7 +416,7 @@ const targetPublicKey =
"8LUKr81SmkdDhuBNAHfH9C8G5m6Cye2mpUggVu61USbD";
- Python Query (`fetch_transactions.py`)
-```Python
+```python
from pymongo import MongoClient
mongo_config = {
@@ -568,50 +568,6 @@ query {
}
```
----
-
-## **ResilientDB GraphQL Schema Overview**
-ResilientDB currently supports:
-
-### **Mutation: `postTransaction`**
-```graphql
-postTransaction(data: PrepareAsset!): CommitTransaction!
-```
-#### **PrepareAsset Fields:**
-| Field | Type | Description |
-|---------------------|----------|-------------|
-| operation | String! | The type of transaction (CREATE) |
-| amount | Int! | The amount associated with the transaction |
-| signerPublicKey | String! | Public key of the sender |
-| signerPrivateKey | String! | Private key for signing the transaction |
-| recipientPublicKey | String! | Public key of the recipient |
-| asset | JSONScalar! | Additional transaction data (any JSON) |
-
-#### **CommitTransaction Response Fields:**
-| Field | Type | Description |
-|-------|--------|-------------|
-| id | String! | Unique transaction ID |
-
-
-### **Query: `getTransaction`**
-```graphql
-getTransaction(id: ID!): RetrieveTransaction!
-```
-#### **RetrieveTransaction Response Fields:**
-| Field | Type | Description |
-|-----------------|----------|-------------|
-| id | String! | Transaction ID |
-| version | String! | Version of the transaction |
-| amount | String! | Transaction amount |
-| uri | String! | URI (if applicable) |
-| type | String! | Type of transaction |
-| publicKey | String! | Public key associated with the transaction |
-| operation | String! | Type of operation (CREATE) |
-| metadata | String | Optional metadata |
-| asset | JSONScalar! | Transaction asset data (any JSON) |
-| signerPublicKey | String! | Public key of the signer |
-
-
**Note:** Two transactions will have identical IDs if all the fields in the
postTransaction mutation are exactly the same. This is because ResilientDB
deterministically generates transaction IDs based on the input fields, ensuring
consistency across identical transactions.
#### **What You Can Do with ResilientDB GraphQL**
