Throughout this chapter, cloud drivers and considerations were discussed, and we dived deeper into how an enterprise would migrate existing workloads into the cloud. While some of these patterns contain development activities to refactor or replatform the application, they are still migration patterns. So, the question is: when does an organization use greenfield development instead of migrations? Typically, when a company decides to be cloud first, they will focus a significant amount of effort migrating their existing workloads to the cloud. At the same time, they will start all new development activities in the cloud, which is greenfield development. Usually, a new project or workload will still require interface points with the legacy applications, whether they are in the cloud or still being migrated, and therefore, a common intersection between these two activities is the integration of interface points. 

As the migration activities subside, the focus on new development in the cloud is a top priority. This phase after migration is usually an exciting time at the organization, since the cloud skills are strong and the optimism of how the cloud can change the company are high. Being a cloud native architect during this time will allow for big ideas to be put forward and old barriers to be removed.