Your SlideShare is downloading. ×
The Art of the Spike
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

The Art of the Spike

1,813
views

Published on

Published in: Technology

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,813
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
5
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. The Art of the Spike Aaron Bedra Principal, Relevance, Inc. Copyright 2007-2010 Relevance, Inc. This presentation is licensed under a Creative Commons Attribution-Noncommercial-Share Alike 3.0 United States License. See http://creativecommons.org/licenses/by-nc-sa/3.0/us/ Saturday, May 15, 2010
  • 2. Saturday, May 15, 2010
  • 3. DRY Saturday, May 15, 2010
  • 4. Do you have 10 years of experience or the same year 10 times? Saturday, May 15, 2010
  • 5. So you’re starting a new project... Saturday, May 15, 2010
  • 6. Yes but why? Saturday, May 15, 2010
  • 7. Business value Saturday, May 15, 2010
  • 8. “Faster” Saturday, May 15, 2010
  • 9. “Better” Saturday, May 15, 2010
  • 10. “Easier” Saturday, May 15, 2010
  • 11. A Jedi craves not these things Saturday, May 15, 2010
  • 12. Making money Saturday, May 15, 2010
  • 13. Preserving reputation Saturday, May 15, 2010
  • 14. Saturday, May 15, 2010
  • 15. We’ve just been assigned a new project Saturday, May 15, 2010
  • 16. Credit card authorization Saturday, May 15, 2010
  • 17. Very lean information set Saturday, May 15, 2010
  • 18. Number, available credit, per charge limit Saturday, May 15, 2010
  • 19. Lookup by card number Saturday, May 15, 2010
  • 20. Web service for charges Saturday, May 15, 2010
  • 21. Transaction speed is essential Saturday, May 15, 2010
  • 22. Ok let’s get down to planning Saturday, May 15, 2010
  • 23. We’ve decided to use clojure as a language Saturday, May 15, 2010
  • 24. And PostgreSQL as a database Saturday, May 15, 2010
  • 25. But wait! Saturday, May 15, 2010
  • 26. Has anyone heard about Redis? Saturday, May 15, 2010
  • 27. It might be a good fit for this Saturday, May 15, 2010
  • 28. We should spike it out! Saturday, May 15, 2010
  • 29. Research time Saturday, May 15, 2010
  • 30. Record everything! Saturday, May 15, 2010
  • 31. Time-box everything! Saturday, May 15, 2010
  • 32. Getting started Saturday, May 15, 2010
  • 33. All technology you are about to encounter should be treated as a first class citizen! Saturday, May 15, 2010
  • 34. Download and install Saturday, May 15, 2010
  • 35. How did it go? Saturday, May 15, 2010
  • 36. Should we keep going? Saturday, May 15, 2010
  • 37. Interfacing Saturday, May 15, 2010
  • 38. Is there an SDK or API? Saturday, May 15, 2010
  • 39. In the language you are using? Saturday, May 15, 2010
  • 40. Does it work? Saturday, May 15, 2010
  • 41. Should we keep going? Saturday, May 15, 2010
  • 42. Prototype code Saturday, May 15, 2010
  • 43. Simple CRUD Saturday, May 15, 2010
  • 44. How long did it take? Saturday, May 15, 2010
  • 45. Should we keep going? Saturday, May 15, 2010
  • 46. Reference Example Saturday, May 15, 2010
  • 47. What does my team think? Saturday, May 15, 2010
  • 48. Should we keep going? Saturday, May 15, 2010
  • 49. Operations Saturday, May 15, 2010
  • 50. How do we deploy it? Saturday, May 15, 2010
  • 51. How do we monitor it? Saturday, May 15, 2010
  • 52. Should we keep going? Saturday, May 15, 2010
  • 53. Performance Saturday, May 15, 2010
  • 54. How fast can a single instance go? Saturday, May 15, 2010
  • 55. Can it scale? Saturday, May 15, 2010
  • 56. How does it compare to our original idea? Saturday, May 15, 2010
  • 57. Does it help us meet our “why” Saturday, May 15, 2010
  • 58. Should we keep going? Saturday, May 15, 2010
  • 59. Management / Client Saturday, May 15, 2010
  • 60. We did a spike and here’s what we found Saturday, May 15, 2010
  • 61. Easy to install Saturday, May 15, 2010
  • 62. Easy to use Saturday, May 15, 2010
  • 63. The dev team has a reference Saturday, May 15, 2010
  • 64. Dev team feels they can be productive on day one Saturday, May 15, 2010
  • 65. Easy deployment Saturday, May 15, 2010
  • 66. Easy monitoring Saturday, May 15, 2010
  • 67. In memory Saturday, May 15, 2010
  • 68. Outperforms our RDBMS Saturday, May 15, 2010
  • 69. Easy and fast scaling Saturday, May 15, 2010
  • 70. ? Saturday, May 15, 2010
  • 71. Questions? Saturday, May 15, 2010
  • 72. Contact • aaronbedra.com (blog) • @abedra (twitter) • aaron@thinkrelevance.com • github.com/abedra • speakerrate.com/talks/3252 Saturday, May 15, 2010