WSO2Con US 2013 - Re-design Enterprise IT with WSO2 App Factory and WSO2 Cloud
•
1 j'aime•513 vues
Recommandé
Contenu connexe
Tendances
Tendances (20)
Similaire à WSO2Con US 2013 - Re-design Enterprise IT with WSO2 App Factory and WSO2 Cloud
Similaire à WSO2Con US 2013 - Re-design Enterprise IT with WSO2 App Factory and WSO2 Cloud (20)
Plus de WSO2
Plus de WSO2 (20)
Dernier
Dernier (20)
WSO2Con US 2013 - Re-design Enterprise IT with WSO2 App Factory and WSO2 Cloud
- 1. Re-design Enterprise IT with WSO2 App Factory and WSO2 Cloud Chris Haddad WSO2 Vice President, Technology Evangelism
- 2. Disruptive Forcing Functions • Addressing The Long Tail Market • Interacting in The New Web • Becoming The Now Generation • Avoiding The Innovator’s Dilemma • Connected Business
- 3. What is your revenue growth strategy? The Long Tail of Market Opportunity
- 4. Where to engage your customer and partner? Interacting on The New Web Mobility, Internet of Everything, and Ecosystem Business Models are Transforming The Web
- 5. When to deliver? Right Now • Time to create a new product – Time to design and build – Time to complete a product trial • Time to enter a new market – Time to onboard local partners – Time to create a marketing campaign • Time to react to market events • Dwell time – time waiting for the next operation to commence or complete
- 6. How to avoid the innovators dilemma? A Flexible, Value-Web Structure
- 7. Why envision a Connected Business? Connected businesses grow revenue and outperform peers by •increasing customer engagement •enhancing productivity •seizing market opportunity
- 8. Connected Business Attributes Accelerates interactions inside and outside the organization Reduces interaction friction and cost Senses business activity and automatically adapts Increases engagement and enhances productivity
- 9. Connected Business Reference Architecture
- 10. Redesign Success Requires Adopting New IT Disciplines
- 11. How do you Redesign IT? Adopt a Cloud-based, Digital Business Ecosystem Platform – Cost-effective, development, collaboration, and deployment infrastructure enabling a long tail of application development and integration – A shared environment for cross-organization application development and delivery – Infrastructure enabling user experience composition across multiple disparate application, API, and service providers
- 12. Redesign Targets
- 13. WSO2 Cloud Native Advantage • Automated governance • Multi-tenant platform • On-demand self service • Elastic scalability • Service-aware load balancing • Cartridge extensions
- 15. WSO2 DevOps Advantage • Complete lifecycle automation Collaboration oriented • Project workspaces and dashboards • Continuous delivery
- 16. To establish responsive Iterations Adopt Unified, Full Life Cycle DevOps
- 17. To Establish Responsive Iterations, increase DevOps automation
- 18. • • • • WSO2 PaaS Offering - Key Differentiators A complete set of Cloud-Native middleware services enabling complex project delivery Enterprise-ready foundation – Scale, performance, SLA, integration Re-shapes team collaboration and reduces wait states – Incorporates DevOps processes – Fosters Application Lifecycle Management and Governance best practices Business driven PaaS – Lowest run-time cost – CxO dashboards delivering portfolio visibility – Development and DevOps dashboards presenting activity, iterations, and project blockers – Showback/chargeback billing
- 19. Recommended Reading • The Path to Responsive IT – http://wso2.com/whitepapers/the-path-to-responsive-it • DevOps Meets ALM in the Cloud – http://wso2.com/whitepapers/devops-meets-alm-in-the-cloud-cloud-d paas • Cloud-Native Advantage – http://wso2.com/whitepapers/cloud-native-advantage-multi-tenant-sh paas • Promoting Service Re-use with API Management – http://wso2.com/whitepapers/promoting-service-reuse-within-your-en success
Notes de l'éditeur
- 20-25 minutes Disruptive technology forces coupled with increasing business revenue and growth demands provide the catalyst for examining how to redesign Enterprise IT into a more responsive and agile organization. Re-designing Enterprise IT culture, practices, and architecture is incredibly difficult. The way to shift the status quo and improve delivery is through grassroots adoption, best practice mentoring, and making the right path the easy path. In this session, Chris will describe how to successfully re-design Enterprise IT practices, achieve responsive iterations, gain effective collaboration, and streamline processes by adopting WSO2 App Factory and WSO2 Cloud.
- Successful and growing organizations adapt their corporate structure, address time to market hurdles, seize the long tail of market opportunity, and address New Web interaction models.
- Traditional corporate structures, and traditional corporate IT, only satisfies the most valuable and mission critical market opportunities. A long tail of market opportunities remain unaddressed. To accelerate business growth, organizations must adjust their cost models, team structure, market message, and delivery mechanisms to move ‘down market’ and address the long tail of niche opportunity Because every efficient and successful business initiative today requires an IT component, corporate IT must reduce the platform cost structure, learning curve, and deployment models to fit down-market dynamics or individual, small project requirements.
- Mobility, Internet of Everything, and Ecosystem Business Models are Transforming The Web People are shifting away from destination sites (e.g. Yahoo, Google Search, CNET, CNN) and social networks (e.g. Facebook, Twitter) towards accessing information and interacting with businesses using Web APIs and local apps
- In the abstract, business agility can be defined as your ability to rapidly change business vectors. A business vector is your business speed and direction. The direction may lead into nIew markets and new products, or engaging with new participants. Reducing time to IT solution delivery increases your team’s ability to adjust the business vector and match business opportunity. With adequate instrumentation, IT delivery agility can be quantified. Consider the following agility metric recommendations: Time to create project workspace Time to build, integrate, test Time to approve, promote Time to deploy, release Dwell time – time waiting for the next operation to commence or complete After application project inception and before coding commences, systems administrators must create project workspaces. How long does your team wait before gaining access to source code management repositories, requirement management projects, and defect tracking projects? Moving code through build, integration, and test tools is often a time and labor-intensive process. The entire team waits while applications assets are built, integrated, and tested. When teams use iterative development processes, the wait time aggregates over several hundred or thousands cycles. How long does your team wait during build, integration, and test phases? When one team member finishes a task and the work enters an approval phase, how long does the team wait? After the work is approved to move through phase gate, how long before the project is promoted into the next phase?
- Monolithic corporate go-to-market structures are evolving into distributed teams working together to design, build, sell, and distribute products. Enhanced business network connectivity and increased business asset digitization is creating an environment where team participants can work together across geographical and organizational boundaries to create value webs. Value webs are ad hoc teams that create solutions for a specific, targeted business opportunity. For example, a special purpose, value web team introducing a product into a new market. By creating value webs instead of business units, organizations can nimbly and flexibly address new markets, seize market share, and avoid the ‘innovators dilemma’. John Malone wrote about the disruptive ‘Protean Corporation’ [1]. While business does not have to entirely adopt the Protean structure, creating a flexible structure while preserving corporate culture can help all organizations address more diverse market opportunity and increase revenue growth. [1] http://www.amazon.com/The-Future-Arrived-Yesterday-Corporation/dp/0307406903
- A connected business seamlessly integrates people, process, and data across an extended value chain decreases interaction cost automatically adapts business activity in response to market events Integrated Accelerates interactions inside and outside the organization Accessible Reduces interaction friction and cost Collaborative Increases engagement and enhances productivity Adaptive Senses business activity and automatically adapts
- When defining a roadmap to align IT’s pace with business agility expectations, establish IT team objectives that quicken IT solution development and delivery, offer new technology as on-demand shared services, and enhance your team’s ability to rapidly satisfy emerging business use cases (e.g. social collaboration, mobile application connectivity, ecosystem partnering). Open source PaaS, Open APIs, and Open Ecosystems are accelerating agility, empowering developers, and enabling innovative business strategies. In a recently published white paper, I describe how adopting a New IT plan can create a responsive IT team. The path to New IT requires moving away from traditional application platforms, traditional team structure, and traditional information flows. Responsive IT teams are adapting their infrastructure, processes and tooling to re-invent the application platform and re-think application delivery. The New IT architecture underlying Responsive IT intelligently incorporates Cloud Platforms, BigData Analytics, Enterprise DevOps, and API first development.
- eTrade: API, consumers must submit application for code review * compliance focus * *automation* enables long tail * Cloud is a game changing enabler use cases
- Reduce time to market, streamline processes, rapidly iterate by adopting a New IT platform that includes the following Cloud-Native concepts and Cloud-Aware behavior: Automated governance safely secures Cloud interactions, hides Cloud complexity, and streamlines processes DevOps tooling delivers an on-demand, self-service environment enabling rapid iteration and effective collaboration Multi-tenant platform reduces resource footprint and enables new business models On-demand self service streamlines processes and reduces time to market Elastic scalability broadens solution reach across the Long Tail of application demand (high volume and low volume scenarios) Service-aware load balancing creates a service-oriented environment that efficiently balances resources with demand Cartridge extensions transform legacy servers into Cloud-aware platforms Learn more about Cloud-Native Platform as a Service. Read more about multi-tenant platform advantage and how to select a Cloud Platform.
- DevOps principles and practices bridge the divide between solution development and run-time operations to deliver projects faster and with higher quality. WSO2’s DevOps for Developers perspective automates deployment and also offers: Complete lifecycle automation guides projects from inception through development, test, production deployment, maintenance, and retirement Collaboration oriented environment eliminates communication gaps Project workspaces and dashboards communicate project status, usage, and deployment footprint to all stakeholders Continuous delivery fosters responsive iterations and faster time to market Learn more about DevOps PaaS capabilities, and read more about how WSO2 integrates DevOps with ALM in the Cloud
- Agile and DevOps principles must be applied across a cross-functional team and the entire lifecycle (e.g. project inception, design, development, deployment, and management). Operations activities related to deployment and release management often hinders agility and time-to-market. The level of effort required to deploy a real-world application is often non-trivial. Continuous deployment technology automates operations activities and replaces manual intervention. While dwell time sounds cozy and refreshing, excessive wait states and downtime between activities diminishes team efficiency and engagement. Automated notifications eliminate dwell time between hand-offs. Automated project workspace creation, Cloud environment provisioning, and on-demand self-service access reduces wait time between software development phases. A DevOps focus on continuous activity execution (e.g. continuous build, continuous integration, continuous test, continuous delivery) creates a ‘no wait’ environment. Teams do not have to wait for the next script to run or for the next activity to commence. By incorporating automation into developer and operations processes, teams bypass time consuming manual tasks and gain faster phase execution. Both DevOps and PaaS promote simple, on-demand self-service environments that shield team members from complexity and reduce skill hurdles. By offering on-demand self-service access, rapid business innovation and experimentation is possible. By reducing complexity, team members are not required to obtain special training and skills before consuming IT services and infrastructure. To read more about Enterprise DevOps PaaS accelerating team agility, read a recent blog post.
- Traditional application PaaS (aPaaS) environments do not help organizations build apps, but simply serve as a cloud run-time environment. DevOps PaaS brings no waits, faster phase execution, widespread accessibility, rapid grassroots innovation, and increased resource availability to IT projects. DevOps PaaS delivers development, test, and production run-time clouds that are integrated into development workspaces containing source code management, defect tracking, requirements management, test automation frameworks, and continuous build. Figure 2 describes the infrastructure topology underlying a DevOps PaaS. By automating software activities, workflow, and phase approval gates, a DevOps PaaS decreases software development and delivery times. A rapid IT timeframe closely matching today’s fast business-pace will accelerate revenue growth and enhance customer retention rates. A New IT model driven by DevOps PaaS will expand development team participation, lower IT cost, and increase business agility. Recommended Reading DevOps Meets ALM in the Cloud PaaS Performance Metrics Multi-tenant, shared container PaaS TCO WSO2 App Factory Product Page
- A complete set of middleware services (e.g. integration, API, web services, web applications, event processing, registry, business activity monitoring) Increase team collaboration and reduce wait states by supporting DevOps processes and Application LifeCycle Management practices with Cloud run-time infrastructure CxO dashboards and delivering portfolio visibility (e.g. app/API usage, app/API spend, project pipeline) and demonstrating IT efficiency (e.g. on-time, on-budget, component/API re-use); Development and DevOps dashboards presenting activity, iterations, and project blockers. Lowest run-time cost based on in-process application platform resource sharing yielding industry-leading tenant density Tenant-aware and service-aware load balancer optimizes application platform service sharing OSGI based tenant-isolation leads to reduced application platform license (or subscription) cost aPaaS auto-scale functionality reduces DevOp burden by eliminating need to explicitly define application topology - dynamic, policy based partitioning and provisioning of private and shared tenant resources - Automatic, flexible topology provisioning across private, managed, and public Clouds Presents an Application Platform Service view to development teams instead of an infrastructure detail view Big Data Analytics and Complex Event Processing capabilities for Adaptive Business environments