Commit: 9ec6ed10322298a515413dfa36e86589821b75b0 - MESS (hg)

Commit MetaInfo

• Révision: 9ec6ed10322298a515413dfa36e86589821b75b0 (tree)
• l'heure: 2020-03-19 19:04:20
• Auteur: Albert Mietus < albert AT mietus DOT nl >
• Commiter: Albert Mietus < albert AT mietus DOT nl >

Message de Log

Pub/Sub: lead done

Change Summary

• modified: SoftwareCompetence/DesignWorkShops/index.rst
• modified: conf.py
• add: SoftwareCompetence/DesignWorkShops/PubSub/index.rst

Modification

diff -r 2052cb956f31 -r 9ec6ed103222 SoftwareCompetence/DesignWorkShops/PubSub/index.rst
--- /dev/null	Thu Jan 01 00:00:00 1970 +0000
+++ b/SoftwareCompetence/DesignWorkShops/PubSub/index.rst	Thu Mar 19 11:04:20 2020 +0100
@@ -0,0 +1,62 @@
+.. Copyright (C) 2020: ALbert Mietus.
+
+.. _PubSub:
+
+=============
+**Pub**/*Sub*
+=============
+
+.. sidebar:: **HighTech** vs *Gooogling*
+
+   When you search for `Pub/Sub`, you will find over 312M hits! Mostly about cloud-computing, and on how servers exchange
+   messages via a *‘broker’*.
+   |BR|
+   Often it is infrastructure engenering based.
+
+   This workshop isn’t about that. We focus on *Modern, Embedded Software Systems*: How can an (HighTech) Software Engineer use
+   this pattern to create better software.
+
+
+.. post:: 		
+   :tags: DesignWorkShops
+   :category: practice
+   :location: ehv
+   :language: en
+
+   :practice-time: 2 * 1 hour
+
+   The publish-subscribe *architecture*-**pattern** is very popular to route messages, according to `WikiPedia
+   <https://en.wikipedia.org/wiki/Publish–subscribe_pattern>`_.  It is used much more generic, however. This workshop shows how
+   to use it in an embedded application; or another single process application.
+   |BR|
+   Then it becomes a HighTech (embedded) software **design pattern**.
+
+   We start with a simple implementation of **Pub**/*Sub*. You can experiment with that (Python) code and/or port it to your
+   favorite language. Then, you are asked to **design** a cached, distributed version. Which is a bit more ambitious. And even
+   though the result is probably *pointless*, it’s a great Design-Exercise and a lot of fun!
+
+   It will help you to understand Pub/Sub, help you to use it in embedded software. Eventually, you may need Pub/Sub in a
+   distributed environment. Then, it is better to use one of the existing ones, like `DDS
+   <https://en.wikipedia.org/wiki/Data_Distribution_Service>`_ (Data Distribution Service); which more efficient and even
+   RealTime!
+   |BR|
+   But, by knowing how to implement it and are able to design it, will help you to use it for the better
+
+
+
+.. toctree::
+   :glob:
+
+   *
+   */index
+
+
+
+------------------------
+
+
+.. _PubSub_links:
+
+.. seealso::
+
+   * ...

diff -r 2052cb956f31 -r 9ec6ed103222 SoftwareCompetence/DesignWorkShops/index.rst
--- a/SoftwareCompetence/DesignWorkShops/index.rst	Thu Mar 19 09:36:44 2020 +0100
+++ b/SoftwareCompetence/DesignWorkShops/index.rst	Thu Mar 19 11:04:20 2020 +0100
@@ -9,4 +9,5 @@
    :glob:
    :maxdepth: 2
 
-   */index
+   TPE/index
+   PubSub/index

diff -r 2052cb956f31 -r 9ec6ed103222 conf.py
--- a/conf.py	Thu Mar 19 09:36:44 2020 +0100
+++ b/conf.py	Thu Mar 19 11:04:20 2020 +0100
@@ -54,3 +54,4 @@
         '**': [ 'recentposts.html', 'tagcloud.html', 'postcardHeader.html'],
     }
 
+html_static_path.append('_static')