New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
doc: Optimizing AWS Lambda Documentation #6991
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
1 Ignored Deployment
|
slug: /feature-flag-tutorials/serverless/lambda | ||
--- | ||
|
||
For developers new to feature flags in serverless environments, this guide will walk you through practical examples using the [Unleash Node.js SDK](https://github.com/Unleash/unleash-client-node) in [AWS Lambda](https://aws.amazon.com/lambda/). These concepts can be easily adapted to other serverless solutions like [Google Cloud Functions](https://cloud.google.com/functions). Having feature flagging capabilities available inside of your serverless functions allows you to validate new parts of your serverless functions and stay in control of the feature exposure. | ||
With feature flagging capabilities in your serverless functions, you can validate new parts of your serverless functions. This gives you complete control over feature exposure and simplifies serverless function versioning management. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the first sentences uses "serverless functions" twice which feels repetitive. Can you update?
|
||
- If you make a breaking change to a serverless function (e.g., new params), you usually need to create a new version with an appropriate URL routing scheme | ||
- But sometimes you may need to add a non-breaking change, signature-wise, that may still have unwanted side effects for some consumers | ||
- Give a concrete example |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is this section finished? Looks like placeholder content still
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@ivarconr do we have an example for this? I'm assuming "signature-wise" is referring to code signing, but not sure.
let unleash; | ||
|
||
async function init() { | ||
if (!unleash) { | ||
unleash = await startUnleash({ | ||
url: 'https://sandbox.getunleash.io/enterprise/api/', | ||
appName: 'lambda-example-app', | ||
url: "https://sandbox.getunleash.io/enterprise/api/", |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Probably put <YOUR_UNLEASH_URL>
here like we do elsewhere?
|
||
if(unleash) { | ||
if (unleash) { | ||
await destroyWithFlush(); | ||
unleash = undefined; |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would rather set this to null
ee2d9d2
to
73bd576
Compare
About the changes
Closes #
Important files
Discussion points
Updates according to our revision doc for our horizontal content pieces.