$30 off During Our Annual Pro Sale. View Details »

Building a Massively Scalable Cloud Service from the Grounds Up

Building a Massively Scalable Cloud Service from the Grounds Up

Serving binaries for developers is not a trivial task. As opposed to software downloaded by end users, developer binaries are mostly consumed by software tools. As such, these binaries are exposed to massive request load, similar to a coordinated DDoS attack in the case of popular binaries. Add to that: the need to manage metadata; support for pricy REST queries; controlling storage quotas; collecting stats; calculating common repository indexes on demand; and across the globe distribution, and look, you’ve got yourself a pretty complicated system to run and manage. This talk will show you how Bintray, JFrog’s social binary distribution service, works, to allow any developer to serve and consume OSS binaries. We will speak about how the system is segmented to support massive loads across data centers with full redundancy and stateless vertical scaling; how Grails applications can scale and how we tie up different NoSQL technologies such as CouchDB, MongoDB, Elasticsearch and Redis; we’ll also see how Java technologies, such as Grizzly and Jersey can provide a lightweight alternatives to traditional web technologies; and demonstrate how no-interruption deployments are done to provide continuous distribution of binaries to developers worldwide.

Baruch Sadogursky

November 06, 2013
Tweet

More Decks by Baruch Sadogursky

Other Decks in Programming

