In a recent challenge we wished to open our existing swagger documentation up to the public, in a cost-effective and self managed way. That got me thinking…
💡 — Use one of Amazons mature cloud services; AWS S3
The Serverless Framework is a powerful ‘open-source’ library that allows developers to seamlessly build and integrate applications into various cloud platforms (PAAS) such as Amazon Web Services, AWS.
Following the (stable) release of Serverless in 2017, AWS have built their own tool to deploy resources into their platform; AWS SAM a.k.a. Serverless Application Model, which was initially released in 2018. It is important to note at the time of reading this, SAM may be a valuable alternative tool for to your upcoming project(s).
You may be asking yourself, why bother using Serverless or the Serverless Framework to deploy client applications…
StepFunctions is yet another service offered by Amazon Web Services that can be used to orchestrate serverless workflows with AWS Lambda. StepFunctions are particularly useful in highly distributed systems and micro-service architectures.
One feature that I personally love about stepFunctions is the visual flow of an activity type diagram that can be understood by all areas of the business, see below;
AppSync is a managed GraphQL service offered by Amazon Web Services and can be used to build scalable enterprise APIs. A typical AppSync solution consists of small resolvers that can be combined to access various data sources such as databases, HTTP APIs or AWS Lambda.
In this example, I will be talking about using AWS AppSync with AWS Lambda data sources and one of the challenges I have come across while developing enterprise scale solutions with these technologies.
Each Lambda resolver you have in a particular request triggers an invocation. The problem comes with having nested resolvers where you only…