1 / 28

Global Company SOA Landscape Recommendations

Global Company SOA Landscape Recommendations. By eFlix Architects Group, LLC. eFlix Architects Group, LLC. EAG Team Members Andrew Bond – Principal Design Architect Jai Mathaiyan – Chief Technical Architect Oleg Shnayderman – Distinguished Lead Architect.

chana
Download Presentation

Global Company SOA Landscape Recommendations

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Global CompanySOA Landscape Recommendations By eFlix Architects Group, LLC

  2. eFlix Architects Group, LLC EAG Team Members • Andrew Bond – Principal Design Architect • Jai Mathaiyan – Chief Technical Architect • Oleg Shnayderman – Distinguished Lead Architect

  3. eFlix Architects Group, LLCAbout the group Formed in 2010, we are a dynamic team of professionals, working in close collaboration to deliver custom SOA software projects to a variety of specialized clientele. With years of experience working with a variety of corporations across the spectrum of industries and markets, we deliver solutions that exceed customer expectations. We specialize in: • Assessment of existing IT architectures • Identify SOA solutions that provide maximum value • SOA migration planning and execution • Implementing agile software development methodologies

  4. eFlix Architects Group, LLC Past projects, references • 2011 – San Jose Mineta Airport – Provided SOA consulting as part of a $6.5 million upgrade from the existing Sperry Univac 1100/2200 based Airport Management System (AMS) to a modern SOA infrastructure allowing Federal TSA system integration, flexible/scalable IT management, coordinated flight information, scheduling and airline database integration. • 2010 – eJinni, a project to design a system for small businesses that loan, rent and sell entertainment media and equipment from a retail store, to help them compete with features offered by larger and online competitors, with the flexibility to include online shopping and order shipment options. Incorporating modern SOA techniques, with modular, flexible design allowing quick analysis and debugging of defects, and technical issues

  5. Agenda • Overview • Current Landscape • Future Landscape • Governance Recommendations • Appendix (*) (*) Technical Details for IT and Development Team

  6. Purpose & Scope • Analyze existing systems and design interaction behavior between the Global Company, Magento store and Cyber security to build a single service oriented application.

  7. Purpose & Scope - Business goals • Credit card authorization and payment should be automated by integrating with Cyber Security. However credits will continue to be manual. • Reuse the Magneto's storefront with Global company's UI. However the brand names have to be separate because Magento could possibly sell products by itself in future • Orders have to be fulfilled and shipped automatically. Provision to apply certain rules on orders and process them manually if required. For e.g. orders > $1000 should be processed manually. • Add UPS shipment service for automated shipping. • Integration with Twitter for sales announcements. • RAM, Disk storage and Environments can be increased/decreased automatically with integration with Cloudshare services.

  8. Purpose & Scope - Technology goals • Global company's current investment in Oracle SOA should be kept. However recommendations for service inventory and upgrade to 11g is desirable. • The Global company's SOA services should be used for Cloudshare's credit card processing and recurring billing • Replace the current store based tax calculation with online real-time shipment and tax calculation.

  9. Overview of Business Units • Global Business model is online sales, a multi-level marketing as well as distributor of multiple consumer goods. Estimated annual revenue (sales): $8 000 000 000.00 • Magento Magento is a feature-rich, professional open-source eCommerce solution that offers merchants complete flexibility and control over the look, content, and functionality of their online store. Magento’s intuitive administration interface contains powerful marketing, merchandising and content management tools to give merchants the power to create sites that are tailored to their unique business needs. Completely scalable and backed by an extensive support network, Magento offers companies the ultimate eCommerce solution. [http://www.magentocommerce.com/company/] Estimated annual revenue (sales): $100 000 000.00 • “CloudShare is a cloud computing company that provides unprecedented flexibility and ease of use for moving enterprise IT systems and applications—unchanged—into the cloud.” (http://www.cloudshare.com/about_cloudshare/about_cloudshare.aspx) CloudShare is a cloud computing provider which enables users to create, replicate and share fully functional IT environments in the Cloud (http://en.wikipedia.org/wiki/CloudShare) Estimated annual Revenue (Sales): $2 000 000 000.00 • Note: describe what each business does and est. annual revenue (make numbers for revenue!)

  10. Users Interviewed • Customer Support • Operation

  11. Customer Support Outline of Findings • Global’s customer support group is located in high-wage, high-cost region (SF Bay area), while Magento support is off-shore (Bangalore) • The support process requires relatively low-medium skilled workers, requiring about 6 months train-up period for a worker to be fully productive • Recommendation – Workforce restructuring of Global Customer Service staff after a 6 month integration period where the Magento staff can prepare and train-up

  12. OperationsOutline of Findings • Magento and Global Operation staff are both currently located in high-wage, high-cost region (SF Bay area) • Recommendation Magento and Global Operations staff should remain in place for the next 1-2 fiscal years, at least until after a full integration of Magento and Global systems are complete, and the architecture for migration of IT platforms to CloudShare is complete.

  13. Current Landscape

  14. As-Is Business Processes • Diagrams (about a few slides each as needed): • Use Case Overview Diagram • Global & Magento Business Process Model • Order Fulfillment • Order Returns • Back Office Systems • CloudShare Business Process Model • New Subscription • Payment Processing • Use Case Scenarios • End-to-end sequence diagrams for key Use Cases

  15. As-Is - Magento • Use case overview diagram

  16. As-Is Magento • SOA Landscape

  17. As-Is Magento • List of Core service • Catalog Service • Admin Service • Shopping Cart • Order Service • Fulfillment • Returns

  18. Magento Order Processing Browser (IE) Shopping Cart Cyber Source Admin Back office Customer Place order Buy Sign Order For HOP Confirm Page Pay Verify Order Payment Page Enter CC# & Check-Out Check-Out (Note: Post to HOP) Route to Processor Authorize Order Transaction Result & Signature Redirect Verify Transaction Signature Receipt Page Ship order

  19. As-Is Magento • Sample Order Booking wsdl

  20. As-Is Magento • Sample Order Return wsdl

  21. As-Is SOA Landscape • SOA Architecture Logical Component Diagram • List of Core Services and Key Contracts • Highlight “hot spots” where changes are needed • Identify Key Challenges • Note: stick to problem definition here. Do not discuss solutions yet – that’s for the next section.

  22. Future Landscape

  23. To-Be Business Processes • Diagrams (highlight changes in a different color): • Use Case Overview Diagram • Global & Magento Business Process Model • Order Fulfillment • Order Returns • Back Office Systems • CloudShare Business Process Model • New Subscription • Payment Processing • Use Case Scenarios • End-to-end sequence diagrams for key Use Cases

  24. To-Be SOA Landscape • SOA Architecture Logical Component Diagram • List of New Services and Contracts • Highlight Key Changes which addressesthe Challenges identified in As-Is State • Include: • Integration of PCI Compliant Payment Service • Integration of new shipping service(s) • Other recommended services • Note: don’t put details here (put them in the appendix)

  25. Governance Recommendations

  26. Governance Notes: • Management Policy Changes • Policy Table • Recommended Service Granularity Approach(Ref: SOA Governance Patterns) • PCI Compliance Validation • SOA Architecture Maintenance • Web Service Versioning of Key Contracts (Ref: Service Life Cycle) • Change Management around Data Models • Infrastructure Upgrade Roadmap • Move to Hybrid Cloud? • Upgrade to SOA Suite 11g

  27. Appendix

  28. Appendix: • Include • Any Design Design Details (i.e. explain “why”) • Architecture Prototypes (that support recommendations) • Web Service Contracts (request/response examples) used in analysis leading to recommendations • UI Screenshots of recommended changes • Etc…

More Related