Transcript

  1. View Slide

  2. View Slide

  3. View Slide

  4. View Slide

  5. View Slide

  6. View Slide

  7. View Slide

  8. Some Numbers
    ___________
    liftoff + 9 months

    View Slide

  9. Some Numbers
    ___________
    liftoff + 9 months
    Users 7K

    View Slide

  10. Some Numbers
    ___________
    liftoff + 9 months
    Users 7K
    Packages 90K

    View Slide

  11. Some Numbers
    ___________
    liftoff + 9 months
    Users 7K
    Packages 90K
    Requests 1.8B/Month

    View Slide

  12. View Slide

  13. View Slide

  14. Requirements
    ___________

    View Slide

  15. Requirements
    –Download binaries
    ___________

    View Slide

  16. Requirements
    –Download binaries
    –Web application
    ___________

    View Slide

  17. Requirements
    –Download binaries
    –Web application
    –REST API
    ___________

    View Slide

  18. Requirements
    –Download binaries
    –Web application
    –REST API
    –Backend services
    ___________

    View Slide

  19. View Slide

  20. View Slide

  21. View Slide

  22. View Slide

  23. View Slide

  24. View Slide

  25. View Slide

  26. Non-Func. Requirements
    _________________

    View Slide

  27. Non-Func. Requirements
    Requirement RPS Availability
    _________________

    View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  31. View Slide

  32. View Slide

  33. View Slide

  34. View Slide

  35. View Slide

  36. View Slide

  37. View Slide

  38. View Slide

  39. View Slide

  40. View Slide

  41. View Slide

  42. View Slide

  43. File A: 46b34
    File B: a64ff7
    /repo-z/package-y/file-x
    /repo-m/package-n/file-k
    /repo-w/package-t/file-f

    View Slide

  44. File A: 46b34
    File B: a64ff7

    View Slide

  45. View Slide

  46. View Slide

  47. View Slide

  48. View Slide

  49. View Slide

  50. View Slide

  51. View Slide

  52. View Slide

  53. View Slide

  54. View Slide

  55. View Slide

  56. View Slide

  57. View Slide

  58. View Slide

  59. View Slide

  60. View Slide

  61. View Slide

  62. Requirements
    ___________

    View Slide

  63. Requirements
    –Rapid Application
    Development
    ___________

    View Slide

  64. Requirements
    –Rapid Application
    Development
    –Flexible schema
    ___________

    View Slide

  65. Requirements
    –Rapid Application
    Development
    –Flexible schema
    –Java Back
    ground
    ___________

    View Slide

  66. Requirements
    –Rapid Application
    Development
    –Flexible schema
    –Java Back
    ground
    –Stateless
    ___________

    View Slide

  67. View Slide

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

    View Slide

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

    View Slide

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

    View Slide

  71. Why don’t you just use...?
    Framework Why not?
    Angular.js Ember.js, ж.js Maturity
    Wicket State
    JSF No comment
    ________________
    -

    View Slide

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

    View Slide

  73. View Slide

  74. View Slide

  75. View Slide

  76. View Slide

  77. View Slide

  78. View Slide

  79. View Slide

  80. View Slide

  81. View Slide

  82. View Slide

  83. View Slide

  84. View Slide

  85. View Slide

  86. View Slide

  87. View Slide

  88. Grails means Gorm!

    View Slide

  89. View Slide

  90. View Slide

  91. View Slide

  92. View Slide

  93. View Slide

  94. View Slide

  95. View Slide

  96. View Slide

  97. View Slide

  98. View Slide

  99. Executive summary
    Framework Why not?
    ________________

    View Slide

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

    View Slide

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

    View Slide

  102. Executive summary
    Framework Why not?
    Lucene/compass Only embedded,
    resource guzzler
    solr Bad grail
    s integration
    sphynx No incremental index
    ________________

    View Slide

  103. View Slide

  104. View Slide

  105. View Slide

  106. View Slide

  107. View Slide

  108. View Slide

  109. View Slide

  110. View Slide

  111. View Slide

  112. View Slide

  113. View Slide

  114. View Slide

  115. View Slide

  116. View Slide

  117. View Slide

  118. View Slide

  119. View Slide

  120. View Slide

  121. View Slide

  122. View Slide

  123. View Slide

  124. View Slide

  125. View Slide

  126. View Slide

  127. View Slide

  128. View Slide

  129. SaaS for Download Server
    Component SaaS
    _________________

    View Slide

  130. SaaS for Download Server
    Component SaaS
    blob storage SoftLayer datastore
    _________________

    View Slide

  131. SaaS for Download Server
    Component SaaS
    blob storage SoftLayer datastore
    mapping Cloudant
    _________________

    View Slide

  132. SaaS for Web and services
    Component SaaS
    _________________

    View Slide

  133. SaaS for Web and services
    Component SaaS
    Model Mongohq
    _________________

    View Slide

  134. SaaS for Web and services
    Component SaaS
    Model Mongohq
    Grail
    s N/A
    _________________

    View Slide

  135. SaaS for Web and services
    Component SaaS
    Model Mongohq
    Grail
    s N/A
    ElasticSearch N/A
    _________________

    View Slide

  136. SaaS for Web and services
    Component SaaS
    Model Mongohq
    Grail
    s N/A
    ElasticSearch N/A
    Redis N/A
    _________________

    View Slide

  137. View Slide

  138. View Slide

  139. View Slide

  140. View Slide

  141. View Slide

  142. Virtualization
    __________

    View Slide

  143. Virtualization
    __________
    Pros

    View Slide

  144. Virtualization
    __________
    Pros
    – Cheap

    View Slide

  145. Virtualization
    __________
    Pros
    – Cheap
    – elasticity

    View Slide

  146. Virtualization
    __________
    Pros
    – Cheap
    – elasticity
    – Volatility

    View Slide

  147. Virtualization
    __________
    Pros
    – Cheap
    – elasticity
    – Volatility
    cons

    View Slide

  148. Virtualization
    __________
    Pros
    – Cheap
    – elasticity
    – Volatility
    cons
    – Overhead

    View Slide

  149. Virtualization
    __________
    Pros
    – Cheap
    – elasticity
    – Volatility
    cons
    – Overhead
    – Tenant, not owner

    View Slide

  150. View Slide

  151. View Slide

  152. View Slide

  153. View Slide

  154. View Slide

  155. View Slide

  156. View Slide

  157. View Slide

  158. View Slide

  159. View Slide

  160. View Slide

  161. View Slide

  162. View Slide

  163. View Slide

  164. View Slide

  165. View Slide

  166. View Slide

  167. View Slide

  168. View Slide

  169. View Slide

  170. View Slide

  171. View Slide

  172. View Slide

  173. View Slide

  174. View Slide

  175. View Slide

  176. View Slide

  177. View Slide

  178. View Slide

  179. View Slide

  180. View Slide

  181. View Slide

  182. View Slide

  183. View Slide

  184. View Slide

  185. 1. Vagrant boots centos
    on virtualbox

    View Slide

  186. 1. Vagrant boots centos
    on virtualbox
    2. Chef install
    s all db and
    service rpms from
    private YUM repo

    View Slide

  187. 1. Vagrant boots centos
    on virtualbox
    2. Chef install
    s all db and
    service rpms from
    private YUM repo
    3. Profit!

    View Slide

  188. View Slide

  189. View Slide

  190. View Slide

  191. View Slide

  192. View Slide

  193. View Slide

  194. View Slide

  195. View Slide

  196. View Slide

  197. View Slide

  198. View Slide

  199. View Slide

  200. View Slide

  201. View Slide

  202. View Slide

  203. View Slide

  204. View Slide

  205. View Slide

  206. View Slide

  207. View Slide

  208. View Slide

  209. View Slide

  210. View Slide

  211. View Slide

  212. View Slide

  213. View Slide

  214. View Slide

  215. View Slide

  216. View Slide

  217. View Slide

  218. Conclusions time
    ______________

    View Slide

  219. Conclusions time
    –Define Criticality
    ______________

    View Slide

  220. Conclusions time
    –Define Criticality
    –Embrace the change
    ______________

    View Slide

  221. Conclusions time
    –Define Criticality
    –Embrace the change
    –Plan for scale, but be real
    ______________

    View Slide

  222. Conclusions time
    –Define Criticality
    –Embrace the change
    –Plan for scale, but be real
    –Backup everything!
    ______________

    View Slide

  223. View Slide