This. Trends change so fast that even if you write the best book of it's kind it may be irrelevant in the next year.
Talk about why this paradigm is fundamentally different. Now that developers have to worry less about server provisioning, capacity constraints etc. why is that important? What flexibility and capabilities do we have now that we didn't before?
We have dedicated many pages (and will dedicate more) explaining how/why serverless is different. Why we think it's superior (in some instances) to traditional technologies and how it can alleviate the burden that comes with managing traditional infrastructure (and current methods of implementing back ends for web applications).
The book is covering AWS and technologies such as Lambda, and API Gateway. These have already evolved as we began to write the book. I want to focus more on patterns and applications but we also need to introduce readers to these patterns and show how to actually put them together - so it's an interesting question of finding balance.
Don't just tell people why it is different. Tell people why it is the same. What is timeless about it? How do I implement the Gang of Four's singleton pattern? [well maybe that's not a good place to start].
