For a couple of weeks we’ve been meaning to post a full update about PostageApp. But when push comes to shove, we realize that at this early stage in its development, we’d rather spend the time to make PostageApp better than merely talk about how it will continue to get better.
For now, here’s a short update:
1. First off, we’re sorry for this morning’s queuing delay.
This morning (April 28th) at approximately 6 am EDT, PostageApp experienced an error with its queuing engine that caused a sending delay of up to 3hrs. But rest assured, no emails were lost.
2. System upgrades.
This morning’s delay had to do with how the system handles peak times – when thousands of mail requests get put into a queue and processed. It’s actually one of the primary areas of improvement we’ve been working on. These are the three key areas we’ve focused on:
i. Separating the key application architecture onto distinct servers, so that each can be more easily scaled and monitored.
ii. Improving the scale-ability of the queuing-worker processes so it can better handle peaks in the queue.
iii. Improving the server and process monitoring to detect logjams and failures.
We expect to push our system improvements live soon and we’ll let you know as soon as it’s done.
We also appreciate everyone’s patience and excellent feedback, and we wanted to make sure that you know we’re committed to making this as stable and robust as we all need it to be.. the mail must get through!