It works by accepting PUT/POST/DELETE HTTP requests on behalf of another system. If the other system is up, then Miranda relays the event immediately; if the other system is down, Miranda saves the message until the system can process it.
The microservice architecture is a great way to design a system, but if one of those microservices goes down then the system goes down too. What is needed is some way of making those microservices reliable.
Miranda is a system that makes an unreliable system reliable in much the same way that TCP makes a reliable, stream-oriented protocol from an unreliable datagram protocol.
It works by "sitting in front" of the underlying system and accepting writes (HTTP POST, PUT and DELETE) for the underlying system and recording them. If the underlying system is online, the writes are handed off immediately. If the underlying system is offline, then the writes are saved and played back in the order that Miranda received them.
DOSUG 6/6/2017 (pptx)Download
clcl Denver/Boulder Cybersecuirty meetup 8/10/2017 (pptx)Download
Miranda Denver/Boulder Cybersecuirty Meetup 8/10/2017 (pptx)Download
Miranda Tech Confluence 8/16/2017 (pptx)Download
Miranda - Denver Java Users Group 10/11/2017 (pptx)Download
Denver DevOps Meetup 10/17/2017 (pptx)Download
Miranda Denver AWS Users group 10/18/2017 (pptx)Download
clcl Denver AWS users group 10/18/2017 (pptx)Download
Miranda and clcl Denver Erlang and Elixir Meetup 11/6/2017 (pptx)Download