This document discusses how to successfully build enterprise applications following best practices like the twelve-factor app methodology, practicing DevOps principles, empowering developers, and automating processes. It notes that applications should be built for specific business needs rather than copying others and that there is a gap in integrating developer tools into the software development lifecycle. Success should be measured by business value outcomes like code in production rather than "everything else". Potential platforms mentioned include CoreOS, DC/OS, Murano, Kubernetes, and CloudFoundry.

1. Frank Wu
Nicholas Gulrajani

8. How it could go! (one scenario)

9. Follow the 12- Factor Application Pattern

10. Practice DevOps - A Shared Knowledge

11. Empower the Developer - Automate the process

12. Provide meaningful data for the Developer
NOT THIS

13. LEVERAGE

14. An Enterprise Success - Follow A - B - C

15. So, What Does this Mean ?
● Don’t Build to “Copy”
● Build for the Business Specific Needs
● Gap in developer IDE integration
○ SDLC Workflow Tool Integrations
● Success metrics on Business Value
Outcomes; Code in Production
‘Everything else..!’
-CoreOS, DC/OS, Murano
-Kubernetes++ (OpenShift Enterprise)
-Cloudfoundry
….talk to us afterwards.