Calendar Invites at scale on AWS

June 23, 2018

So I started off my ISV journey 7 years ago.  Just an innocent attempt to get people to my events by sending them a Calendar Invite.  If they accepted, I knew that they were coming.  Or at least had a better chance of showing up to my events.  Along the way I had a Web based Calendar engine built by a local contractor on an old Cold Fusion stack.  It worked and we were off on many use cases on how I thought it should work.  Some 2200 hours of personal time in testing, UI design, and disastrous blunders on my part as a weekend and after work project I needed break.  If this was going to be bigger idea I needed help.  Enter a friend named Arnie.  Arnie came into the calendar “Thunder Dome” 2.5  years ago.  Or about 1800 hrs ago.  It has been a part time project for him and he caught the bug as indicated that those hours are after work and weekends. 

He helped with so many things –  testing , coding , web site, blogging and overall front end animal.  I voted him to Co-Founder last year.  He is a true inspiration.  Then we decided to blow up the old site and start over -literally scrap all the code some – $80K in custom contract coding down the drain..  Not easy.  We were both at a loss for 60 days.  We knew after talking with several large test customers we needed to get to scale on AWS with SES. 



We then started our Pizza Journey into AWS in August 0f 2017.  About 3 months ago in February of 2018 we were fortunate to recruit Jonn , who is our lead developer and CTO.  We have been iterating using Slack, and brain storming on how to use SES, Python SDK, SNS, Lambda and Arnie’s Vue front end with his run time engine.  We have the prototype running now in AWS.  Pretty exciting to see the Pizza project running!  The test site will be up and running in a few weeks. www.calendarsnack.com. More to come as we attempt to give every marketeer in the world their own calendar server for sending and tracking of Calendar invites!

No Responses

    Leave a Reply

    Your email address will not be published. Required fields are marked *