Your SlideShare is downloading. ×
0
&the story so far
Cian	  Clarke	  www.cianclarke.com	  	  @cianclarke	  github.com/cianclarke	  cian.clarke@feedhenry.com	  
We’re	  a	  
Photo:	  Peter	  Grogan	  
why NoSQL?why ?what for?doweuse
2011
}lol shardinglol sharding2011
TODAY
Q1 2013
oh sh!t you guys we needData Storagelike right now ~ Somebody, Aug 2011
$fh.db
fh-ditchData In The Cloud ..hook
We’re	  also	  a	  
A customer has…SERVICESAPPS+
CUSTOMERCUSTOMERCUSTOMER CUSTOMER
© Copyright FeedHenry Ltd. 2012PartnersClients
So why didchoose NoSQL?
we<3 JSON
But why didchoose ?Why notor or …., or stick with
replicationreplicationreplication
Great, so wheredo we actuallyuse ?
we	  use	  in	  repor@ng	  
we	  use	  in	  customer	  projects	  
:-­‐(	  
Customer	  	  Ra@ngs	  
Product	  Catalog	  •  400,000	  records	  •  Parsed,	  then	  dumped	  into	  DB	  all	  at	  once	  •  Fell	  over	  :-­...
Store	  	  Locator	  
Incident	  Response	  System	  
So, all fun &games with?	  
?@feedhenry | @cianclarke	  feedhenry | cianclarkefeedhenry.com | cianclarke.comme	  www	  
FeedHenry & MongoDB
FeedHenry & MongoDB
FeedHenry & MongoDB
FeedHenry & MongoDB
FeedHenry & MongoDB
Upcoming SlideShare
Loading in...5
×

FeedHenry & MongoDB

244

Published on

Presentation given to the Dublin Mongo User Group, December 2012 on our use of MongoDB in FeedHenry

Published in: Technology, Business
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
244
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Transcript of "FeedHenry & MongoDB"

  1. 1. &the story so far
  2. 2. Cian  Clarke  www.cianclarke.com    @cianclarke  github.com/cianclarke  cian.clarke@feedhenry.com  
  3. 3. We’re  a  
  4. 4. Photo:  Peter  Grogan  
  5. 5. why NoSQL?why ?what for?doweuse
  6. 6. 2011
  7. 7. }lol shardinglol sharding2011
  8. 8. TODAY
  9. 9. Q1 2013
  10. 10. oh sh!t you guys we needData Storagelike right now ~ Somebody, Aug 2011
  11. 11. $fh.db
  12. 12. fh-ditchData In The Cloud ..hook
  13. 13. We’re  also  a  
  14. 14. A customer has…SERVICESAPPS+
  15. 15. CUSTOMERCUSTOMERCUSTOMER CUSTOMER
  16. 16. © Copyright FeedHenry Ltd. 2012PartnersClients
  17. 17. So why didchoose NoSQL?
  18. 18. we<3 JSON
  19. 19. But why didchoose ?Why notor or …., or stick with
  20. 20. replicationreplicationreplication
  21. 21. Great, so wheredo we actuallyuse ?
  22. 22. we  use  in  repor@ng  
  23. 23. we  use  in  customer  projects  
  24. 24. :-­‐(  
  25. 25. Customer    Ra@ngs  
  26. 26. Product  Catalog  •  400,000  records  •  Parsed,  then  dumped  into  DB  all  at  once  •  Fell  over  :-­‐(  •  Node  +  Streams  =  Awesome  •  Streaming  CSV  parser  -­‐>  Chunks  -­‐>  Into  DB  
  27. 27. Store    Locator  
  28. 28. Incident  Response  System  
  29. 29. So, all fun &games with?  
  30. 30. ?@feedhenry | @cianclarke  feedhenry | cianclarkefeedhenry.com | cianclarke.comme  www  
  1. A particular slide catching your eye?

    Clipping is a handy way to collect important slides you want to go back to later.

×