Write-up of how we’ve used event-driven architecture at ITV to enable a data-driven approach to the content supply chain. By rearchitecting an existing message-driven, microservice-based system, we were able to introduce data and analytics capabilities without impacting feature development.
Why do we need this? One of the most difficult aspects of a leader’s role is striking the right balance between giving direction and encouraging teams to make decisions independently. While experience may suggest that a particular approach is likely to be the most effective, it’s unlikely to be successful unless the team commits to it. There’s also a chance that better solutions exist, and given the right environment, teams will often discover these for themselves.
Experimenting with snippets of code and getting rapid feedback is a good way to get up to speed with a new language or library. I’ve been using Kotlin and Λrrow at work this week, so have been looking for tools that help achieve this workflow. Worksheets in IntelliJ provide some of this functionality, but personally I prefer the immediacy of a text editor and the command line for this kind of thing.
Learning (and subsequently trying to explain) monads has become something of a rite of passage in functional programming. Burrito analogies aside, the most helpful description I have come across is given by Noel Welsh and Dave Gurnell in Scala with Cats:
“A monad is a mechanism for sequencing computations.”
Case classes provide a convenient way of working with immutable objects in scala. Manipulating fields within them can be tedious, however. In this post, we will look at how lenses can be used to abstract over this complexity while preserving the benefits of immutability.