Traditionally, developers create unit tests to test code and to ensure bugs don’t get introduced as time goes on and your code changes. The theory is that if you write tests that cover every line of code, then when you make a change and the tests still pass, you can feel pretty comfortable that it will work as it should.
Well there is a lot more that can go wrong in your production system than introducing a bug in your code.
Continue reading “When Unit Tests Aren’t Enough… ABT – Always Be Testing”
Many third party API’s have rate limits to ensure you don’t overuse or DoS them. Twitter for instance has the following rate limits:
- Unauthenticated calls are permitted 150 requests per hour. Unauthenticated calls are measured against the public facing IP of the server or device making the request.
- OAuth calls are permitted 350 requests per hour and are measured against the oauth_token used in the request.
IronWorker provides an easy way to schedule jobs in the cloud without being tied to a particular server. Think Cron in the cloud.)
We use HipChat for internal communications at SimpleWorker and one of the great things about it is that it has a nice API allowing you to do some cool things like post messages to a chat room programmatically. One thing I wanted to be notified about was when someone mentioned SimpleWorker on Twitter and what better way to do that then to schedule a worker to check Twitter every day (or hour) and post results to our HipChat room.
Continue reading “Post Twitter Updates to HipChat using SimpleWorker – No Server Required”
Our friends over at IndexTank recently posted an article on how to create a search page using IndexTank and SimpleWorker. SimpleWorker to gather data from a remote service, in this case Plixi, and IndexTank to index that data for searching. SimpleWorker is great for collecting and keeping data up to date because you can schedule a worker to run every X minutes to retrieve data and update your IndexTank index.
Continue reading “How to Build a Serverless Search Engine with SimpleWorker and IndexTank”
A type of topic appearing more and more frequently in StackOverflow and Quora are questions on general architecture and app design. We came across one the other day on approaches to queuing and scheduling workers.
Chad Arimura will be speaking at the MongoSF conference next Tuesday, May 24th. He’ll be showing off the combination of SimpleWorker and MongoDB. As databases moves to more elastic and sharded NoSQL solutions like MongoDB, more and more processing moves from the data tier to the application tier. This shift makes background processing queues an even more essential component to the modern web stack.
Continue reading “Workers + NoSQL”