Baruch Sadogursky

How we took our server-side application to the Cloud and liked what we got.

Presented in DevOps tools track at DevOps Con Israel 2013

Transcript

1. HOW WE TOOK OUR SERVER- SIDE APPLICATION TO THE CLOUD… …and liked what we got
2.  Where we started  What we did  Paradigm shift Agenda
3. First Things First 3
4. BACKGROUND
5. Who’s talking?
6. Developer who?
7. Developer who?
8. JFrog Where?
9. JFrog Where?
10. JFrog Where?
11. JFrog Where?
12. Artifactory what?
13. Yet Another Java Server App
14. Moving Forward
15. Moving Forward
16. Moving Forward
17. Moving Forward
18. Moving Forward
19. Artifactory SaaS
20. etc. Artifactory SaaS
21. Moving Forward
22. A load of Artifacts!
23. JOURNEY TO THE CLOUD
24. THE *AAS BUZZ
25. * As A Service Self Service Multi-tenant
26. Product Self Service Multi- tenant * aaS GaaE: Google as an Example
27. Product Self Service Multi- tenant * aaS Gmail   Not *aaS, web-app GaaE: Google as an Example
28. Product Self Service Multi- tenant * aaS Gmail   Not *aaS, web-app Google Apps   SaaS GaaE: Google as an Example
29. Product Self Service Multi- tenant * aaS Gmail   Not *aaS, web-app Google Apps   SaaS Google App Engine   PaaS GaaE: Google as an Example
30. Product Self Service Multi- tenant * aaS Gmail   Not *aaS, web-app Google Apps   SaaS Google App Engine   PaaS Google Compute Engine   IaaS GaaE: Google as an Example
31. Product Self Service Multi- tenant * aaS AaaE: Amazon as an Example
32. Product Self Service Multi- tenant * aaS Amazon store   Not *aaS, web-app AaaE: Amazon as an Example
33. Product Self Service Multi- tenant * aaS Amazon store   Not *aaS, web-app aStore   SaaS AaaE: Amazon as an Example
34. Product Self Service Multi- tenant * aaS Amazon store   Not *aaS, web-app aStore   SaaS Amazon Elastic Beanstalk   PaaS AaaE: Amazon as an Example
35. Product Self Service Multi- tenant * aaS Amazon store   Not *aaS, web-app aStore   SaaS Amazon Elastic Beanstalk   PaaS Amazon Elastic Cloud   IaaS AaaE: Amazon as an Example
36.  Multi-tenancy  Platform selection > PaaS or IaaS  DB schema updates The SaaS Pains - Overview
37. Multi-tenancy
38. Java 9 Already!
39.  Two-year release cycle  Java 7: 07 2011  Java 8: 09 2013  Java 9: Late 2015 Wait for it?!
40.  Two-year release cycle  Java 7: 07 2011  Java 8: 09 2013  Java 9: Late 2015 Wait for it?!
41. Multi Tenancy Types Muli-tenancy Type
42. Multi Tenancy Types Muli-tenancy Type Data Separation
43. Multi Tenancy Types Muli-tenancy Type Data Separation Application Separation
44. Multi Tenancy Types Muli-tenancy Type Data Separation Application Separation Process Separation
45. GaaE for Multi Tenancy Types Product Muli-tenancy Type
46. GaaE for Multi Tenancy Types Product Muli-tenancy Type Google Apps Data Separation
47. GaaE for Multi Tenancy Types Product Muli-tenancy Type Google Apps Data Separation Google App Engine Application Separation
48. GaaE for Multi Tenancy Types Product Muli-tenancy Type Google Apps Data Separation Google App Engine Application Separation Google Compute Engine Process Separation
49. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Comparing the Strategies
50. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Comparing the Strategies 
51. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Separating processes  No shared state  Simple transition from existing  JVM per tenant! Comparing the Strategies 
52. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Separating processes  No shared state  Simple transition from existing  JVM per tenant! Comparing the Strategies  
53. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Separating application  No shared state  Or is it?  Simple transition from existing Separating processes  No shared state  Simple transition from existing  JVM per tenant! Comparing the Strategies  
54. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Separating application  No shared state  Or is it?  Simple transition from existing Separating processes  No shared state  Simple transition from existing  JVM per tenant! Comparing the Strategies   
55. Strategy Pros Cons Separating data  Normal Java Application  Manual state separation  Complicated and critical schema Separating application  No shared state  Or is it?  Simple transition from existing  Stay tuned… Separating processes  No shared state  Simple transition from existing  JVM per tenant! Comparing the Strategies   
56. Separate Application: Tomcat Root ┌── lib ├── webapps │ ├── customer-name │ ├── other-customer-name │ └── many other customers └── other dirs (bin, conf, log, etc)
57. Separate Application
58. Separate Application
59. Too… many… classes…
60. Reuse!
61. Is it even possible?
62. Is it even possible?
63. THE QUEST FOR SHARED LIBRARIES
64. Spring Framework
65. public class AppCtxHolder implements ApplicationContextAware { private static ApplicationContext ctx; public AppCtxHolder() { } public void setApplicationContext(ApplicationContext applicationContext) { ctx = applicationContext; } public static ApplicationContext getApplicationContext() { return ctx; } } Spring Framework
66. public class AppCtxHolder implements ApplicationContextAware { private static ApplicationContext ctx; public AppCtxHolder() { } public void setApplicationContext(ApplicationContext applicationContext) { ctx = applicationContext; } public static ApplicationContext getApplicationContext() { return ctx; } } Spring Framework
67. public class AppCtxHolder implements ApplicationContextAware { private static ApplicationContext ctx; public AppCtxHolder() { } public void setApplicationContext(ApplicationContext applicationContext) { ctx = applicationContext; } public static ApplicationContext getApplicationContext() { return ctx; } } Spring Framework
68. Apache Wicket
69. Thread Pools
70. Logger
71. Logger
72. CATS Software
73. Jackrabbit
74. Heap-wide Caches
75. THE QUEST FOR SHARED LIBRARIES: RESULTS
76. ┌── lib ├── webapps │ ├── customer-name │ │ ├── favicon.ico │ │ ├── META-INF │ │ └── WEB-INF │ │ ├── web.xml │ │ └── classes │ │ └── DUMMY.TXT │ ├── other-customer-name │ │ ├── favicon.ico │ │ │ └── META-INF │ │ └── WEB-INF │ └── many other customers └── other dirs (bin, conf, log, etc) Tomcat Root – Where’s the JARs?
77. ┌── lib ├── webapps │ ├── customer-name │ │ ├── favicon.ico │ │ ├── META-INF │ │ └── WEB-INF │ │ ├── web.xml │ │ └── classes │ │ └── DUMMY.TXT │ ├── other-customer-name │ │ ├── favicon.ico │ │ │ └── META-INF │ │ └── WEB-INF │ └── many other customers └── other dirs (bin, conf, log, etc) Tomcat Root – Where’s the JARs?
78. ┌── lib ├── webapps │ ├── customer-name │ │ ├── favicon.ico │ │ ├── META-INF │ │ └── WEB-INF │ │ ├── web.xml │ │ └── classes │ │ └── DUMMY.TXT │ ├── other-customer-name │ │ ├── favicon.ico │ │ │ └── META-INF │ │ └── WEB-INF │ └── many other customers └── other dirs (bin, conf, log, etc) Tomcat Root – Where’s the JARs?
79. ┌── lib │ ├── artifactory │ │ ├── artifactory-*.jar │ │ ├── jackrabbit-core-jfrog-2.2.8c.jar │ │ ├── spring-core-3.1.1.RELEASE.jar │ │ ├── wicket-core-1.5.3.jar │ │ └── other jars │ ├── catalina.jar │ ├── servlet-api.jar │ └── other jars ├── webapps └── other dirs (bin, conf, log, etc) Tomcat Root – In Global Lib!
80. ┌── lib │ ├── artifactory │ │ ├── artifactory-*.jar │ │ ├── jackrabbit-core-jfrog-2.2.8c.jar │ │ ├── spring-core-3.1.1.RELEASE.jar │ │ ├── wicket-core-1.5.3.jar │ │ └── other jars │ ├── catalina.jar │ ├── servlet-api.jar │ └── other jars ├── webapps └── other dirs (bin, conf, log, etc) Tomcat Root – In Global Lib!
81. ┌── lib │ ├── artifactory │ │ ├── artifactory-*.jar │ │ ├── jackrabbit-core-jfrog-2.2.8c.jar │ │ ├── spring-core-3.1.1.RELEASE.jar │ │ ├── wicket-core-1.5.3.jar │ │ └── other jars │ ├── catalina.jar │ ├── servlet-api.jar │ └── other jars ├── webapps └── other dirs (bin, conf, log, etc) Tomcat Root – In Global Lib!
82. ┌── lib │ ├── artifactory │ │ ├── artifactory-*.jar │ │ ├── jackrabbit-core-jfrog-2.2.8c.jar │ │ ├── spring-core-3.1.1.RELEASE.jar │ │ ├── wicket-core-1.5.3.jar │ │ └── other jars │ ├── catalina.jar │ ├── servlet-api.jar │ └── other jars ├── webapps └── other dirs (bin, conf, log, etc) Tomcat Root – In Global Lib!
83. ┌── lib │ ├── artifactory │ │ ├── artifactory-*.jar │ │ ├── jackrabbit-core-jfrog-2.2.8c.jar │ │ ├── spring-core-3.1.1.RELEASE.jar │ │ ├── wicket-core-1.5.3.jar │ │ └── other jars │ ├── catalina.jar │ ├── servlet-api.jar │ └── other jars ├── webapps └── other dirs (bin, conf, log, etc) Tomcat Root – In Global Lib!
84. PaaS or IaaS?
85. PaaS or IaaS?
86. What was it about DB upgrade?
87. THE DEVOPS
88. Providing Self Service
89. Separating Concerns
90. Outcome: DevOps
91. THE PROCESS
92. Diversity
93. Recursive Slide (w. baby picture)
94. Right Tools for the Job
95. Right Tools for the Job
96. Right Tools for the Job
97. THE PARADIGM SHIFT
98. Reversing the Cycle
99. Reversing the Cycle
100. Consequences