The document discusses moving a Java server application to the cloud by deploying it on Artifactory's Software-as-a-Service (SaaS) platform. Some benefits mentioned include not having to maintain the server, receiving fanatical technical support, and always having the latest version. A potential downside is not being able to deploy custom plugins. It also describes the large amount of artifacts and data stored on Artifactory and how it can easily scale to support increasing usage and storage needs.

1. HOW WE TOOK OUR SERVER-
SIDE JAVA APPLICATION TO THE
CLOUDand liked what we got

2. WHO’S TALKING?
linkd.in/jbaruch

3. Developer who?
3

4. Developer who?
4

5. WHAT FROG?

6. WHAT FROG?

7. WHAT FROG?

8. WHAT FROG?

9. WHAT FROG?

10. WHAT FROG?

11. One more thing!
bit.ly/1bDaHiD
JUC Israel - July 16, 2014

12. SO…

13. First things First.

15. Poll time!
I use binary repository:

16. Poll time!
I use binary repository:
 Naturally,Artifactory!

17. Poll time!
I use binary repository:
 Naturally,Artifactory!
 Shame on me,
but still Nexus…

18. Poll time!
I use binary repository:
 Naturally,Artifactory!
 Shame on me,
but still Nexus…
 I don’t like features, I use Archiva

19. Poll time!
I use binary repository:
 Naturally,Artifactory!
 Shame on me,
but still Nexus…
 I don’t like features, I use Archiva
 I am a caveman, binary what?

20. In the beginning…

21. In the beginning…

22. Yet Another Java Server App

23. Rabbit?!

25. Checksum storage

26. Checksum storage

27. Checksum storage

28. Checksum storage

29. Append Only, GC-ed

31. Artifactory 3 – 10 times faster!
(Not bastards)

33. Moving Forward

34. Moving Forward

35. Moving Forward

36. Moving Forward

37. Moving Forward

38. Artifactory SaaS
etc.

40. What you like about it:

41. What you like about it:
– No need to maintain the server

42. What you like about it:
– No need to maintain the server
– Fanatic tech support

43. What you like about it:
– No need to maintain the server
– Fanatic tech support
– Always up to date!

44. What you like about it:
– No need to maintain the server
– Fanatic tech support
– Always up to date!
What you don’t like about it:

45. What you like about it:
– No need to maintain the server
– Fanatic tech support
– Always up to date!
What you don’t like about it:
– Can’t deploy your own plugins!

46. What you like about it:
– No need to maintain the server
– Fanatic tech support
– Always up to date!
What you don’t like about it:
– Can’t deploy your own plugins!

47. What you like about it:
– No need to maintain the server
– Fanatic tech support
– Always up to date!
What you don’t like about it:
– Can’t deploy your own plugins!

48. Artifactory SaaS
etc.

49. Sh.t-load of artifacts!

50. Terabytes.
FEBRUARY

51. Terabytes.
FEBRUARY
MAY

52. Terabytes.
FEBRUARY
MAY
AUGUST

53. Terabytes.
AUGUST
MAY
JANUARY

54. Bring Them On!

55. To The Cloud

56. Bullshit Bingo

57. Much ado about *aaS

58. * As A Service

59. * As A Service
Self-service

60. * As A Service
Self-service Multi-tenancy

61. Controversial example ahead!
You might find it inaccurate.
If you are annoyed by that feeling,
try to remember – it’s just an
example.

62. GaaE: Google as an Example
Product Self
Service
Multi-
tenant
* aaS

63. GaaE: Google as an Example
Product Self
Service
Multi-
tenant
* aaS
Gmail
  Not *aaS,
web-app

64. GaaE: Google as an Example
Product Self
Service
Multi-
tenant
* aaS
Gmail
  Not *aaS,
web-app
Google Apps
  SaaS

65. GaaE: Google as an Example
Product Self
Service
Multi-
tenant
* aaS
Gmail
  Not *aaS,
web-app
Google Apps
  SaaS
Google App
Engine
  PaaS

66. GaaE: Google as an Example
Product Self
Service
Multi-
tenant
* aaS
Gmail
  Not *aaS,
web-app
Google Apps
  SaaS
