gopher-holes-unlimited VS aws-appsync-community

When you define the backing resources and request schemas in your spec file, SAM will automatically create a huge amount of supporting resources:

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.

Gopher Holes Unlimited

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.

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.

With serverless microservices, structure your root-level folders by resource type. Take the Gopher Holes Unlimited reference architecture project as an example.

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.

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.

# 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  *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)

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.

For context; the web application is built with React and TypeScript which makes calls to an AppSync API that makes use of the Lambda and DynamoDB datasources. We use Step Functions to orchestrate the flow of events for complex processing like purchasing and renewing policies, and we use S3 and SQS to process document workloads.

AWS AppSync is a serverless GraphQL offering by AWS, previously I authored a blog about AWS AppSync 101 which gets you up to speed with the capabilities of AppSync and how you can leverage them in your serverless applications.

Amplify Studio's Data allows you to define Amazon DynamoDB keeping in mind the properties with the right type and also powered with AWS AppSync where which generates a GraphQL schema under the hood.

AWS AppSync I'm keeping this section a bit shorter for you all, since AppSync is not something I have actually used personally, but have heard great things about. AppSync is another API option AWS has made available specifically for applications that want to take advantage of GraphQL or a Publish/Subscribe model. The GraphQL model may be of interest to front end developers that need to query multiple sources of data from one API endpoint, like databases or microservices. The Pub/Sub model I am more familiar with in the IoT hardware-communicates-with-software aspect, however this is also powerful for frontend developers looking to take advantage of real-time updates with serverless WebSocket connections. With AppSync, you also have caching, offline data synchronization, and real-time updates. You can learn more and check out the developer docs on the AWS Website.

5. Amazon Appsync

Amplify is a set of tools that allows full-stack web and mobile developers to create and build apps. It makes using AWS services, like our Cognito identity and access management service, or our managed GraphQL service AppSync, much simpler and straight forward to use.

This was the top-voted, long-awaited request for AppSync.

Appsync is the AWS service focus on creating flexible APIs, and Amplify is the framework that combines multiple AWS tools to help you build any type of Application.

Check out AppSync (https://aws.amazon.com/appsync/) or Apollo, you can deploy Apollo app to AWS as serverless application.