Serverless Architecture For Bulk Email Management

Changed the format to comply with a IEEE format and revised the abstract and conclusion to better fit the research that is perfomed. Added analysis of runtimes using boxplot and described the method used to analyze the application and fixed any grammatical errors that were noticied in the first version. I would consider this revision not to be a complete redo but a refinement and a small add on to better substantiate the research that is being conducted.

Sending emails in large quantities can be tediousconsidering free services do not cover bulk email and paidservices can be costly and are not easy to customize. Traditionalemail client used for basic emailing services fail to be useful inlarger volumes of emails to target people or spread informationto consented individuals. This paper proposes a serverless archi-tecture to tackle such problems by using one such offering fromthe Amazon Web Services(AWS) which can be easily replacedby a software architects choice of service. The constraints helpto make an architecture using components that can fit most ofthe needs of a serverless backend and extend it to scenariossuch mobile notifications, One Time Password (OTP) systems orother means of communication to minimize single point of failureand also decrease the dependency on physical servers for suchoperations offering a comparable solution within the cloud. Thearchitecture proposed is tested to find the time taken to sendthe emails of various quantities and see how it affects the cost.The architecture was successful able to send multiple emails in aquick and single invocation and has demonstrated a higher levelof scalability compared to conventional methods.