- Wondering why Gnip isn't returning what we expect.September 8, 2008 krakn (krakn)
- going to be a great week! came across solid write-up of Gnip vis a vis MOM and the Enterprise. http://bit.ly/1lfUCdSeptember 8, 2008 jvaleski (Jud)
- Looking at Simple Update protocol http://tinyurl.com/6fjc6k and gnip http://tinyurl.com/4bmytu http://tinyurl.com/6xcaoeSeptember 8, 2008 oxfordben (oxfordben)
- @bfeld Could certainly be an interesting problem for Gnip to look at.September 5, 2008 midtownninja (Vishy Venugopalan)
- Great Meeting you this morning GNIP - http://www.gnipcentral.com!September 5, 2008 HeatherPaulsons (HeatherPaulsons)
Three (Six?) Week Software Retrospective
July 24, 2008, 7:28am by jud
I had to go back into older blog posts to remind myself when we launched; July 1st. It feels like we’ve been live since June 1st.
Looking Back
Things have gone incredibly well from an infrastructure standpoint. We’ve had to add/adjust some system monitoring parameters to accommodate the variety of Data Producers publishing into the system; different frequencies/volumes call for for specialized treatment. We weren’t expecting the rate, or volume, of Collection creation we wound up with. Within three hours of going live, we had enough Collections in the system to adversely impact node startup/sync times. We patiently tuned our data model, and tuned TerraCotta locks to get things back to normal. It’s looking like we’ll be in bed with TerraCotta for the long haul.
Amazon
I’m not sure I could be any more pleased with AWS. Our core service is heavily dependent on EC2, and that’s been running sans issues. We’re working on non-Amazon failover solutions that assure un-interrupted service even if all of EC2 dies. Our backups are S3 dependent so we had some behind the scenes issues last weekend when S3 was flaky; see my previous post on this issue. We haven’t had our day in the sun with outages, and I obviously hope we never do, but so far I’m walking around with a big “I <3 AWS” t-shirt on.
Other
On the convenience library front, we (Gnip + community) have made all of our code available on github. We’ve had tremendous community support and contribution on this front; so cool to see; thanks everyone!
Collections are by far the primary data access pattern (as opposed to raw public activity stream polling); not really a surprise.
Summize/Twitter has been a totally cool way to track ether discussion around Gnip. When we notice folks talking about Gnip, positive or negative, we can reach out in “real-time” and strike up a conversation.
That’s all for now.
Thanks to all the Data Producers and Consumers that have integrated with Gnip thus far!
« Newer Post Older Post »