The architecture of this is perhaps the most complex in this book, even though the implementation itself is relatively simple. As mentioned earlier in this chapter, there are many moving parts in a lambda architecture since it is two distinct systems that work side by side, with each having its own unique set of services. I show a high-level architecture in the following diagram:
This design is somewhat contrived and overly simplified. A system with true scale likely would not be able to get away with a serverless function that calculated historical prices by year, as I do in the batch layer. To fit this example application into a single chapter, I had to make the system relatively simple to demonstrate the pattern and ...
