LaunchDarkly VS Artifactory

LaunchDarkly Reviews

Artifactory Reviews

LaunchDarkly mentions (37)

• How to Add Paid Features to Your SaaS Apps

  This kind of goes without saying since it's the opposite of the first don't I listed, but it's worth restating and giving some examples. Using tools from third parties means taking advantage of what they have done so you don't have to do that work. This means you are free to build things that make your app special. I like to use feature flag tools for this. Some examples are LaunchDarkly, Split, and AWS App... - Source: dev.to / 12 days ago

• Pivoting a million dollar DevTool startup

  Taplytics is a broad A/B testing platform for marketing teams. While DevCycle is a feature flagging tool built for developers. Taplytics actually has feature flagging, but DevCycle is much more focused and plans to compete directly with incumbents like LaunchDarkly by building a better developer experience (more on how later). But with Taplytics they built so many features and every customer was using them in a... - Source: dev.to / 4 months ago

• Arc Update - 1.20.1 (43987)

  I had a custom rule added to Little Snitch that blocked the following domains: launchdarkly.com, clientstream.launchdarkly.com, mobile.launchdarkly.com. Source: 6 months ago

• Feature flags implementation in Nest.js 😻

  There are however Saas to implement directly a feature management system. Several solutions exist like LaunchDarkly, Flagsmith or Unleash.io. Using a SaaS (Software as a Service) feature flagging solution offers the advantage of a faster and more straightforward implementation process. These services are readily available and can be quickly integrated into your project. - Source: dev.to / 8 months ago

• Boost DX, Enhance UX, and Skyrocket Profits! Dive into a sub-50ms world with Edge Feature Flags 🚀

  Currently, there are numerous feature flag systems available. Options include our own company's open-source system, "Bucketeer", and the renowned SaaS "LaunchDarkly" among others. When comparing these, the following considerations might come into play:. - Source: dev.to / 8 months ago

Artifactory mentions (20)

• Where to store executables shared by a team/project

  I kind of hate it, but Artifactory seems popular at companies: https://jfrog.com/artifactory/. Source: 11 months ago

• Adding Virtual Environments to Git Repo

  When not providing all dependencies yourself, you might suffer from people deleting the packages you depend on (IMHO a very rare scenario). If it is really that critical (hint: usually it isn't), create a local mirror of Pypi (full or only the packages you need). Devpi, Artifactory, etc. Can do that or you just dump the necessary files into Cloud storage, so you have a backup. Source: about 1 year ago

• Authenticated Docker Hub image pulls in Kubernetes

  Operate a pull-through cache registry, like Artifactory or the open source reference Docker registry. This will allow you to pull images from Docker Hub less frequently, improving your chances of staying under the anonymous usage limit. - Source: dev.to / about 1 year ago

• Concretely, how do you trust the experts? That is, how do you a) identify experts relevant to something and b) determine if they have a consensus (and if so, what it is) on a given topic?

  Like suppose for a second that . . . Idk . . . a product team wants our ci workflows to start using Artifactory. Okay great, I don't know Artifactory integration but I'm going to tell them "Sure, I'll get right on that.". Source: over 1 year ago

• What do I do with large "asset" files?

  If these "assets" have an independent release schedule I would treat them separately (especially if they are externally provided). If they are not built from source then treat them as artefacts, they don't belong in git. You can store the in an artefact repository (like Artifactory of Nexus) or (as u/nekokattt points out) in something like S3. Source: over 1 year ago