From 31a8b530ea361d1a92c65dc99270dfc7f1a2f820 Mon Sep 17 00:00:00 2001
From: josh-wong <joshua.wong@scalar-labs.com>
Date: Thu, 6 Feb 2025 03:40:41 +0000
Subject: [PATCH] AUTO: Sync ScalarDB docs in English to docs site repo

---
 .../run-transactions-through-scalardb-cluster.mdx           | 6 ++++++
 1 file changed, 6 insertions(+)

diff --git a/versioned_docs/version-3.13/scalardb-cluster/run-transactions-through-scalardb-cluster.mdx b/versioned_docs/version-3.13/scalardb-cluster/run-transactions-through-scalardb-cluster.mdx
index eee90e5e..5166dc10 100644
--- a/versioned_docs/version-3.13/scalardb-cluster/run-transactions-through-scalardb-cluster.mdx
+++ b/versioned_docs/version-3.13/scalardb-cluster/run-transactions-through-scalardb-cluster.mdx
@@ -251,6 +251,12 @@ ScalarDB has its own data model and schema that maps to the implementation-speci
 
 You can run transactions by using a one-phase or a two-phase commit interface. Select your method for running transactions.
 
+:::note
+
+If you are building a monolithic application, you should use the one-phase commit interface. However, if you are building a microservice application, see [ScalarDB Cluster Deployment Patterns for Microservices](./deployment-patterns-for-microservices.mdx) to decide which interface to use.
+
+:::
+
 <Tabs groupId="interfaces" queryString>
   <TabItem value="Java" label="Java" default>
     <h3>One-phase commit interface</h3>