gopher-holes-unlimited
serverless-application-model
gopher-holes-unlimited | serverless-application-model | |
---|---|---|
16 | 98 | |
60 | 9,237 | |
- | 0.2% | |
0.0 | 9.2 | |
over 1 year ago | 8 days ago | |
JavaScript | Python | |
MIT License | Apache License 2.0 |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
gopher-holes-unlimited
-
A Beginner's Guide to the Serverless Application Model (SAM)
When you define the backing resources and request schemas in your spec file, SAM will automatically create a huge amount of supporting resources:
-
Are We Making Lambda Too Hard?
If we take my reference application Gopher Holes Unlimited as an example, we see that I have a function that updates an existing gopher and another function that links gophers to gopher holes.
-
I Have Good News And Bad News About Your Cloud Metrics
Gopher Holes Unlimited
-
Serverless API Essentials: PUT vs PATCH
Any operation that you need to be idempotent and require the full resource data to be provided should be backed by a PUT operation. For example, if we take the update gopher hole endpoint from my reference project Gopher Holes Unlimited, you can see that we overwrite the entire gopher hole resource.
-
Infrastructure From Code - My First Impression
The real key to the success I've had doing this is that I can quickly find my resources from a known entry point, like an API endpoint. I can look at my spec, see that it ties to a specific Lambda function, and go straight there.
-
Best Practices for Building Serverless Microservices
With serverless microservices, structure your root-level folders by resource type. Take the Gopher Holes Unlimited reference architecture project as an example.
-
Introducing A New Cross-Cutting Architecture Diagram: The Critical Path
When talking about data flows, I mean the path through your system a business process follows. If we take an example from Gopher Holes Unlimited, we can see what happens when a new gopher is added to the system.
-
Build Better Serverless APIs By Going Storage First
I'm not a fan of providing theory without practice. So I have revamped my Gopher Holes Unlimited application to show the specifics of how to setup and process jobs.
-
How (and Why) You Need To Start Generating Your Serverless Infrastructure Diagrams
# My Example Microservice ## Description This is an example README for **Gopher Holes Unlimited** - a fake business but real API that tracks two things: 1. Gophers 2. Holes ## Infrastructure ![Infrastructure Diagram](/diagrams/diagram.png) *Resources currently deployed in Production. This diagram was automatically generated in the CI pipeline* ## Source If you want to check out the source, please visit our [GitHub page](https://github.com/allenheltondev/gopher-holes-unlimited)
-
Solutions Architect Tips - The 5 Types of Architecture Diagrams
We will take an example from my fake business but real API, Gopher Holes Unlimited, where we add a new gopher into the system to be tracked.
serverless-application-model
-
Simple and Cost-Effective Testing Using Functions
The complete solution with SAM is available here.
-
Deploying a Serverless Dash App with AWS SAM and Lambda
There are many options to deploy Serverless Applications in AWS and one of them is SAM, the Serverless Application Model. I chose to use it here, because it doesn't add too many layers of abstraction between what's being deployed and the code we write and our infrastructure is quite simple.
-
Serverless Apache Zeppelin on AWS
The solution uses AWS SAM with the global configuration for Lambda functions and the public API you can use to access Apache Zeppelin. The stack deployment provides the URL as an output value.
-
Using design patterns in AWS Lambda
When you combine this with the AWS Serverless Application Model you can also very easily include your dependencies. Or use a compiled language like golang for your Lambda functions. You simply run sam build before you run the aws cloudformation package and aws cloudformation deploy commands. SAM will build the binary and update the template to point to the newly built binary. Package will then upload it to S3 and replace the local reference to the S3 location. Deploy can then create or update the stack or you can use the CloudFormation integration in CodePipeline.
-
Serverless Site Health Check Notification System
I'm a big fan of using an Infrastructure as Code (IaC) approach for any project. My go to tools for this are the Servlerless Application Model (SAM) and it's associated CLI (SAM CLI). For more official use cases and for cross platform apps I typically use Terraform.
-
Starting My AWS Certification Journey as a Certified Cloud Practitioner
AWS SAM
-
API Gateway, Lambda, DynamoDB and Rust
Kicking off the tour and not starting a war, but I'm going to be using the Serverless Application Model.
-
Consuming an SQS Event with Lambda and Rust
The diagram here is super simple. I'm going to write something a little later that shows how this code could fit into a bigger workflow, but for now, I'm keeping it basic. And yes, that's the SAM Squirrel in there.
-
AWS Data Engineer Associate Certification - Coming Soon
Interestingly, AWS CDK and SAM are both explicitly mentioned. While CDK broadly addresses Infrastructure as Code, SAM is highlighted for its role in developing serverless data pipelines - a hugely underrated concept.
-
A Beginner's Guide to the Serverless Application Model (SAM)
Naturally, there are several options available to declare your cloud resources. The options with the most popularity are the CDK, AWS CloudFormation, SST, Serverless framework, Terraform, and AWS SAM. There are others, but when talking about Infrastructure as Code (IaC), these are the ones you hear about most often.
What are some alternatives?
postman-contract-test-generator - Postman collection and environment that will take an Open API Spec, validate component adherence, generate contract tests, and execute them.
aws-elastic-beanstalk-cli - The EB CLI is a command line interface for Elastic Beanstalk that provides interactive commands that simplify creating, updating and monitoring environments from a local repository.
serverless-websockets - Get started with websockets with this serverless solution
LocalStack - 💻 A fully functional local AWS cloud stack. Develop and test your cloud & Serverless apps offline
serverless-graphql - Serverless GraphQL Examples for AWS AppSync and Apollo
Moto - A library that allows you to easily mock out tests based on AWS infrastructure.
aws-cdk - The AWS Cloud Development Kit is a framework for defining cloud infrastructure in code
sst-start-demo - A simple SST app to demo the new `sst start` command
draw.io - draw.io is a JavaScript, client-side editor for general diagramming.
openvscode-server - Run upstream VS Code on a remote machine with access through a modern web browser from any device, anywhere.
terraform - Terraform enables you to safely and predictably create, change, and improve infrastructure. It is a source-available tool that codifies APIs into declarative configuration files that can be shared amongst team members, treated as code, edited, reviewed, and versioned.
aws-sam-cli - CLI tool to build, test, debug, and deploy Serverless applications using AWS SAM