Flagsmith Reviews

Liquibase Reviews

Flagsmith mentions (13)

• Why use Open Source Feature Flags?

  Considering all these points, the team at Flagsmith has developed a feature flag management platform Flagsmith and made it open source. The core functionality is open and you can check out the GitHub repository here. I have utilized and authored several blogs discussing their excellent offerings and strategies. - Source: dev.to / about 2 months ago

• free-for.dev

  Flagsmith - Release features with confidence; manage feature flags across web, mobile, and server side applications. Use our hosted API, deploy to your own private cloud, or run on-premise. - Source: dev.to / over 1 year ago

• Which startups are made using Django?

  Flagsmith is written in Django and is open source as well: https://flagsmith.com. Source: almost 2 years ago

• The actual infrastructure costs of running SaaS at scale (billions of requests/month)

  Before we dive in, one important call-out: We provide our feature management product to customers in three ways depending on how they want to have it managed: Fully Managed SaaS API, Fully Managed Private Cloud SaaS API and Self-Hosted. The infrastructure costs that we are sharing is for our customers that leverage our Fully Managed SaaS API offering (try it free: https://flagsmith.com/) which represents a portion... - Source: dev.to / about 2 years ago

• The Story Behind Our Open Source Ecommerce Platform with +9,000 GH stars in 6 months

  On March 15th, Sebastian Rindom, the CEO & Co-founder of Medusa, did an interview with Flagsmith where he talked about how Medusa started, why create a headless commerce solution, why make it open-source, and more. - Source: dev.to / about 2 years ago

Liquibase mentions (5)

• How do you guys go about the persistence layer?

  As far as keeping track of domain changes you can store DDL files in version control like you mention or use tools like Flyway (https://flywaydb.org) or Liquidbase (https://liquibase.org) which takes care of database migrations. Source: about 2 years ago

• How do you guys go about the persistence layer? (x-post)

  I just use SQL directly (or something like JOOQ). For database migrations I use Liquibase. Source: about 2 years ago

• Where questioning the scale of a company and its clients its seen bad

  Regarding the migrations, there are tools such as https://liquibase.org/ or FlyAway that handle this. Heck, you can even use an ORM that has a migration baked-in but that defeats the purpose of having the migrations in a separate project. Source: about 2 years ago

• State based change management tool for Snowflake

  I've trialled schemachange and liquibase which are change script based tools. I've ruled out a whole load of other tools that are either change script based tools or don't support Snowflake, including the following:. Source: over 2 years ago

• Learning SQL and using dll (CREATE,DROP,ALTER)

  Nowadays I prefer to automate database updates and deployment, using Liquibase and its relational database vendor agnostic syntax for that. Especially on production systems. But on local dev environments, I can still use the occasional SQL in a pinch. Source: over 2 years ago