Tech Talk: Micro Services vs Monoliths With Jan Machacek
CoRecursive: Coding Stories
00:00
The Reactive Service Architecture
Each service, as it operates, should omit as much information about its work as possible on to this this message topic. It is now possible for someone to come along and say, you know, i'm going to build a blackmailing service. You have stream of messages going romlike message number one zero, the beginning of time, all the way to to day. Now, if you were to replay all the messages and write them to a data base table, you'd get a snapshot in history. And so it is actually sometimes really useful to to think of, like even a date base table or some sort of persisten store, as a snapshot of this system at a particular point in
Play episode from 06:45
Transcript
