Flagsmith VS Apache Camel

Flagsmith Reviews

Apache Camel 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 / 18 days 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 / almost 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

Apache Camel mentions (12)

• Ask HN: What is the correct way to deal with pipelines?

  "correct" is a value judgement that depends on lots of different things. Only you can decide which tool is correct. Here are some ideas: - https://camel.apache.org/ - https://www.windmill.dev/ Your idea about a queue (in redis, or postgres, or sqlite, etc) is also totally valid. These off-the-shelf tools I listed probably wouldn't give you a huge advantage IMO. - Source: Hacker News / 8 months ago

• Why messaging is much better than REST for inter-microservice communications

  This reminds me more of Apache Camel[0] than other things it's being compared to. > The process initiator puts a message on a queue, and another processor picks that up (probably on a different service, on a different host, and in different code base) - does some processing, and puts its (intermediate) result on another queue This is almost exactly the definition of message routing (ie: Camel). I'm a bit doubtful... - Source: Hacker News / about 1 year ago

• Can I continuously write to a CSV file with a python script while a Java application is continuously reading from it?

  Since you're writing a Java app to consume this, I highly recommend Apache Camel to do the consuming of messages for it. You can trivially aim it at file systems, message queues, databases, web services and all manner of other sources to grab your data for you, and you can change your mind about what that source is, without having to rewrite most of your client code. Source: over 1 year ago

• S3 to S3 transform

  For a simple sequential Pipeline, my goto would be Apache Camel. As soon as you want complexity its either Apache Nifi or a micro service architecture. Source: over 1 year ago

• 🗞️ We have just released our JBang! catalog 🛍️

  🐪 Apache Camel : Camel JBang, A JBang-based Camel app for easily running Camel routes. - Source: dev.to / over 1 year ago