You will need to register with SkillsMatter here before attending. This is important!
HTTP and REST is seen as the underpinning of Microservices, yet implementations tend to adopt other systems over time to gain access to the richer semantics that they provide. This session will investigate options for Microservices communication.
6:30 - Arrive, brief introductions.
6:40 - Demos/ Lightning talks
7:20 - Software Memories and Simulated Machines
8:00 - Finish.
Lightning Talk - AMQP/MQ Light as a transport for Microservices. Thoughts and practical advice.
Steve Upton - Developer for IBM MQ Light. Working in messaging on AMQP, MQTT and MQ projects.
Overview of the challenges and advantages of using AMQP as a Microservice transport. How you need to think and architect differently when using an asynchronous protocol like AMQP.
Lightning Talk - Introducing Event Sourced Microservices
Brief Introduction to approaching Event Sourced Microservices. How to think about them, the options it creates, and the common pitfalls of the pattern.
Main Talk - Software Memories and Simulated Machines
In this talk a vision is presented for the future of large scale distributed software development and deployment that is based on mirrored simulation of software execution behaviour (motion) and its environment (state) for reinterpretation and augmentation across space and time. When fully realized across multiple languages and platforms this vision has the potential to be one of the most significant advances in the engineering of software systems.
The talk will touch on the following topics which have inspired this approach:
• activity theory
• mirror neurons and simulated embodiment
• simulation theory (and the matrix)
• episodic memories and dreams
as well as indirectly:
• discrete event simulation
• actor programming model
• supervision and control
• signals and boundaries
This talk offers a model of human and software understanding based on activities actioned by actors within an environment supporting observation and perception of such acts including the situational context surrounding them, both before and after. The model is used to capture software behavior that is then streamed and mirrored into a Machine Matrix in which extensions, adaptations and augmentations are applied post execution as playback of behavior is simulated across 1000s of threads and processes.