|
@@ -90,7 +90,11 @@ Architecture
|
|
|
* A [Node.js](/result) or [ASP.NET Core SignalR](/result/dotnet) webapp which shows the results of the voting in real time
|
|
* A [Node.js](/result) or [ASP.NET Core SignalR](/result/dotnet) webapp which shows the results of the voting in real time
|
|
|
|
|
|
|
|
|
|
|
|
|
-Note
|
|
|
|
|
-----
|
|
|
|
|
|
|
+Notes
|
|
|
|
|
+-----
|
|
|
|
|
|
|
|
The voting application only accepts one vote per client. It does not register votes if a vote has already been submitted from a client.
|
|
The voting application only accepts one vote per client. It does not register votes if a vote has already been submitted from a client.
|
|
|
|
|
+
|
|
|
|
|
+This isn't an example of a properly architected perfectly designed distributed app... it's just a simple
|
|
|
|
|
+example of the various types of pieces and languages you might see (queues, persistent data, etc), and how to
|
|
|
|
|
+deal with them in Docker at a basic level.
|
Oliver L Schoenborn