Enterprise makeover. Be a good web citizen, deliver continuously and change your organisation
•
1 gefällt mir•2,757 views
Microservices, cloud, continuous delivery heavily influenced how modern teams build software systems. Come to this talk to learn how our team rebuild frontend stack of several newspapers significantly reducing cycle time and creating fun work environment that lets great developers be great. Some of the things I’ll share: - how respecting the Web makes us faster - what we learned running 12factor apps on Heroku - nuances of Continuous Delivery that you won’t find in books - thinking process behind our decisions and some of the change patterns we used Video: http://www.schibsted.pl/2015/07/enterprise-makeover-part-16-creating-lean-enterprise/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-26-use-the-web-dont-abuse-it/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-36-rethinking-agile-practices/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-46-cloud-native-development-on-heroku/ http://www.schibsted.pl/2015/07/enterprise-makeover-part-56-continuous-delivery-orchestration/ http://www.schibsted.pl/2015/07/enterprise-makeover-66-organizational-change-summary/
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Was ist angesagt?
Was ist angesagt? (20)
Andere mochten auch
Andere mochten auch (13)
Ähnlich wie Enterprise makeover. Be a good web citizen, deliver continuously and change your organisation
Ähnlich wie Enterprise makeover. Be a good web citizen, deliver continuously and change your organisation (20)
Kürzlich hochgeladen
Kürzlich hochgeladen (20)
Enterprise makeover. Be a good web citizen, deliver continuously and change your organisation
- 7. Once upon a time... http://upload.wikimedia.org/wikipedia/commons/d/d9/Carlo_Dolci_-_St_Catherine_Reading_a_Book_-_WGA06372.jpg Part 2/10
- 8. CMS
- 16. CMS Web Frontend
- 17. CMS Web Frontend
- 18. Change pattern: Low hanging fruit
- 20. Hackday
- 22. 5 times faster
- 28. Use the Web, don’t abuse it Part 3/10
- 32. header articles list most read articles list footer ad resource resource resource resource resource
- 33. header articles list most read articles list footer ad as media type
- 34. header articles list most read articles list footer ad as media type URL
- 35. header articles list most read articles list footer ad as media type URL cache-control
- 37. Web integration
- 47. move ESI processing between backend and proxy server reversibledecisions
- 50. article video article text link - sport widget core content article text
- 51. <a role="widget" class="widget-link" href=”//example.com/sportWidget”> sport widget </a> link - sport widget
- 52. read URL article video article text link - sport widget article text
- 53. HTTPGET article video article text link - sport widget article text
- 54. HTML + (CSS) + (JS) article video article text sport widget article text
- 57. Why not Single Page App integration? Part 4/10
- 58. Based on: Nicholas Zakas: Enough With The JavaScript Already!
- 59. Based on: Nicholas Zakas: Enough With The JavaScript Already!
- 60. Based on: Nicholas Zakas: Enough With The JavaScript Already!
- 61. Based on: Nicholas Zakas: Enough With The JavaScript Already!
- 62. Based on: Nicholas Zakas: Enough With The JavaScript Already!
- 64. +
- 65. + =
- 72. curl wget bot
- 76. “PhantomJS can be CPU and memory intensive (and randomly crashes or freezes)” http://sorcery.smugmug.com/2013/12/17/using-phantomjs-at-scale/
- 84. every 2 weeks 6 times a day http://upload.wikimedia.org/wikipedia/commons/b/be/Abacus_4.jpg
- 85. http://pixabay.com/static/uploads/photo/2013/07/12/18/30/stopwatch-153398_640.png Lead time: 5-8 minutes
- 87. IDE is my layout tool
- 90. no dev|test|prod.properties in the app codebase
- 91. treat you code like an open source library
- 92. in-memory HttpSession is the root of all deployment evil
- 93. run apps as stateless processes
- 96. ssh + tail
- 97. ssh + tail
- 98. ssh + tail
- 100. log to stdout and pipe it to modern log analysis tool
- 101. "Installing software is like a first date: if it can't be polite, smart, and generous, what should I expect later?" - Scott Berkun
- 102. create fast, disposable and self-contained services <build_tool> build <build_tool> run
- 108. can’t display ad
- 110. someone dies personal data compromised can’t display ad
- 111. someone dies personal data compromised can’t display ad
- 112. Why did we choose Heroku?
- 117. diff
- 120. our users
- 121. our users EU backend US backup backend
- 122. our users EU backend US backup backend Varnish
- 124. self-service envs
- 128. trial!
- 132. we may outgrow Heroku one day
- 133. we may outgrow Heroku one day
- 135. manually
- 136. git push/pull origin master http://upload.wikimedia.org/wikipedia/commons/d/d4/Devicetemplates_laptop-01.png
- 137. run build with tests
- 138. git push heroku_test master
- 141. CI/CD as a service
- 145. self-hosted CI tools
- 147. “An opportunity opens up to transform your software into something more expressive and versatile than you expected. This can mean new features or it can just mean the replacement of a big chunk of rigid code with a simple, flexible expression of a deeper model. While this does not happen every day, it is so valuable when it does come up that the opportunity needs to be recognized and grasped.”
- 148. “An opportunity opens up to transform your software into something more expressive and versatile than you expected. This can mean new features or it can just mean the replacement of a big chunk of rigid code with a simple, flexible expression of a deeper model. While this does not happen every day, it is so valuable when it does come up that the opportunity needs to be recognized and grasped.”
- 149. “An opportunity opens up to transform your software into something more expressive and versatile than you expected. This can mean new features or it can just mean the replacement of a big chunk of rigid code with a simple, flexible expression of a deeper model. While this does not happen every day, it is so valuable when it does come up that the opportunity needs to be recognized and grasped.”
- 150. “An opportunity opens up to transform your software into something more expressive and versatile than you expected. This can mean new features or it can just mean the replacement of a big chunk of rigid code with a simple, flexible expression of a deeper model. While this does not happen every day, it is so valuable when it does come up that the opportunity needs to be recognized and grasped.”
- 154. Pipeline as code
- 157. shape the path
- 159. be nice to people
- 160. Summary • Consider using the Web before you start reimplementing it • Consider designing for replaceability and deployability • Consider automating boring things including PaaS setup and deployment pipelines • Consider using different change patterns for your context
- 161. Summary • Consider using the Web before you start reimplementing it • Consider designing for replaceability and deployability • Consider automating boring things including PaaS setup and deployment pipelines • Consider using different change patterns for your context
- 162. Summary • Consider using the Web before you start reimplementing it • Consider designing for replaceability and deployability • Consider automating boring things including PaaS setup and deployment pipelines • Consider using different change patterns for your context
- 163. Summary • Consider using the Web before you start reimplementing it • Consider designing for replaceability and deployability • Consider automating boring things including PaaS setup and deployment pipelines • Consider using different change patterns for your context
- 164. Thank you Mateusz Kwaśniewski “The purpose of an organization is to enable ordinary human beings to do extraordinary things” - P.Drucker