Emails, texts, and other notifications are critical for engaging with customers. No matter what form they take – alerts, daily summaries, weekly updates, special notices, or monthly newsletters – emails and notifications keep your customers informed, provide them with core services, and help drive revenue.
Continue reading “Best Practices: Parallel Processing Emails, SMS, and Other Notifications”
Against most predictions, email has stood the test of time and remains one of the most common and effective forms of communication. This is particularly true in the world of web applications where the flow of information from app to user is constant.
Ruby on Rails is one of the leading stack choices for building web applications, and ActionMailer is the goto MVC method that allows the app to interact with an SMTP server to deliver email. ActionMailer combined with a great SMTP delivery service like SendGrid, lets developers quickly and easily deliver email from inside their apps.
Continue reading “Powerful Email Infrastructure with IronWorker, ActionMailer, and SendGrid”
|Neo Handling Load
I’ve been in many conversations recently about how an application can handle spiky behavior. More importantly, how to handle it without a bunch of wasted resources that sit idle most of the time just to handle the spikes. There are a bunch of applications where this is a very typical use case, for instance:
Continue reading “Spikability – An Application’s Ability to Handle Unknown and/or Inconsistent Load”
They say a picture is worth a thousand words. Coincidentally, processing an image is about a thousand times more demanding than processing text. As more and more developers look to image processing solutions like ImageMagick to power social, retail, and mobile apps, they will run into many challenges as they try to get it to run efficiently and to scale.
We recently launched a Solutions section on ways to use Iron.io services to do some amazing things. This is the first of a series of posts on the use cases shown there.
Continue reading “Best Practices: Scalable Image Processing”
A common problem developers have is how to run through a large number of tasks in a short amount of time. For instance, sending out a nightly notification to all your users, calculating your user’s bills every month or updating their Facebook graph data. These types of things are very common and almost every application needs to do it and it becomes more and more of a problem as your user base grows.
Continue reading “How to Reduce a 9 Hour Job into a 9 Minute Job”
Here’s the second video in my tutorial series. In under 3 minutes I demonstrate how to schedule a worker that posts to Twitter, and even show the code involved, which is a grand total of about 50 lines.
Continue reading “Video Series – Episode 2: Scheduling”
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”
We’ve created a public github repository for SimpleWorker example code. There are a few samples in there right now and we’ll keep adding to it and we welcome any contributions as well! If you have a worker you’d like to share, fork the project, add your worker example, then send us a pull request.