Skip to content

Commit a2e144c

Browse files
Integrated latest changes at 08-23-2024 10:30:07 AM
1 parent c11501c commit a2e144c

File tree

1 file changed

+7
-9
lines changed
  • ej2-javascript/document-editor/collaborative-editing

1 file changed

+7
-9
lines changed

ej2-javascript/document-editor/collaborative-editing/overview.md

Lines changed: 7 additions & 9 deletions
Original file line numberDiff line numberDiff line change
@@ -9,7 +9,7 @@ documentation: ug
99
domainurl: ##DomainURL##
1010
---
1111

12-
# Collaborative editing
12+
# Collaborative Editing
1313

1414
Allows multiple users to work on the same document simultaneously. This can be done in real-time, so that collaborators can see the changes as they are made. Collaborative editing can be a great way to improve efficiency, as it allows team members to work together on a document without having to wait for others to finish their changes.
1515

@@ -27,20 +27,18 @@ Allows multiple users to work on the same document simultaneously. This can be d
2727

2828
To support collaborative editing, it's crucial to have a backing system that temporarily stores the editing operations of all active users. There are two primary options:
2929

30-
- *Distributed Cache*: Handles a higher number of `HTTP` requests per second compared to a database approach. For instance, a server with 2 vCPUs and 8GB RAM can handle up to 125 requests per second using a distributed cache.
31-
- *Database*: With the same server configuration, it can handle up to 50 requests per second.
30+
- ***Distributed Cache***: Handles more HTTP requests per second than a database approach. For example, a server with 2 vCPUs and 8GB RAM can process up to 125 requests per second using a distributed cache. We highly recommend using a distributed cache as a backing system over a database.
3231

33-
Using the distributed cache or database all the editing operations are queued in order and conflict resolution is performed using `Operational Transformation` Algorithm.
32+
- ***Database***: With the same server configuration, it can handle up to 50 requests per second.
3433

35-
> *Recommendation* - If you expect average `http` requests per second of your live application as 50 or below, then the database can provide reliable a backing system for operation queue. If you expect average requests per second of your live application as above 50, then the distributed cache is highly recommended backing system.
34+
Using the distributed cache or database all the editing operations are queued in order and conflict resolution is performed using `Operational Transformation` algorithm.
3635

37-
> Tips to calculate the average requests per second of your application:
38-
Assume the editor in your live application is actively used by 1000 users and each user's edit can trigger 2 to 5 requests per second. The total requests per second of your applications will be around 2000 to 5000. In this case, you can finalize a configuration to support around 5000 average requests per second.
36+
>**Tips**: To calculate the average requests per second of your application Assume the editor in your live application is actively used by 1000 users and each user’s edit can trigger 2 to 5 requests per second. The total requests per second of your applications will be around 2000 to 5000. In this case, you can finalize a configuration to support around 5000 average requests per second.
3937
40-
> Note: The above metrics are based solely on the collaborative editing module. Actual throughput may decrease depending on other server-side interactions, such as document importing, pasting formatted content, editing restrictions, and spell checking. Therefore, it is advisable to monitor your app's traffic and choose a configuration that best suits your needs.
38+
>**Note**: The above metrics are based solely on the collaborative editing module. Actual throughput may decrease depending on other server-side interactions, such as document importing, pasting formatted content, editing restrictions, and spell checking. Therefore, it is advisable to monitor your apps traffic and choose a configuration that best suits your needs.
4139
4240
#### See Also
4341

4442
- [Collaborative editing using Redis cache in ASP.NET Core](../../document-editor/collaborative-editing/using-distributed-cache-asp-net-core)
4543
- [Collaborative editing using Microsoft SQL server in ASP.NET Core](../../document-editor/collaborative-editing/using-database-in-asp-net-core)
46-
- [Collaborative editing using Java](../../document-editor/collaborative-editing/using-java)
44+
- [Collaborative editing using Java](../../document-editor/collaborative-editing/using-java)

0 commit comments

Comments
 (0)