Adopting a PaaS Solution (Part 2) - Red Hat DevOps & Microservices Conference 2017
2 likes351 views
The document outlines the twelve-factor methodology for building cloud-ready applications. The twelve factors are: I) Codebase, II) Dependencies, III) Config, IV) Backing services, V) Build, release, run, VI) Processes, VII) Port binding, VIII) Concurrency, IX) Disposability, X) Dev/prod parity, XI) Logs, and XII) Admin processes. The twelve-factor methodology advocates building applications that are optimized to leverage benefits of the cloud such as scale, isolation and resilience.
Adopting a PaaS Solution (Part 2) - Red Hat DevOps & Microservices Conference 2017
- 1. Adopting a PaaS Mario Mendoza Solution Architect marmendo@redhat.com
- 2. I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes Twelve Factor
- 3. I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes Twelve Factor What about my current applications ?
- 4. REFACTOR ● Legacy is totally replaced ● New interfaces and data ● Use OCP as platform ● Some data and features can be re-wrapped, but most are refactored. PATTERNS IN MODERNIZING WORKLOADS 3 MAIN PATTERNS REHOST ● Containerize existing workloads ● Deploy them on OCP ● Keep external integrations and data on legacy ● Focus on smaller or frozen apps REPLATFORM ● Legacy remains intact ● New layer - new capabilities ● Deploy on OCP ● New integration points between legacy and new layers (Need for Agile Integration)
- 5. Not our target APPLICATION MODERNIZATION Application Portfolio Rehost (lift/shift) Replatform (lift/reshape) Repurchase Refactor (rewrite, decouple apps) Review Analyze Prioritize Retire Retain as is (for now) How much work required ? Highly scaled and high rate of change apps are candidates Smaller or frozen apps are candidates here Identify services and applications portfolio
- 6. Red Hat Services for APPLICATIONS MIGRATION AND MODERNIZATION Explore Analyze Prove Pilot Migrate in Iterations Discovery Session Discuss Options Define Migration Strategy, Prove Technology and Business Case Scale & Execute Plan Migrate to a container based PaaS ● WebSphere/WebLogic JBoss EAP ● Tibco, JCAPS JBoss Fuse Integration Services ● IBM/MQ JBoss A-MQ ● IBM WODM JBoss BRMS
- 7. I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes
- 8. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 9. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 10. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 11. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 12. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 13. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 14. VII. Port binding Export services via port binding VIII. Concurrency Scale out via the process model IX. Disposability Fast startup and graceful shutdown X. Dev/prod parity Keep development, staging, and production as similar as possible XI. Logs Treat logs as event streams XII. Admin processes Run management tasks as one-off processes I. Codebase One codebase tracked in revision control, The codebase is the same across all deploys II. Dependencies Explicitly declare and isolate dependencies III. Config Store config in the environment IV. Backing services Treat backing services as attached resources V. Build, release, run Strictly separate build and run stages VI. Processes Execute the app as one or more stateless processes TWELVE FACTOR for cloud ready applications
- 16. Adopting a PaaS Mario MENDOZA Solution Architect marmendo@redhat.com