When companies make decisions about moving to the cloud they must weigh business factors and technical factors. AWS Managed Services such as serverless technology offer a great application architecture choice to deliver features fast and do it at a lower cost structure. However, doing so is far from simple and sometimes can have a significant learning curve. Best trained, most well-meaning engineers can make bad decisions. Similarly, business managers can underestimate complexity and costs. What can one do to reduce these risks? This article takes a narrow view of such risk and tries to examine this problem under the development and operations lens. At FastUp we have deployed the following best practices to our client’s serverless cloud operations as well as to our own operations with great success.
In 2018, I wrote a series of posts about my experience
working AWS Serverless for a global high volume public facing web application. It took us about a year and a half, about
15 software engineers, and a lot of stumbling to get it working. In 2016, when we started, AWS Serverless was newish.
The community was abuzz about how cool it was. The Serverless Framework was the only real tool that developers could
use. There were just no examples in the wild. At FastUp we continue to develop business applications on the AWS
Serverless stack of API Gateways, Lambda and Dynamo Database. In this post I am going to cover how our approach to
building and deploying Serverless has changed over the years.
Coronavirus has upended life as we know it. Fortunately, healthcare providers are plowing through it all and bringing to us what we need the most. Their unimaginable personal sacrifices are saving us day and night from some unimaginable individual consequences. This blog post must begin with a big thanks to all healthcare providers. You Rock!