The mission of Mercury Health is to help improve longevity and quality of life through healthy activity. The Mercury Health development team has embraced a DevOps approach and is using continuous integration for builds and unit tests. If everything passes they use continuous deployment that deploys to various environments. Then UI Automation tests are run to ensure usability and key functionally works as designed. Lastly, Load and Performance tests are run from various locations around the world at the expected peak load to ensure there are no challenges around performance or stability when operating at full capacity.
- Code QL:
- Microsoft Security DevOps Analysis:
- Full Deployment, Dev, QA, Prod:
- Single Deployment, Dev only:
At Microsoft, DevOps means one thing. “It is the union of People, Process and Products to enable continuous delivery of value to our end users”. -Donovan Brown, Partner PM Azure Incubation Team. On the people side, this means breaking down walls between dev teams, qa teams and ops teams. Instead of three separate teams, have one team with everyone focused on one goal, to continually deliver value to our end users. Teams have become far more cross functional and own the end-to-end customer experience. The developers role is too implement a user story, write full coverage unit tests for that user story and either work with QA to write UI automation or writing the UI automation themselves to test the User Story. This way, devs can iterate fast enough and catch regression bugs without the need for months of regression testing that’s such a manual process.
We’re also working hand in hand with the Ops folks to figure out what is the best way to consistently and quickly deploy our applications. For processing, there needs to be a process in place which will let teams iterate fast enough, produce code of high enough quality, and a way to deliver the application to the end users quickly and consistently. Agile processes (done correctly) work great. And finally, for end-to-end products and tooling, the answer can be Azure DevOps & GitHub, a better together story.
- Part 1 - DevOps Nirvana – Part 1
- Part 2 - [DevOps Nirvana – Part 2] Continuous Delivery, coming soon...
- Part 3 - [DevOps Nirvana – Part 3] Demo Setup and Walkthrough, coming soon...
DevOps Nirvana, what does this mean? Webster defines it as a state of perfect happiness. Although a complete DevOps end-to-end setup might not be perfect, it can be extremely close. By adopting the principles of agile, automation, continuous integration and continuous delivery, and you will reach your goal of healthy DevOps.
- DevOps addresses the risk associated with changes.
- This risk arises from missed requirements, new bugs, failed deployments, etc.
- DevOps focuses on streamlining deployments to minimize the effort required to deploy software.
- As applications complexity increases, we see deployments measured not in man hours but in man days.
- Deploy more frequently, with reduction of pain associated with performing each deployment.
- This also helps to ensure consistency so that QA looks like Dev and Production looks like QA.
- DevOps minimizes hand-offs between teams.
- This is not only through leveraging technology, but also by changing the cultures of the teams involved.
- Significantly higher throughput.
- High functioning DevOps organizations have drastically higher throughput. In these organizations code makes it from Commit to Production 2,555 times faster.
- Significantly higher employee loyalty.
- Employees of these organizations are 2.2 times as likely to recommend their current employer to a friend as a “great place to work”.
- Significant increase in quality.
- Unplanned work is reduced by 22%, leading to a 29% increase in new work completed by their development and DevOps team.
- Significant reduction in Security Issue mitigation.
- A 50% reduction in the time spent addressing security issues.
Back in early 2016, Abel Wang and I met in-person for a couple days and worked to create an app and demo that was simple enough to setup, yet powerful enough to demonstrate some core concepts of DevOps best practices on Azure. During this time, Mercury Health was born, named after Greek Mythology by Jeff Fattic. This app is basically a simple health tracking application. It tracks the exercises that you do and food that you eat throughout the day. Then based on the calories in and calories out, it draws some cool graphs to let you know if you're healthy or not. Recently I re-wrote and enhanced the app using .Net 6 to utilize some key concepts and Azure services such as App Service Plans, App Service, Key Vault, SQL DB, Configuration Store, Feature Flags, Application Insights, Log Analytics Workspace, Playwright UI Automation, Availability Testing, API Management, and Azure Load Testing for performance and scalability testing. The source code repo of choice is GitHub that uses the built in tools, DependaBot, CodeQL, Advanced Security, and GitHub Actions for CI/CD.
The development team follows the modern application pattern for building and deploying code using resilient DevOps practices.
The development team follows the common web application architecure for building a single project with traditional application layers.
| Azure DevOps | Microsoft Teams | Microsoft Teams |
|---|---|---|
 Dashboard |
 Development Channel |
Live Sites Channel |
This project has adopted the Microsoft Open Source Code of Conduct. For more information see the Code of Conduct FAQ or contact opencode@microsoft.com with any additional questions or comments.