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

feat: add specific use cases #174

Merged
merged 9 commits into from
Jan 21, 2024
Merged

feat: add specific use cases #174

merged 9 commits into from
Jan 21, 2024

Conversation

markphelps
Copy link
Contributor

Adds more specific use cases where Flipt is uniquely applicable including:

  • Edge/IoT
  • CloudNative
  • GitOps

@markphelps markphelps requested a review from a team as a code owner January 21, 2024 03:49
Copy link
Member

@GeorgeMac GeorgeMac left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nice, love all the changes. Added some thoughts / corrections.

usecases/cloudnative.mdx Outdated Show resolved Hide resolved
## Database Support

Flipt's plugable data store architecture allows it to be deployed to a variety of edge computing environments without requiring traditional server-based relational databases. Specifically, Flipt's support for SQLite, [LibSQL](https://turso.tech/libsql), and [Turso](https://turso.tech/) allow it to run in environments where a traditional database is not available.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

You could additionally add that the same goes for the declarative backends. They allow you to deploy Flipt to edge locations, much like putting a CDN infront of an s3 bucket. You can deploy Flipt infront of object storage and evaluate at the edge.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yeah i moved the section on declarative storage up and put them both under the same heading

usecases/edge.mdx Outdated Show resolved Hide resolved
usecases/edge.mdx Outdated Show resolved Hide resolved
usecases/edge.mdx Outdated Show resolved Hide resolved
usecases/gitops.mdx Outdated Show resolved Hide resolved

Our [GitHub Action](/tooling/github-actions) allows you to easily integrate Flipt into your CI/CD pipelines. This allows you to install Flipt into your CI pipeline and run tests against your feature flags before deploying your code to production.

You can also import your feature flag data from your repository, or any other source, into Flipt using our [Import Command](/cli/commands/import). This allows you to import your feature flag data into Flipt before running your tests.
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think it is better to encourage folks to use local backend here for CI. As it avoid the need to run Flipt with a DB and have a separate import step. You just run Flipt with local and point it at the relevant directory.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why not both? updated

.vale/styles/Flipt/spelling-exceptions.txt Outdated Show resolved Hide resolved
usecases/edge.mdx Outdated Show resolved Hide resolved
@markphelps markphelps merged commit 837bbb9 into main Jan 21, 2024
3 of 4 checks passed
@markphelps markphelps deleted the usecases-redo branch January 21, 2024 16:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants