Why Reshape Reference Architecture
•Descargar como PPT, PDF•
2 recomendaciones•3,076 vistas
The reference architectures of the past (i.e. client-server, web application, SOA services) are not adequately addressing current business demand, use cases, and expectations. This presentation describes why IT teams must learn new architecture paradigms and reshape their reference architecture. Important transformative drivers include: The Now Generation Connected Business Demands Complex Requirements The Long Tail Web 3.0 This is the first presentation in a three part series: Why Reshape Reference Architecture What Reference Architecture Models make sense today How to Reshape Reference Architecture
Recomendados
Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (20)
Destacado
Destacado (19)
Similar a Why Reshape Reference Architecture
Similar a Why Reshape Reference Architecture (20)
Más de Chris Haddad
Más de Chris Haddad (20)
Último
Último (20)
Why Reshape Reference Architecture
- 1. Why Reshape Reference Architecture? Chris Haddad VP Platform Evangelism Twitter @ cobiacomm http://blog.cobia.net/cobiacomm Last Updated: Jan. 2014
- 2. Why Change? Increasingly Complex Requirements http://wso2.com/landing/enabling-the-connected-business
- 3. Join The Now Generation ๏ 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 http://blog.cobia.net/cobiacomm/2013/03/19/accelerating-business-agility-with-app-factory-devops-paas/
- 4. Evolve with The Web Channel Social Community, Context, and Ecosystems 02/07/14 4
- 5. Engage your customers and partners Mobility, Internet of Everything, and Ecosystem Business Models are Transforming The Web
- 6. Situational Context: Traffic {incidents: [ {impacting: false, eventCode: 0, iconURL: "http://...", lat: 38.743999, shortDesc: "Exit ramp closed on I 95...", type: 1, severity: 0, fullDesc: "In NEWINGTON exit ramp closed on I-95 ...", startTime: "2010-02-21T00:14:07", lng: -77.188004, id: "368598263", endTime: "2010-02-27T05:04:19" }, Image source: http://www.directoryofnewyorkcity.com/blog/2009/05/how-to-find-parking-in-new-york-city/ Real-time traffic map: http://www.mapquestapi.com/traffic/
- 7. Increase Development Volume By Enabling The Long Tail
- 8. Become a More Connected Business Reduce interaction friction and cost Accelerate interactions inside and outside the organization Increase engagement and enhance productivity Sense business activity and automatically adapt http://wso2.com/landing/enabling-the-connected-business
- 9. Become more responsive and effective
- 10. What architecture goal-state is required? The next presentation defines the reference architecture target?
- 11. Recommended Reading The Path to Responsive IT ๏ ๏ ๏ http://wso2.com/whitepapers/the-path-to-responsive-it Connected Business Attributes
- 12. About the Author Chris Haddad ๏ ๏ www.linkedin.com/in/cobiacomm/ ๏ http://wso2.com/about/team/leadership/chris-haddad/ Access to Industry Leading Guidance ๏ ๏ ๏ Blog site http://blog.cobia.net/cobiacomm ๏ 12 @cobiacomm on Twitter Slideshare channel http://www.slideshare.net/cobiacomm/
Notas del editor
- Why reshape Reference Architecture? The reference architectures of the past (i.e. client-server, web application, SOA services) are not adequately addressing current business demand, use cases, and expectations. This presentation describes why IT teams must learn new architecture paradigms and reshape their reference architecture. This is the first presentation in a three part series: Why Reshape Reference Architecture What Reference Architecture Models make sense today How to Reshape Reference Architecture
- Why must organizations change their IT reference architecture? The simple answer, IT faces increasingly complex requirements and exceedingly demanding expectations.
- Queuing, waiting, and the status quo doesn’t fit well with today’s now generation and New Enterprise dynamics. Within today’s “Now Generation”, business stakeholders, who drive revenue growth and customer retention, desire to rapidly seize opportunity and market share. They often view IT timeframes and capabilities as a poor match for today’s fast business-pace. IT reference architecture must evolve to support increased business agility. 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 new 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?
- Business teams initially used The Web to present mass marketing content and fairly static information sources. The Web quickly evolved to address Web 2.0 transactional concerns and support e-commerce, social networks, and software as a service. Web 2.0 is centered around static destination sites presenting dynamic content. Mobile, Internet of Things (IoT), and dynamic business environments are driving data and interaction away from aggregating Web2.0 destinations and towards a distributed, decentralized Web 3.0 environment. Web 3.0 is centered around ad-hoc communities who connect in a peer-to-peer (P2P) or machine-to-machine (M2M) topology; and who share data and content created at the edge. Web 3.0 more closely mirrors natural ecosystems where significant interactions occur away from central watering holes (destination sites), and where interactions are driven by contextual data and personalized presentation. In Web 3.0, social interactions are now self-selecting, with mobile users directly interacting via Web 3.0 applications(i.e. snapchat) and APIs.
- Mobility, Internet of Everything, and Ecosystem Business Models are Transforming The Web towards a new interaction model, and businesses must adapt. Without adapting business practices and IT systems towards web API interaction, organizations will be unable to maintain or increase engagement with customers and partners. 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.
- Today’s competitive business knows how to increase productivity and efficiency by adapting to situational context. A situational context example, adjusting commute patterns to address traffic and weather conditions. After we know where we are, and what we are looking to find, situational context may further influence smart API response and positive consumer actions. ----- Image source: http://www.directoryofnewyorkcity.com/blog/2009/05/how-to-find-parking-in-new-york-city/ Real-time traffic map: http://www.mapquestapi.com/traffic/
- Most IT reference architecture models address only the head of the long tail curve [1]. The head on the left represents a few mission-critical applications that service a supermajority of business demand. IT often is geared to only service high-impact, mission critical projects. While mission critical applications ‘run today’s business’ and maintain corporate revenue, a significant opportunity exists in the long tail of application development and innovation. Innovative ideas are often not well served by mission-critical reference architecture. Commonly, mission critical reference architecture is too costly, too resource intensive, or too time consuming to adopt. A large amount of data access, analytics, and workflow requirements are unmet by the one-size-fits-all, tightly allocated IT service model. To maximize business flexibility and agility, New Enterprise IT meets The Long Tail of application and analytic demands with new platforms. The slide illustrates the service scope of Old IT and New Enterprise IT. If we shift the Old IT cutoff to the right, IT can support innovative business ideas and new business opportunities. If more business ideas and opportunities test the market, organizations can remain relevant, fail fast, increase revenue, and enhance income. Extending IT across more Long tail opportunities solves the Innovators dilemma [2]. For more information The Long Tail dynamics, view the Ted video http://www.ted.com/talks/chris_anderson_of_wired_on_tech_s_long_tail.html [1] Apptrepreneurs and Enterprise Application Development , Gartner September 2011ID:G00219046 [2] http://en.wikipedia.org/wiki/The_Innovator's_Dilemma
- A connected business seamlessly integrates people, process, and data across an extended value chain decreases interaction cost Increases business engagement and delivers exceptional productivity automatically adapts business activity in response to market events To learn more, read the following blog posts Connected Business Transformation Connected Business Attributes Connected Business Architecture Realizing Connected Business Architecture
- To meet business demand and expectations, IT must become more responsive and effective. Often outdated processes, tools, and skills inhibit IT’s ability to be a strategic enabler and gain an IT business edge. By adopting a new, Responsive IT delivery model, teams can foster effective business collaboration, responsive iterations, streamlined processes, and no wait states; enabling business to operate at the speed of now. By changing the business-IT dynamic through an innovation focus, business stakeholders start to view IT as a strategic partner.
- Back in 2003-2007, I consulted with many large organizations (i.e. Citigroup, Liberty Mutual, New York Life, Shell, Exxon Mobile, Siemens, Target) pitching Service Oriented Architecture as a competitive advantage, and unfortunately, few teams delivered the hyped benefits. Outside the startup culture, changing processing and outcomes is extremely difficult, and before we pitch the next Big Thing (e.g. Cloud, DevOps, APIs, BigData), we need to incorporate lessons learned into our strategy, roadmap, and execution exercises. During my consulting career, I refined my consulting toolbox, and I have incorporated many successful approaches into the methodology. The next presentation outlines what architectural goal state is required, then we will review how to successfully reshape reference architecture. Image courtesy: http://edcforums.com/threads/the-atwood-collectors-thread-part-2.101226/page-5