Skip to content
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

Merged
merged 4 commits into from May 15, 2024
Merged

Conversation

nnennandukwe
Copy link
Contributor

About the changes

Closes #

Important files

Discussion points

Updates according to our revision doc for our horizontal content pieces.

Copy link

vercel bot commented May 6, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
unleash-docs ✅ Ready (Inspect) Visit Preview 💬 Add feedback May 15, 2024 11:38am
1 Ignored Deployment
Name Status Preview Comments Updated (UTC)
unleash-monorepo-frontend ⬜️ Ignored (Inspect) Visit Preview May 15, 2024 11:38am

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.
Copy link
Contributor

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
Copy link
Contributor

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

Copy link
Contributor Author

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/",
Copy link
Contributor

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;
Copy link
Contributor

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

@nnennandukwe nnennandukwe requested a review from ivarconr May 8, 2024 13:40
@nnennandukwe nnennandukwe merged commit e9c4b47 into main May 15, 2024
7 checks passed
@nnennandukwe nnennandukwe deleted the update-lambda-doc branch May 15, 2024 11:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

None yet

3 participants