diagrams added to Networking & Database scenarios (#484)

This commit is contained in:
Peter Turcan
2025-07-29 09:24:12 -07:00
committed by GitHub
parent 11d433c423
commit 39aa721326
4 changed files with 9 additions and 0 deletions

Binary file not shown.

After

Width:  |  Height:  |  Size: 20 KiB

Binary file not shown.

After

Width:  |  Height:  |  Size: 24 KiB

View File

@@ -823,6 +823,10 @@ User Table:
== Next Steps
In the design of a database, consider all the independent processes, and how they might access persistent memory, for example:
image::database-persistent-memory.png[]
Perhaps now consider boost:filesystem[] for file management, and for a heavier duty database engine - integrate boost:asio[] to handle remote database transactions. Referring to the xref:task-networking.adoc[] sample would be a good place to start.
The Boost libraries have a lot to offer this particular scenario!
@@ -832,3 +836,4 @@ The Boost libraries have a lot to offer this particular scenario!
* https://www.boost.org/doc/libs/latest/libs/libraries.htm#Containers[Category: Containers]
* https://www.boost.org/doc/libs/latest/libs/libraries.htm#Data[Category: Data structures]
* https://www.boost.org/doc/libs/latest/libs/libraries.htm#Memory[Category: Memory]

View File

@@ -913,6 +913,10 @@ Received: we are connected!
The samples shown here are portable and cross-platform (Windows/Linux/Mac), and the servers are asynchronous to handle multiple clients.
The following diagram shows how the different layers work together in the samples:
image::client-server-layers.png[]
== See Also
* https://www.boost.org/doc/libs/latest/libs/libraries.htm#Concurrent[Category: Concurrent Programming]