Omaha DevOps Meetup - Sept 2018
Download as PPTX, PDF2 likes212 views
The document outlines Nebraska Furniture Mart's transition to a microservices architecture and cloud-based infrastructure to improve their e-commerce platform, emphasizing the challenges faced with aging software and the need for innovation. Key achievements included a significant increase in deployment frequency and reduced release times, enhancing the company's ability to scale and adapt to market changes. The company's mission aims to create a fast, secure, and reliable online shopping experience to support future growth.
Omaha DevOps Meetup - Sept 2018
- 1. NFM’s Cloud, DevOps, Containers, and Microservices Adventures Michael Nichols Senior Software Architect September 2018
- 2. Brief Nebraska Furniture Mart History 2 Largest home furnishing store in North America selling furniture, flooring, appliances and electronics Founded in 1937 by Rose Blumkin, universally known as Mrs. B. under the motto "sell cheap and tell the truth,“ she worked in the business until age 103 In 1983, Mrs. B. sold a majority interest to Berkshire Hathaway in a handshake deal with Warren Buffet
- 3. The Current Ecommerce Landscape Q2 2017 Results were outstanding Walmart up 63% Target up 32.4% Amazon up 26.6% (now represents 38% of all ecommerce, up 2%) Nebraska Furniture Mart up 16.5% Walmart U.S. online sales up 33% in first fiscal quarter of 2018 Major competitor growth accelerating Innovation is disrupting retail like nothing ever seen before. 3 $econds = 3
- 4. U.S. E-Commerce Sales Growth by Quarter 4 Source: https://www.digitalcommerce360.com/2018/08/20/u-s-e-commerce-sales-quarter/ Non-adjusted figures from the U.S. Commerce Department, Internet Retailer. This data was updated on August 2018
- 5. • In 10 years, the retail industry will look nothing like it does now. • “The department store is online now.” • “The world has evolved, and it's going to keep evolving, but the speed is increasing.” The Current Ecommerce Landscape 5
- 6. Rollout out 2006 2011 Redesign 2017 NFM Website History 6 − ASP.NET 2.0 − SQL Server − Double Digit Growth Annually − Major Redesign − Search Engine Solution − Landed in the top 500 retail site − Rank 275th in the Internet Retailer 2017 Top 1000 − 35% Annual Growth over the last 5 years
- 7. Our Challenges 7 Aging Software Architecture and Infrastructure IAAS - Infrastructure as a Service Third Party Challenges
- 8. Our Challenges • Monolithic Application • Tied to a single developer framework and run time • Required Horizontal Scaling • DLL dependencies and version management for entire application • Manual Testing Efforts • Testing requires full regression for small changes • All or none deployments • Constraints prevent Innovation 8
- 9. Our Challenges 9 • Dependent on IAAS provider’s hardware resources as well as staff resources and skill sets • Coined the term “IAAR” - Infrastructure as a Request • Environments Lack of transparency, repeatability, and stability • Fear of change due to lack of proper change management (silos of knowledge and skillsets)
- 10. Our Challenges 10 • 3rd Party Mobile Dependency • 3rd Part Search Engine Limitations
- 11. Our Vision 11 Green Field Effort Microservice Architecture Implemented via Containers running in Mesosphere DCOS on Microsoft Azure supported by an Automated CI/CD pipeline • Vertical Scaling • Simplified delivery • Automated & Reproducible • Improved Resource Utilization • Supports adopting the latest cutting edge technologies and development frameworks – Asp.Net Core • Supports automated unit, service and various integration testing • Allows releases of individual services /multiple versions service. • Build Once – Run Everywhere
- 12. 2016/2017 FFNFM Started 1/2018 Internal Beta Launch 3/2018 Beta Launch 6/2018 Mobile Launch 9/2018 Full Site Launch Our Path 12 Mission Statement Based on our tradition of providing quality products and services, we are working to build a world class site that is fast, secure, reliable, accessible and scalable, which will support future growth and features to better serve our customers.
- 13. Keys to Success – Strategies 13 • DevOps Culture • Microservices Architecture/Containers • Move to Cloud • Automation Everywhere!
- 14. DevOps Culture Implement Microservice Architecture via Software Patterns In Single Solution Separation of Service including builds & releases Test Automation & wiring into builds and release Automating of Infrastructure "Infrastructure as Code" Initial Pipeline creation - Dev Teams begin working in POC environment Monitoring & Alerting Pipeline updated to reflect process Teams consume/ experiment with Pipeline in clusters and define release process Infrastructure Automation of cluster implemented Builds & Release deployed to DCOS cluster Full pipeline builds/ releases/process POC on DCOS clusters
- 15. DevOps Culture Agile Project Management Challenges User Stories – Too Large and Lacked Clear Definition of Done Spanned iterations Unable to represent work completed Overcommitting WIP – Ineffective multitasking Lots of unknowns – New technologies and immature tooling Team Norms DevOps Culture Challenges Minimal Viable Product – Good enough! Sharing roles/responsibilities - Eliminating Silos Transparency/Documentation for Team Members/Development/External Teams Involvement of Security/Compliance/Corporate teams early Dual responsibilities support existing & new 15
- 16. Docker Local Development Microservices Architecture/Containers
- 19. Move to the Cloud SAAS First, PAAS Second, and IAAS Last
- 20. Lessons learned – Overcoming hurdles from latest technology Microservice Code POC New Code Base Started – AspDotNetCore Apha unstable Separation of Services/Domains - Refactoring efforts NuGet packages – Refactoring and versioning issues Single service version – No team independence Build Releases POC TFS Builds and Releases – Immature Tooling Silos of knowledge Automated Testing POC Unit Tests – Code coverage transparency and tooling issues Test Architect - Tooling knowledge and difficulty identifying appropriate integration tests 20
- 21. Our Wins From… Development teams completed 1 release per week / 52 releases over a 12-month span. 28 hours to complete a monolithic code push – going from committing code to stage to being released into production To… Development teams have completed 81 releases since May 1st – Sept. 24th The development teams are on pace to complete more than 240 releases in a 12-month span. That’s an increase of 362% more releases with the new site versus the old site. An average of 1 hour and 18 minutes to move a change from dev to prod That’s a 95% decrease in the time it takes to release new functionality in the new site versus the old site. Over 500 unit tests are run with each release in less than 40 seconds. Completed 4 successful production releases on Sept. 18th
- 23. Twelve-Factor App methodology I Codebase There should be exactly one codebase for a deployed service with the codebase being used for many deployments. II Dependencies All dependencies should be declared, with no implicit reliance on system tools or libraries. III Config Configuration that varies between deployments should be stored in the environment. IV Backing services All backing services are treated as attached resources and attached and detached by the execution environment. V Build, release, run The delivery pipeline should strictly consist of build, release, run. VI Processes Applications should be deployed as one or more stateless processes with persisted data stored on a backing service. VII Port binding Self-contained services should make themselves available to other services by specified ports. VIII Concurrency Concurrency is advocated by scaling individual processes. IX Disposability Fast startup and shutdown are advocated for a more robust and resilient system. X Dev/Prod parity All environments should be as similar as possible. XI Logs Applications should produce logs as event streams and leave the execution environment to aggregate. XII Admin Processes Any needed admin tasks should be kept in source control and packaged with the application. 23
- 24. Useful Resources 24 Microservices in .NET Core By Christian Horsdal Gammelgaard Docker in Practice By Ian Miell and Aidan Hobson Sayers Microservice Patterns (eBook) By Chris Richardson
Editor's Notes
- #12: Based on our tradition of providing quality products and services, we are working to build a world class site that is fast, secure, reliable, accessible and scalable, which will support future growth and features to better serve our customers.
- #24: The Twelve-Factor App methodology is a methodology for building software as a service applications. These best practices are designed to enable applications to be built with portability and resilience when deployed to the web.[1] References[edit] ^ Jump up to:a b c Hofmann,, Michael; Schnabel, Erin; Stanley, Katherine (13 March 2017). Microservices Best Practices for Java. IBM Redbooks. p. 2—3. ISBN 9780738442273.