I once worked for a corporation that had its offices close to a river. It was a beautiful location with great views. Lunch-hour walks became the most satisfying part of my workday.
Something I witnessed along my walking path one day, completely changed how I had perceived and practiced my talks up until that day.
On a dry summer day, as I was walking, I heard a distant but faint voice. I stopped and listened. It sounded more like a one-way talk than a conversation.
As I walked closer, I saw a man standing at the edge of the riverbank, facing the river and talking. He was talking with a full voice. His animated hand gestures and occasional shake and nod of his head were very visible. …
In the previous article “Think and Develop Serverless Applications as Set-Pieces”, we saw how a serverless application can be thought of as a collection of set-pieces and developed as independent smaller services. In this article, we will see how to apply the set-pieces concept in practice. For this, we will look at Back-in-stock Email Notification feature as a case study.
As I walk you through the requirements and the architecture, I will try and follow a simple narration. I believe simple messages do not require expansive modeling artifacts!
Here is the one-liner requirement for the Back-in-stock Email Notification feature.
“In a given country, customers register their interest to get notified via email, when an out-of-stock product becomes available to…
In my previous articles on serverless, I used themes such as cooking, growing, fishing, and hiring. In this, I talk about football, movies, and music. “What do they have to do with serverless?”, you might ask. Well, there isn’t anything directly common between these themes and serverless. However, with some imagination and story-telling, we can easily build the connections ourselves.
I often make analogies to convey the serverless message. Serverless adoption happens at different levels, not just at the core technical level. …