The Slides from the ESUG presentation are now inline here:
https://www.slideshare.net/zweidenker/docker-and-pharo-zweidenker
>>>
>>> As presented on ESUG here is the brief description of one of our current
>>> projects.
>>>
>>> Mobility Map
>>> ——
>>>
>>> Mobility Map is a
> Am 30.09.2018 um 13:01 schrieb Pierce Ng :
>
> On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote:
And a lot more. This is a coarse grained overview over the
architecture. I’m happy to answer further questions about this.
[very nice writeup]
>
> Hi Norbert,
>
>
On Wed, Sep 26, 2018 at 07:49:10PM +0200, Norbert Hartl wrote:
>>> And a lot more. This is a coarse grained overview over the
>>> architecture. I’m happy to answer further questions about this.
>>> [very nice writeup]
Hi Norbert,
Very nice write-up, thanks.
What persistence mechanism are you
> Am 25.09.2018 um 17:44 schrieb Sven Van Caekenberghe :
>
>
>
>> On 25 Sep 2018, at 14:39, Norbert Hartl wrote:
>>
>>
>>
>>> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe :
>>>
>>> Wow. Very nice, well done.
>>>
>>> Any chance on some more technical details, as in what
Yes, this is impressive.
I agree that any technical details and architectural insight (no matter how
high-level) would be useful.
Related: There's enough in http://pharo.org/success that it could be
sectioned by tags (industries, technologies, etc.). There's a lot there that
could really be
> On 25 Sep 2018, at 14:39, Norbert Hartl wrote:
>
>
>
>> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe :
>>
>> Wow. Very nice, well done.
>>
>> Any chance on some more technical details, as in what 'connected by a
>> message queue for the communication' exactly means ? How did
> Am 25.09.2018 um 12:52 schrieb Sven Van Caekenberghe :
>
> Wow. Very nice, well done.
>
> Any chance on some more technical details, as in what 'connected by a message
> queue for the communication' exactly means ? How did you approach micro
> services exactly ?
>
Sure :)
The
Wow. Very nice, well done.
Any chance on some more technical details, as in what 'connected by a message
queue for the communication' exactly means ? How did you approach micro
services exactly ?
> On 25 Sep 2018, at 12:20, Norbert Hartl wrote:
>
> As presented on ESUG here is the brief
