Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Serverless Design Patterns and Best Practices

You're reading from   Serverless Design Patterns and Best Practices Build, secure, and deploy enterprise ready serverless applications with AWS to improve developer productivity

Arrow left icon
Product type Paperback
Published in Apr 2018
Publisher Packt
ISBN-13 9781788620642
Length 260 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Brian Zambrano Brian Zambrano
Author Profile Icon Brian Zambrano
Brian Zambrano
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. Introduction FREE CHAPTER 2. A Three-Tier Web Application Using REST 3. A Three-Tier Web Application Pattern with GraphQL 4. Integrating Legacy APIs with the Proxy Pattern 5. Scaling Out with the Fan-Out Pattern 6. Asynchronous Processing with the Messaging Pattern 7. Data Processing Using the Lambda Pattern 8. The MapReduce Pattern 9. Deployment and CI/CD Patterns 10. Error Handling and Best Practices 11. Other Books You May Enjoy

Introducing the lambda architecture


To the best of my knowledge, Nathan Martz, author of Apache Storm, first introduced the lambda architecture in a 2011 blog post. You can read the post yourself at http://nathanmarz.com/blog/how-to-beat-the-cap-theorem.html. In this post, Nathan proposes a new type of system that can calculate historical views of large datasets alongside a real-time layer that can answer queries for real or near-real-time data. He labels these two layers the batch layer and the real-time layer.

The Lambda architecture was derived from trying to solve the problem of answering queries for data that is continuously updated. It's important to keep in mind the type of data we're dealing with here. Streaming data in this context are factual records. Some examples of streaming factual data are the following:

  • The temperature at a given location at a given time
  • An HTTP log record from a web server
  • The price of Bitcoin from a given exchange at a given time

You can imagine the case where...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image