How AWS Drives Argyle Social<br />
A bit about Argyle Social<br />What does Argyle do?<br />Social Media management, engagement, & Analytics<br />We are a sm...
AWS is Startup Friendly<br />Feb ‘10<br />May ‘10<br />SimpleDB<br />‘The Server’<br />SimpleDB<br />‘The Server’<br />SQS...
Servers Galore<br />Jun ‘11<br />Social<br />App Server<br />URL Redir<br />Social<br />Social<br />Stream<br />Jobs<br />...
Our current setup<br />EC2 – 9  Servers<br />SQS – 5  Queues<br />SimpleDB – 1 Domain <br />RDS – 1 DB; 5MM records<br />S...
SQS – Simple Queue Service<br />Used for processing:<br />Twitter Streams<br />Email queue<br />Filtering for significant ...
How it works<br />Process Message<br />Process Everything<br />Queue Everything<br />Process Message<br />Process Message<...
Argyle SQS Usage<br />Twitter Site Streams<br />Users<br />Interweb<br />Twitter Stream Reader<br />Twitter Stream Reader<...
SQS – What we learned<br />Not super fast<br />Lag between pushing and seeing an item on pull<br />Visibility timeout is k...
SQS - Conclusions<br />Very easy to get bullet-proof queues<br />No administration costs<br />Expect some limitations that...
Simple DB<br />Easy storage & retrieval of Key/Value pairs<br />Eventual consistent read vs. consistent read<br />Grows wi...
Argyle SimpleDB Usage<br />Redirecting a URL<br />Shortening a URL<br />ar.gy/123<br />ar.gy/ftw<br />ar.gy/12<br />Interw...
SDB – Scratch Pad <br />*This makes your life easier, especially when starting out or debugging<br />
SDB – Lessons Learned<br />Be aware of the limits:<br />Source: http://en.wikipedia.org/wiki/Amazon_SimpleDB#Limitations<b...
SDB – Lessons Learned<br />We’ve had some availability issues<br />Sometimes no response<br />Sometimes no write capabilit...
SimpleDB - Conclusions<br />Great, easy storage<br />Again, reduced maintenance costs<br />Have to change your mindset fro...
AWS Support<br />We’re new to it<br />We don’t expect much<br />It can be helpful toget nagging questionsresolved<br />Thi...
AWS Support<br />We ‘lost’ a server; 4.5 hours after submitted:<br />Clarification on “underlying host issue” pls; 40 minu...
Support Conclusions<br />Well worth the security<br />Rumor has it that upgrading to higher levels isn’t worth it – any ex...
Q & A<br />About Argyle<br />About your own AWS setup<br />
Upcoming SlideShare
Loading in …5
×

AWS at ArgyleSocial

1,165
-1

Published on

Published in: Technology, Design
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
1,165
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
4
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide

AWS at ArgyleSocial

  1. 1. How AWS Drives Argyle Social<br />
  2. 2. A bit about Argyle Social<br />What does Argyle do?<br />Social Media management, engagement, & Analytics<br />We are a small & very efficient dev team<br />Adam (general), Mike (platform), & Josh (design)<br />
  3. 3. AWS is Startup Friendly<br />Feb ‘10<br />May ‘10<br />SimpleDB<br />‘The Server’<br />SimpleDB<br />‘The Server’<br />SQS<br />MySql<br />MySql<br />Dec ‘10<br />Social<br />RDS<br />App Server<br />SimpleDB<br />MySql<br />SQS<br />
  4. 4. Servers Galore<br />Jun ‘11<br />Social<br />App Server<br />URL Redir<br />Social<br />Social<br />Stream<br />Jobs<br />MySql<br />MySql<br />RDS<br />SimpleDB<br />SQS<br />S3<br />Support<br />
  5. 5. Our current setup<br />EC2 – 9 Servers<br />SQS – 5 Queues<br />SimpleDB – 1 Domain <br />RDS – 1 DB; 5MM records<br />Support & S3 – Just starting out<br />Let’s dig into SQS, SimpleDB, & Support<br />
  6. 6. SQS – Simple Queue Service<br />Used for processing:<br />Twitter Streams<br />Email queue<br />Filtering for significant items<br />Log Processing for Goals<br />Very easy to get started:<br />
  7. 7. How it works<br />Process Message<br />Process Everything<br />Queue Everything<br />Process Message<br />Process Message<br />Process Message<br />Queue<br />
  8. 8. Argyle SQS Usage<br />Twitter Site Streams<br />Users<br />Interweb<br />Twitter Stream Reader<br />Twitter Stream Reader<br />Twitter Stream Reader<br />Argyle Web Interface<br />Twitter Processor<br />Twitter Processor<br />Twitter Processor<br />Streams RDS Database<br />Queue<br />AWS Service Land<br />
  9. 9. SQS – What we learned<br />Not super fast<br />Lag between pushing and seeing an item on pull<br />Visibility timeout is key<br />Make sure you have time to finish and delete<br />‘at least once delivery’ you may get something twice<br />Not guaranteed FIFO<br />Default size<br />Restrictive Sizing can lead to errors<br />1kB to 64kB<br />Getting Queue Url<br />Create it and store it, don’t look it up<br />
  10. 10. SQS - Conclusions<br />Very easy to get bullet-proof queues<br />No administration costs<br />Expect some limitations that rolling or running your own won’t incur<br />MSMQ, Spread, etc<br />
  11. 11. Simple DB<br />Easy storage & retrieval of Key/Value pairs<br />Eventual consistent read vs. consistent read<br />Grows with your data<br />NoSQL N00bs: take your time<br />This isn’t relational, which is obvious, but may take some time to really wrap your head around<br />No JOIN or GROUP BY, etc<br />
  12. 12. Argyle SimpleDB Usage<br />Redirecting a URL<br />Shortening a URL<br />ar.gy/123<br />ar.gy/ftw<br />ar.gy/12<br />Interweb<br />Redirector<br />Redirector<br />Click log<br />Cached URL<br />Non-cached URL<br />Memcached<br />Memcached<br />SimpleDB<br />SimpleDB<br />AWS Service Land<br />
  13. 13. SDB – Scratch Pad <br />*This makes your life easier, especially when starting out or debugging<br />
  14. 14. SDB – Lessons Learned<br />Be aware of the limits:<br />Source: http://en.wikipedia.org/wiki/Amazon_SimpleDB#Limitations<br />
  15. 15. SDB – Lessons Learned<br />We’ve had some availability issues<br />Sometimes no response<br />Sometimes no write capabilities<br />Storage of big items is possible, but must be linked out<br />Can separate domains to increase performance<br />
  16. 16. SimpleDB - Conclusions<br />Great, easy storage<br />Again, reduced maintenance costs<br />Have to change your mindset from RDBMS<br />
  17. 17. AWS Support<br />We’re new to it<br />We don’t expect much<br />It can be helpful toget nagging questionsresolved<br />This is your company on the line, right?<br />
  18. 18. AWS Support<br />We ‘lost’ a server; 4.5 hours after submitted:<br />Clarification on “underlying host issue” pls; 40 minutes to reply<br />
  19. 19. Support Conclusions<br />Well worth the security<br />Rumor has it that upgrading to higher levels isn’t worth it – any experiences out there?<br />(Update: we got good feedback around higher levels of service from Adzerk)<br />You still have to design for failure<br />
  20. 20. Q & A<br />About Argyle<br />About your own AWS setup<br />
  1. A particular slide catching your eye?

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

×