We'd like to make ConfigCat avaliable for as many users as possible. Our SDKs are avalible in multiple languages. But still lots of our users missed Ruby support in ConfigCat:
"Does configcat have Ruby sdk??"
"So I am sad you don’t have a ruby client I can see."
"Are you plannig to support ruby?"
Finally we decided to create a standalone Ruby SDK.
Ruby is an interpreted language. It's very similar to Python and we already have an SDK written in Python. Taking advantage of this, the first idea was that we simply convert our Python code to Ruby and everything will be just fine.
You created a new software feature, put it behind a feature flag, and deployed it to production.
Now, you want to enable this new feature to some of your users, so you get early feedback, before releasing the new feature to your whole userbase.
But whom to release the new feature first?
How to choose the first user segment?
And how to target them with feature flag rules?
Lets see some typical real world examples how big companies do it.
Release based on Company, or Email address
A great first step is to enable the new feature to your colleagues, while keeping it hidden from the rest of the world.
This enables you to get early feedback from users inside of your company.
You'd be surprised how much bug they'll catch on the first day!
Here is how you can segment and target your colleagues with one simple rule in ConfigCat:
If you're a software reseller you are allowed to buy a ConfigCat subscription for your client.
You are allowed to resell one subscription to one client only.
Of course, you are allowed to resell more subscriptions to the same client.
2FA is a way of granting access to users only after presenting two separate pieces of evidence (factors). One of these factors is usually a password which the user should know and the other factor something they have or even something they are. This way you can be sure that only knowing your password won't be enough for an attacker to gain access to your account.
How does 2FA work in ConfigCat?
In our case the first factor is password you use to login to ConfigCat Management Console. The second factor is a 6-digit number generated via an Authenticator App.
As feature flags are getting popular, an ever-growing number of developers are facing the challenges associated with them.
No matter if you implement your own feature flag library, or choose a hosted feature flag service like ConfigCat, chances are high you want to use your feature flags in your frontend and in your backend services as well.
If your feature flags can be toggled on a central feature flag dashboard, such as
Our architecture, stacks and why did we choose them. A recipe for SaaS startups for an affordable, scalable and high-performing system that scales well.