Google App
Engine
  PaaS
Google Compute Engine
Engine
  IaaS

67. AaaE: Amazon as an Example
Product Self
Service
Multi-
tenant
* aaS

68. AaaE: Amazon as an Example
Product Self
Service
Multi-
tenant
* aaS
Amazon store
  Not *aaS,
web-app

69. AaaE: Amazon as an Example
Product Self
Service
Multi-
tenant
* aaS
Amazon store
  Not *aaS,
web-app
aStore
  SaaS

70. AaaE: Amazon as an Example
Product Self
Service
Multi-
tenant
* aaS
Amazon store
  Not *aaS,
web-app
aStore
  SaaS
Amazon Elastic
Beantalk
  PaaS

71. AaaE: Amazon as an Example
Product Self
Service
Multi-
tenant
* aaS
Amazon store
  Not *aaS,
web-app
aStore
  SaaS
Amazon Elastic
Beantalk
  PaaS
Amazon Elastic Cloud
  IaaS

72. SaaS pains

73. Multi-tenancy

75. Looks good! When to expect?

76. Extrapolate
This

77. Given:
Release Java 7 07/2011
Release Java 8 12/2012

78. Given:
Release Java 7 07/2011
Release Java 8 12/2012
Find:
Release Java 9?

80. Java 8: 12/2012

81. Java 8: 12/2012
-
Java 7: 07/2011

82. Java 8: 12/2012
-
Java 7: 07/2011
=
15 Months cycle

83. Java 8: 12/2012
-
Java 7: 07/2011
=
15 Months cycle
conclusion: Java 9: 05/2013

84. Java 8: 12/2012
-
Java 7: 07/2011
=
15 Months cycle
conclusion: Java 9: 05/2013
It’s almost a year ago!
Oh, wait…
Java 8 is not out yet!

85. Observation: When Mark
writes about trains it
means release delay

86. Here you go:

87. Java 7: 07/2011

88. Java 7: 07/2011
+ 24 Months =

89. Java 7: 07/2011
+ 24 Months =
Java 8: 07/2013

90. You wish!

91. Java 7: 07/2011
+ 24 Months =
Java 8: 07/2013

92. Java 7: 07/2011
+ 24 Months =
Java 8: 01/2014
Whatever mark says

93. Java 7: 07/2011
+ 24 Months =
Java 8: 01/2014
+ 24 Months =
Java 9: 01/2016
Whatever mark says

94. You think this is it?

95. Java 7: 07/2011
+ 24 Months =
Java 8: 03/2014
Whatever mark says

96. Java 7: 07/2011
+ 24 Months =
Java 8: 03/2014
+ 24 Months =
Whatever mark says

97. Java 7: 07/2011
+ 24 Months =
Java 8: 03/2014
+ 24 Months =
Java 9: 03/2016
Whatever mark says

98. Java 7: 07/2011
+ 24 Months =
Java 8: 03/2014
+ 24 Months =
Java 9: 03/2016
(if no more train blog posts)
Whatever mark says

99. Java 7: 07/2011
+ 24 месяца =
Java 8: 03/2014
+ 24 месяца =
Java 9: 03/2016
(Если не будет больше
постов про поезд)
Сколько Марк скажет

101. Multi-tenancy types
Multi-tenancy Type

102. Multi-tenancy types
Multi-tenancy Type
Data Separation

103. Multi-tenancy types
Multi-tenancy Type
Data Separation
Application Separation

104. Multi-tenancy types
Multi-tenancy Type
Data Separation
Application Separation
Process Separation

105. GaaE for Multi Tenancy types
Product Multi-tenancy Type

106. GaaE for Multi Tenancy types
Product Multi-tenancy Type
Google Apps Data Separation

107. GaaE for Multi Tenancy types
Product Multi-tenancy Type
Google Apps Data Separation
Google App Engine Application Separation

108. GaaE for Multi Tenancy types
Product Multi-tenancy Type
Google Apps Data Separation
Google App Engine Application Separation
Google Compute Engine Process Separation

109. Strategy Pros Cons
Separating data
Separating
application
Separating processes
Let’s compare!

