Serverless Development on AWS

Chapter 5. Serverless Implementation Patterns

There are only patterns, patterns on top of patterns, patterns that affect other patterns. Patterns hidden by patterns. Patterns within patterns.

Chuck Palahniuk

There are patterns all around you. This book follows a pattern; every chapter has a pattern. Nature is full of patterns. Chapter 3 mentioned the three elements of architecture: art, structure, and technique. You’ll see patterns in each of these elements. Though patterns in physical architecture show the influence of region, climate, culture, etc., commonality still prevails in many cases. Patterns in software architecture follow a similar trend: though there are underlying commonalities, many show the influence of the business domain, programming language, operating environment, and other factors.

Irrespective of the differences, patterns aim to provide solutions to recurring and common problems related to the architecture, design, implementation, or operation of software systems. Patterns can become opinionated, especially when influenced by the abovementioned factors. Some patterns come and go quickly while others survive for much longer, although their implementations may differ over time. The circuit breaker pattern (discussed later in this chapter) is a good example; its name might not be obviously related to software, but adaptations and applications of this pattern are visible across different eras and technology stacks. Some patterns become so popular that after ...