JohnChapin
John Chapin is a cofounder of Symphonia, a Serverless and Cloud Technology consultancy based in New York City. He has over 15 years of experience as a technical executive and senior engineer, and was previously VP Engineering, Core Services & Data Science at Intent Media, where he helped teams transform how they delivered business value through Serverless technology and agile practices. John also co-organizes the NYC Clojure meetup. Outside of Symphonia, he can be found running along the west side of Manhattan, surfing at Rockaway Beach, or planning his next trip abroad.
One of the most compelling Serverless architectures doesn’t need to involve AWS Lambda at all. Amazon’s Simple Storage Service, or S3, is a great option for hosting a website or other static content. However, the naive approach to S3 static content hosting doesn’t account for concerns like custom domains, edge caching, transport encryption (SSL), backups, stale file deletion, and disaster recovery.
Deploying simple serverless applications using AWS Lambda is getting easier every day, but for software architects dealing with complex systems, Lambda’s constrained execution environment seems to put it out of consideration, especially when combined with organizational technology choices like Java.
Deploying simple serverless applications using AWS Lambda is getting easier every day, but for software architects dealing with complex systems, Lambda’s constrained execution environment seems to put it out of consideration, especially when combined with organizational technology choices like Java.
Zero fluff.