# Write path

The picture below explains what happens after a written request is directed to a specific node. Please note the proposed designs for write/read paths are primarily based on the architecture of Cassandra.

<figure><img src="https://1722711354-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FwNXdoUkfmcozr29fRrfb%2Fuploads%2FoNG0STUZRwAQNrLlL7pd%2FScreenshot%202023-11-06%20at%2001.02.34.png?alt=media&#x26;token=13e09a2a-1f0d-4c1f-b2f9-282dd427d5df" alt=""><figcaption></figcaption></figure>

1. The write request is persisted on a commit log file.
2. Data is saved in the memory cache.
3. When the memory cache is full or reaches a predefined threshold, data is flushed to SSTable on disk. Note: A sorted-string table (SSTable) is a sorted list of \<key, value> pairs. For readers interested in learning more about SStable, refer to the reference material