Preparing for “Thinking in Serverless”
Your confidence in any new technology will grow over time as you use it, just as daily tasks in life become more manageable with experience. Serverless adoption is similar—you’ll become increasingly fluent as you continue to work on it. To provide the optimal conditions for success, however, organizations that are newly adopting serverless require clarity in their understanding and guidance with their strategy.
This book aims to guide you through the essentials—organizational standards, archi‐ tectural constructs, developmental practices, operational principles, and other funda‐ mentals—so that you, your team, and your organization are well equipped as you embark on your serverless adoption journey.
Creating a Serverless Mindset
Humans constantly think, both consciously and subconsciously. But thinking as a process to solve a particular problem or outline the growth strategy for your company is not easy. When we are forced to think and produce an outcome, we rely naturally on our experience to find ideas and draw parallels to apply. When facing a problem with methodology or technology, we tend to follow a similar approach. Hence, switching from legacy practices to modern ones takes time and requires training and orientation. With cloud technology as its base and using the latest developmental practices, serverless requires you to transform your thinking to higher levels.
What are the mental changes you and your organization need to go through? This section describes how you can transform your thinking and cultivate a serverless mindset.
Aligning your thought process to serverless
As you saw in Chapter 1, the first thought transformation you should focus on is to view serverless technology as an ecosystem, and recognize that you need both tech‐ nical and nontechnical factors to work together to succeed. Keeping this ecosystem view in mind and understanding serverless’s characteristics and unique benefits is crucial to developing a serverless mindset (see Figure 2-1).
Many elements in the serverless ecosystem, such as the source code repository and deployment pipelines, will likely already be familiar to you. But while many of the basic concepts remain the same, the tools and deployment targets will differ—for example, your deployment target will now be the cloud, and the operating environ‐ ment will change.
Figure 2-1. The importance of keeping the serverless ecosystem view as a whole
