In this talk, we’ll go into excruciating technical detail about building a greenfield, massively scalable cloud service. As many of us are assembling open source and SaaS components to power our next generation applications, it seems as easy as choosing the leaders in each space and just gluing them together using APIs. This sentiment couldn’t possibly be more wrong. Along the path to constructing a scalable cloud service, there are many options and critical decisions to take. This talk covers our missteps and our revised successful choices of building Bintray. We will share our challenges and how it affected our approach towards issues like: segmenting the system; supporting horizontal scaling; physical vs virtual hosts; handling cross data center deployments; managing redundancy; and supporting a cloud-based development environment. Many of these approaches you can replicate in your own construction of your next cloud solution.

1. Building a Massively Scalable
Cloud Service
from the Grounds Up

2. About your speaker
linkd.in/jbaruch
stackoverflow.com/users/402053/jbaruch

3. What Frog?

4. What Frog?

5. What Frog?

6. What Frog?

7. So…

8. Some Numbers
liftoff + 26 months

9. Some Numbers
liftoff + 26 months
Repositories 36K

10. Some Numbers
liftoff + 26 months
Repositories 36K
Packages 120K

11. Some Numbers
liftoff + 26 months
Repositories 36K
Packages 120K
Requests 1.7 B/Month

14. Requirements

15. Requirements
– Download binaries

16. Requirements
– Download binaries
– Web Front

17. Requirements
– Download binaries
– Web FRONT
– REST API

18. Requirements
– Download binaries
– Web FRONt
– REST API
– Backend services

19. We know developers

20. %new_sexy_lang% community

21. Not our fault! AWS failed again!

22. Downloads must…

23. Web application must…

24. Backend Services must…

25. Choose your battles...

26. Non-Func. Requirements

27. Non-Func. Requirements
Requirement RPS Availability

28. Non-Func. Requirements
Requirement RPS Availability
Download 10K Always

29. Non-Func. Requirements
Requirement RPS Availability
Download 10K Always
Interaction 200 Almost always

30. Non-Func. Requirements
Requirement RPS Availability
Download 10K Always
Interaction 200 Almost always
Services 10 Most of the time

31. DOWNLOAD SERVICE

33. No Servlets here

42. Deduplication by Checksum
File A: 46b34
File B: a64ff7
/user-a/repo-z/package-y/file-x
/org-c/repo-m/package-n/file-k
/user-m/repo-w/package-t/file-f

43. Flat blobs storage
File A: 46b34
File B: a64ff7

48. /user-m/repo-w/package-t/file-f
Mapping

52. WEB FRONT

59. WEB FRONT
UI

62. Requirements

63. Requirements
– Rapid Application Development

64. Requirements
– Rapid Application Development
– Flexible schema

65. Requirements
– Rapid Application Development
– Flexible schema
– Java Background

66. Requirements
– Rapid Application Development
– Flexible schema
– Java Background
– Stateless

68. Why don’t you just use...?
Framework Why not?

69. Why don’t you just use...?
Framework Why not?
Angular.js Ember.js ж.js Maturity

70. Why don’t you just use...?
Framework Why not?
Angular.js Ember.js ж.js Maturity
Wicket State

71. Why don’t you just use...?
Framework Why not?
Angular.js Ember.js ж.js Maturity
Wicket State
JSF Model

72. Why don’t you just use...?
Framework Why not?
Angular.js Ember.js ж.js Maturity
Wicket State
JSF Model
Non-java No java bg

78. And look what happened:

79. And look what happened:

81. Grails minor update

83. WEB FRONT
Data Model

85. Remember?

90. Grails means
Gorm!

91. Gorm MongoDB plugin

92. WEB FRONT
Search

93. Search

94. 2 types of search
Full Text Search Structured Search

95. 2 types of search
Full Text Search Structured Search

99. Executive summary
Framework Why not?

100. Executive summary
Framework Why not?
Lucene/compass Only embedded, resource
guzzler

101. Executive summary
Framework Why not?
Lucene/compass Only embedded, resource
guzzler
solr Bad grails integration

102. Executive summary
Framework Why not?
Lucene/compass Only embedded, resource
guzzler
solr Bad grails integration
sphynx Painful incremental index

106. vs.

107. vs.

108. You ask

109. ElasticSearch answers

111. WEB FRONT
Additional Services: Indexing, Stats, Logs

116. Redis to the resque

117. Did they just add a 4th nosql?!

120. WEB FRONT
Additional Services: Documentation

122. DEVOPS

123. DEVOPS
IaaS vs. SaaS

124. Leave it to the Pros

125. Or?

126. Physical vs. Virtual

127. Remember this?

128. Virtualization

129. Virtualization
Pros

130. Virtualization
Pros
– Cheap

131. Virtualization
Pros
– Cheap
– elastic

132. Virtualization
Pros
– Cheap
– elastic
– Volatile

133. Virtualization
Pros
– Cheap
– elastic
– Volatile
cons

134. Virtualization
Pros
– Cheap
– elastic
– Volatile
cons
– Overhead

135. Virtualization
Pros
– Cheap
– elastic
– Volatile
cons
– Overhead
– Tenant, not owner

138. DEVELOPMENT ENVIRONMENT

139. Remember?

140. We are liberal

141. We are liberal

142. We are liberal

143. We are liberal

145. The Trend

146. The Trend
Peter Piper picked a peck of pickled
peppers.
Did Peter Piper pick a peck of pickled
peppers?
If Peter Piper Picked a peck of pickled
peppers,
Where's the peck of pickled peppers Peter
Piper picked?

147. The Trend
Docker Docker picked a peck of Docker
Docker.
Did Docker Docker pick a peck of Docker?
If Docker Docker Docker a peck of Docker
Docker,
Docker Docker Docker Docker Docker
Docker Docker?

148. How Docker can help?

149. Where Docker can’t help?

150. No problem, developers will
manage virtual machines!

151. No problem, developers will
manage virtual machines!

152. Vagrant to the rescue

156. 1. Vagrant boots linux VM on
virtualbox

157. 1. Vagrant boots linux VM on
virtualbox
2. Docker runs all databases and
services from images

158. 1. Vagrant boots linux VM on
virtualbox
2. Docker runs all databases and
services from images
3. Profit!

159. HIGH AVAILABILITY
(and Locality)

160. Cluster everything

161. Remember?

163. CDN for Download Server

164. Or?

165. Or?

166. Or?

167. GTD for Web Application

170. BACKUP
and Vendor lock-out

174. Here’s the caveat:

175. Here’s the caveat:

176. Snapshots and replicas

177. MONITORING
State and Logs

180. Prevent this:

182. All together now

184. Conclusions time

185. Conclusions time
– Define Criticality

186. Conclusions time
– Define Criticality
– Embrace the change

187. Conclusions time
– Define Criticality
– Embrace the change
– Plan for scale, but be realistic

188. Conclusions time
– Define Criticality
– Embrace the change
– Plan for scale, but be realistic
– Backup everything!

189. No, thank you!