Event Driven Frontends. What, why and how.
Within an event-driven, microservices architecture there's often a big gap between a web component that relies on some data, and the event data itself. There will usually be several services in the middle, from multiple APIs, databases, distributed caches etc. Building and updating that web component might mean touching many codebases and coordinating across many teams. This can be slow and hamper experimentation. What if... we bring that raw event data right into the browser, making it, in effect "event driven"? That web component can be developed and iterated on at lightning speed. New components can be built without the need for new endpoints. With access to the raw data, frontend developers suddenly have the freedom to explore new, bold ideas without fear of the upstream complexity.
Bio
I graduated in Physics from university and I have been in web development in one form or another for about 10 years (after a short stint as a train driver). I have always had a strong fascination with systems, big or small, virtual or actual. How they work, how they inter- and intra-connect and how they change over time. I live in Hastings on the south coast of the UK with my partner and our wonderful young daughter. I like to swim in the sea (when it's warm - which is hardly ever!) and I like to roller skate.