Getting into that cadence really helps you be responsive to customer feedback. The Azure team used to deploy a major update every 2-3 months, but now it releases minor updates every 2-3 days and major releases every 2-3 weeks. Some successful cloud development teams deploy multiple times a day to a live environment. The kind of workflow you want to enable is one in which you can develop an app, deploy it, learn from production usage of it, change it in response to what you've learned, and repeat the cycle quickly and reliably. Increasingly you hear the term "DevOps." The term developed out of a recognition that you have to integrate development and operations tasks in order to develop software efficiently. For example, you can set up whole test environments including new web server and back-end VMs, databases, blob storage (file storage), queues, etc. It's uniquely important for cloud development because you can easily automate many tasks that are difficult or impossible to automate in an on-premises environment. ![]() It's an important topic because manual processes are slow and error-prone automating as many of them as possible helps set up a fast, reliable, and agile workflow. This pattern is about automating development tasks. The first three patterns we'll look at actually apply to any software development project, but especially to cloud projects. ![]() ![]() For an introduction to the e-book, see the first chapter. It explains 13 patterns and practices that can help you be successful developing web apps for the cloud. The Building Real World Cloud Apps with Azure e-book is based on a presentation developed by Scott Guthrie. Download Fix It Project or Download E-book
0 Comments
Leave a Reply. |