Scala from the Trenches - Java One 2016
Download as PPTX, PDF0 likes245 views
This document summarizes a presentation on test-driven development (TDD) and clean code. It introduces TDD concepts like writing tests before code, refactoring, and using fakes, stubs, and mocks for testing. It then demonstrates a use case of developing a throttling mechanism to prevent denial-of-service attacks on a prize game service. Code for the throttler and demo app are provided in GitHub links. The presentation concludes with information about the speaker and an invitation for questions.
Scala from the Trenches - Java One 2016
- 1. @kfirondev Scala from the Trenches @kfirondev Introduction to TDD and clean code Kfir Bloch Head of Backend Engineering
- 2. @kfirondev KFIR BLOCH ● Head of backend engineering @ Wix ● Hands-on developer above 17 years ● Joined Wix 5 years ago linkedin/in/blochkfir github.com/kfiron@[email protected]
- 4. @kfirondev@kfirondev THE ESSENCE OF TDD REFACTOR MAKE THE TEST PASS WRITE A FAILING TEST
- 5. @kfirondev@kfirondev Great software is something to marvel at: powerful, elegant, functional, a pleasure to work with as both a developer and as a user. Great software isn’t written by machines. It is written by professionals with an unshakable commitment to craftsmanship. “ “
- 6. @kfirondev@kfirondev TDD is based on a simple idea: Write tests for your code before you write the code itself. However, this "simple" idea takes skill and judgment to do well. Now there's a practical guide to TDD that takes you beyond the basic concepts. “ “
- 7. @kfirondev@kfirondev Unit Test FakesCollaborators Stubs Matchers Integration Tests Mocks Contract tests www.maplecityrubber.com TDD & CLEAN CODE “BUZZWORDS” Refactoring
- 9. @kfirondev@kfirondev Get - prize Get - prize OK OK Get - prize Get - prize Already wonAlready played Get - prize Get - prize Get - prize Get - prize Get - prize Get - prize Get - prize Get - prize Get - prize Get - prize Already won Already won Already won Already won Already won Already won Already won Already won Already won Already won USER QUIZ PRIZE SERVER DATABASE
- 10. @kfirondev@kfirondev Get - prize Get - prize OK OK Get - prize Already played Get - prize Get - prize Get - prize Get - prize Get - prize Already won Already won Already won Already won Already won USER QUIZ PRIZE SERVER DATABASE FAIL FAST PATTERN T H R O T T L E R ROLLING WINDOW KEY (user-id) THROTTLER
- 12. @kfirondev • TDD & Clean code definitions • DOS attack use case • Developed rolling window throttler • Wire the throttler to pre-baked service Summary of what we did
- 13. @kfirondev • ~120 backend developers • Zero QA engineers • ~100 deployments per day It works for us projectlifemastery.com
- 14. @kfirondev • Throttler code -> https://github.com/kfiron/tdd-clean-code-workshop-result • Demo app code -> https://github.com/kfiron/java-one-demo-app Resources github.com/kfiron
- 15. @kfirondev linkedin/in/blochkfir github.com/kfiron@[email protected] Kfir Bloch Head of Backend Engineering Q&A
- 16. @kfirondev Thank YouWix Engineering Blog http://engineering.wix.com/ We are hiring http://jobs.wix.com email [email protected] @kfirondev Kfir Bloch Head of Backend Engineering
Editor's Notes
- #4: The first case is degradation of service
- #6: Inspire me and drive how I do TDD
- #8: Many people thinks that code before tests, it is just unit tests I will try to show you some of it in the live coding
- #9: The first case is degradation of service
- #10: Already won
- #11: It not about correctness , it is about resources