Pain and Gain of Service Oriented Architecture

1. Pain & Gain: Service Oriented Architecture Kiran Patel, Software Engineer @kpatel79, kpatel@shutterstock.com

2. In 5 Years… 50 People 10M Images 1M Videos 2 Products 5 Languages 4 Currencies 1 Office

3. In 5 Years… 650 People 60M Images 3M Videos 8 Products 20 Languages 9 Currencies 11 Offices

4. Today... 1.3M Active Users Sell 4 Images/sec Received 50K Images/day Received 3K Videos/day

5. Focused on volume & unbiased search experience. http://www.shutterstock.com/labs/

6. Scale

7. It Just doesn’t work

8. Re-think

9. Re-think Development Practices Products/Tools Organizational Structure Customer Support Data & Infrastructure Tools

14. More Time Building

15. Less Time Firefighting!

16. Huge paradigm shift in the way software is being built today...

17. First Customer Ship! Back In the Day… Requirements Design Development Verification/QA Release

18. First Customer Ship! Back In the Day… Requirements Design Development Verification/QA Release Costly, Time & Resource Intensive 1st Customer feedback

19. Validate our Idea ______and ______

20. Validate our Idea Quickly and ______

21. Validate our Idea Quickly and Cheaply

22. It's Okay to Do Things That Don’t Scale

23. Idea

24. Idea ProductData

25. Idea ProductData

26. Idea ProductData Spin it at your maximum speed!

27. Idea ProductData Spin it at your maximum speed! Build

28. Idea ProductData Spin it at your maximum speed! Build Measure

29. Idea ProductData Spin it at your maximum speed! Build Measure Learn

30. Time to Think about Scale

31. Routing Data Store Business Logic Presentation

32. Team 1 Team 2 Team 3 Data Store Business Logic Presentation Routing Team 4

33. Routing Presentation Logic Storage MySQLPerl/PHP/Ruby/Python

34. Challenges

35. People Productivity

36. Your Site is down…

37. People Productivity Respond to Business needs

38. People Productivity Respond to Business needs System resiliency

39. Goals

40. Goals Increase Engineers Productivity

41. Goals Build around business capabilities

42. Goals Not just a Web-stack

43. Goals Isolate Failure

44. Goals Isolate Responsibilities

45. Goals Independent Deployable

46. Goals Easily Testable

47. Goals Site Speed

48. Goals Decentralized Data Management

49. Goals Infrastructure Automation

50. Goals Design for failure

51. Shared reusable Distributed

52. Transition Plan

53. v  Develop a formal SOA Program Transition Plan

54. v  Develop a formal SOA Program v  Establish a SOA Competency Teams Transition Plan

55. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA Transition Plan

56. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA v  Develop SOA reference architecture Transition Plan

57. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA v  Develop SOA reference architecture v  Establish a training plan for staff competency Transition Plan

58. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA v  Develop SOA reference architecture v  Establish a training plan for staff competency v  Develop SOA Quality Assurance policies and procedures Transition Plan

59. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA v  Develop SOA reference architecture v  Establish a training plan for staff competency v  Develop SOA Quality Assurance policies and procedures v  Deploy Infrastructure Monitoring and alerting tools Transition Plan

60. v  Develop a formal SOA Program v  Establish a SOA Competency Teams v  Adjust current architecture and methodology to adjust for SOA v  Develop SOA reference architecture v  Establish a training plan for staff competency v  Develop SOA Quality Assurance policies and procedures v  Deploy Infrastructure Monitoring and alerting tools v  Transition to SOA iteratively Transition Plan

61. Accounts Search Commerce Translation Media Photo API Commerce API Premier API Offset API Services Layer Orchestration Layer Shutterstock.com premier.shutterstock.com offset.com

62. Team 4 (Service A) Team 5 (Service B) Team 5 (Service C) Team 1 (Premier) Team 2 (Shutterstock) Team 3 (Offset)

63. Plan your Quality Assurance strategy early. Degrade your system gracefully.

64. Plan your Quality Assurance strategy early. Degrade your system gracefully. Make very small changes

65. Plan your Quality Assurance strategy early. Degrade your system gracefully. Make very small changes Test Everything

66. Plan your Quality Assurance strategy early. Degrade your system gracefully. Make very small changes Test Everything Degrade your system gracefully

67. Q&A

68. Thank y u Feedback Please : https://joind.in/talk/view/14731

Pain and Gain of Service Oriented Architecture

You are reading a preview.

Check these out next

Pain and Gain of Service Oriented Architecture

More Related Content

Slideshows for you (20)

Similar to Pain and Gain of Service Oriented Architecture (20)

Recently uploaded (20)