110. Strategy Pros Cons
Separating data  Normal Java Application
Separating
application
Separating processes
Let’s compare!

111. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
Separating processes
Let’s compare!

112. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
Separating processes
Let’s compare!


113. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
Separating processes  No shared state
 Simple transition from existing
Let’s compare!


114. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
Separating processes  No shared state
 Simple transition from existing
 JVM per tenant!
Let’s compare!


115. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
Separating processes  No shared state
 Simple transition from existing
 JVM per tenant!
Let’s compare!



116. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
 No shared state
 Simple transition from existing
Separating processes  No shared state
 Simple transition from existing
 JVM per tenant!
Let’s compare!



117. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
 No shared state
 Simple transition from existing
Separating processes  No shared state
 Simple transition from existing
 JVM per tenant!
Let’s compare!




118. Strategy Pros Cons
Separating data  Normal Java Application  Manual state separation
 Complicated and critical
schema
Separating
application
 No shared state
 Simple transition from existing
 Stay tuned…
Separating processes  No shared state
 Simple transition from existing
 JVM per tenant!
Let’s compare!




119. Separate WARs: Tomcat Root
┌── lib
├── webapps
│ ├── customer-name
│ ├── other-customer-name
│ └── many other customers
└── other dirs (bin, conf, log, etc)

120. Separate WARs

121. Separate WARs

122. Separate WARs
That was the
PermGen.
Yup.

123. We love our toys

124. We love our toys
Artifactory-3.0.1.warwebappWEB-INFlib$du –m
51 .

126. To the common ClassLoader!

127. Will it work?
_________

128. Will it work?
‹ Object state
_________

129. Will it work?
‹ Object state
‹ Static state
_________

130. “Static State Quest I”
(Sierra, who else?)

131. Spring Framework

132. The Evil
App. Context Holder Pattern

133. The Evil
App. Context Holder Pattern
public class AppCtxHolder implements ApplicationContextAware {
private static ApplicationContext ctx;
public AppCtxHolder() { }
public void setApplicationContext(ApplicationContext applicationContext) {
ctx = applicationContext;
}
public static ApplicationContext getApplicationContext() {
return ctx;
}
}

134. The Evil
App. Context Holder Pattern
public class AppCtxHolder implements ApplicationContextAware {
private static ApplicationContext ctx;
public AppCtxHolder() { }
public void setApplicationContext(ApplicationContext applicationContext) {
ctx = applicationContext;
}
public static ApplicationContext getApplicationContext() {
return ctx;
}
}

135. The Evil
App. Context Holder Pattern
public class AppCtxHolder implements ApplicationContextAware {
private static ApplicationContext ctx;
public AppCtxHolder() { }
public void setApplicationContext(ApplicationContext applicationContext) {
ctx = applicationContext;
}
public static ApplicationContext getApplicationContext() {
return ctx;
}
}

136. Apache Wicket

137. Apache Wicket
We love Wicket,
cause it allows
people who hate
UI development
to develop a UI,
which people
don’t hate

138. Apache Wicket

139. Logger

140. Logger

141. CATS Software

142. Jackrabbit

143. Jackrabbit

144. Heap-wide Caches

145. Don’t actually have
to read this

146. Tomcat Root – Where are the
JARs?┌── 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)

147. Tomcat Root – Where are the
JARs?┌── 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)

148. Tomcat Root – Where are the
JARs?┌── 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)

149. Tomcat Root – Global lib folder
┌── 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)

150. Tomcat Root – Global lib folder
┌── 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)

151. Tomcat Root – Global lib folder
┌── 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)

152. Tomcat Root – Global lib folder
┌── 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)

153. Tomcat Root – Global lib folder
┌── 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)

154. PaaS or IaaS?

155. PaaS or IaaS?

156. Self-Service?

157. Prevent the Fork!

160. The process

164. Artifactory is built with
Artifactory!

165. The Process

166. The Process

167. The Process

168. The Process

169. The Process

170. The Process

171. The Process

172. The Process

173. It’s all about right tools

174. Also right tools

175. The Paradigm…

176. Now we do it the other way around

177. Actually, now we do it the right way!

178. And we love what we got!

179. And we love what we got!

180. NO, THANK YOU!