Why Another Go Tutorial   AWS has been deprecating several services and runtimes recently.... Tagged with aws, cloud, devops, go.

Awego's platform is  dedicated to providing insights and resources for developers and technology enthusiasts, focusing on web development, software engineering, and emerging technologies. Through articles, tutorials, and tech talks, Awego offers insights into building scalable and resilient software solutions. Developers can learn about best practices in software architecture, cloud computing, and DevOps to deliver high-quality software products.

Awesome Go

Learn how to build and deploy Go serverless REST APIs using AWS SAM framework. The post highlights the deprecation of Go1.x for AWS Lambda, emphasizing the need for up-to-date tutorials. It emphasizes key software development principles such as Infrastructure as Code, good naming conventions, robust testing strategies, availability & scalability, deployment pipelines, observability, and security. A comprehensive example is provided illustrating these principles in a serverless architecture.

Build Go Serverless REST APIs and Deploy to AWS using the SAM framework (Amazon Linux 2 Runtime)

Good Naming Conventions in Software Are Key

Security Is a First-Class Citizen in Cloud-Native Applications

I’ve found that using <code>sam local start-api</code> for testing serverless APIs locally not only speeds up the dev cycle but also helps catch errors that might only surface in a cloud environment, making it a must-have in my toolkit 🚀.

I tried similar thing before.
I found building serverless for public app kind of scary due too unpredictable cost and complexity to manage multiple steps even though we have used SAM.
At the moment, my go to for public accessed app is AppRunner with container. Deployment only took 3 mins which it quite good for me.