More Related Content
Similar to Pivotal Labs Lunch Talk; 3 Infrastructure and workflow lessons learned at an early stage startup
Similar to Pivotal Labs Lunch Talk; 3 Infrastructure and workflow lessons learned at an early stage startup (20)
More from Rainforest QA (9)
Pivotal Labs Lunch Talk; 3 Infrastructure and workflow lessons learned at an early stage startup
- 1. Rainforest QA Lunch talk:!
3 Infrastructure + workflow
lessons learned at an
early-stage startup
rainforest
@rainforestqa
- 3. Us
Team of 3 in SoMa
All developers
YC S12
rainforest
@rainforestqa
- 19. #3: Use your own product!
(aka dogfooding)
rainforest
@rainforestqa
- 30. Step 2: Put in build process
rainforest
@rainforestqa
- 31. #1 - add gem!
#2 - add to circle.yml
rainforest
@rainforestqa
- 33. #1 Make it disruptive
rainforest
@rainforestqa
- 34. #2 Fix it quickly
rainforest
@rainforestqa
- 38. < 20 mins to test
rainforest
@rainforestqa
Editor's Notes
- - Master
- Run SF Mongo meetup
- - No support in mongo
- - Inconsistent data in db due to our code breaking
- We fixed with helper scripts. Slow and sucked.
- - No formal or standard way of doing them
- All complex or slow if large
- Schema design suffers as a result
- - Non-trivial reporting queries require code
- Great if you know what you’re after when you design your schema
- Ours is evolving
- - We especially love window functions in PG
- - wanted to know how much each client costed us per week
- this joins 4 tables, partitions by week and sorts by most expensive first
- - Don’t exist
- Fix by de normalizing data
- Usually results in-consistent data without transactions
- - No redis
- - We sent emails and enqueued jobs before things were consistent