Software is changing the world. In today’s ever changing technological advancements, its very important for businesses to have their long-term vision and business strategies aligned with their business process. Organizations are looking into a software solutions which cater their current as well as future needs. The recent trend is to break one size fits-all monolithic software applications into small domain specific micro services.

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

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

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

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

13. 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

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

24. Idea

25. Idea
ProductData

26. Idea
ProductData

27. Idea
ProductData
Spin it at your
maximum speed!

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

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

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

31. Time to Think
about Scale

33. Routing
Data Store
Business
Logic
Presentation

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

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

36. Challenges

37. People
Productivity

38. Your Site is down…

39. People
Productivity
Respond to
Business
needs

40. People
Productivity
Respond to
Business
needs
System
resiliency

41. Goals

42. Goals
Increase Engineers
Productivity

43. Goals
Build around
business capabilities

44. Goals
Not just a Web-stack

45. Goals
Isolate Failure

46. Goals
Isolate
Responsibilities

47. Goals
Independent
Deployable

48. Goals
Easily Testable

49. Goals
Site Speed

50. Goals
Decentralized Data
Management

51. Goals
Infrastructure
Automation

52. Goals
Design for failure

53. Shared reusable Distributed

54. Transition Plan

55. v Develop a formal SOA Program
Transition Plan

56. v Develop a formal SOA Program
v Establish a SOA Competency Teams
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
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
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
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
Transition Plan

61. 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

62. 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

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

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

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

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

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

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

70. Q&A

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