Chapter 14. Architecting, Building, and Publishing a Portfolio CDK Application
Whether you read the chapters sequentially and have successfully built your own CDK application, or you skipped ahead to this chapter, here you’ll learn how to build something new and unique to you.
This chapter is a little different from the previous chapters because we don’t have code examples or specific instructions for you. Instead, we will guide you through an abbreviated “working backward” process to help translate a business problem or opportunity for innovation into a cloud application that you will actually build.
Follow along to get started with defining and building your own application. We strongly encourage you to start your project by setting up a GitHub repository and your GitHub Actions workflows from the start so that you can test, publish, and share as you build.
Into the Working Backward Process
Working backward is a concept used frequently to develop new products at Amazon and AWS, but it is very similar to what is sometimes called “design thinking.”
Solving problems that are worth solving takes time. We want to make sure we are solving the right problem, and to do that, we need to continuously get feedback from internal sources (like our systems) and external sources (like our customers). Figure 14-1 provides a structure we can use as we work backward from customer problems and convert business problems into technical solutions.
Figure 14-1. Approach to solving problems in an ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access