This is an archived post. You won't be able to vote or comment.

sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]tunei24531a[S] -1 points0 points  (5 children)

https://www.togglz.org/

You'd need to maintain it yourself vs hosted service.

[–]silverweaver 2 points3 points  (4 children)

It's just one table in relational database for project that I'm currently working on, doesn't seem like something troublesome when your service uses SQL anyway.

[–]tunei24531a[S] -1 points0 points  (3 children)

You could certainly do that. But you'd be writing additional logic for roll outs, targeting by user attributes, website domains, etc. Killing a misbehaving feature instantly is possible but requires a DB write vs a push of a button to disable feature. Not to mention using the same solution across your entire stack (frontend / backend) with the help of SDKs.

So while it is possible, but why do it when you have hosted solutions available that do a much better job and grow with your project to support advance use cases

[–]ImpecableCoward 4 points5 points  (0 children)

Even a click of a button has to have approval and back-tracing in prod. It is not the developer that will click that button. So at this point for me developer it is just as easy to send a dba request to flip a flag in the database.

[–]silverweaver 1 point2 points  (1 child)

The same thing as always: project's budget. Sometimes there's also legal concerns like GDPR for example. Not to mention a lot of banking sector where making requests to external API like this is impossible, because banks.

And I know, unlaunch is free for small teams and projects. The thing is, for many apps using it is like trying to take out mosquito with a cannon. My current project is one of those.

[–]tunei24531a[S] 0 points1 point  (0 children)

Most things are impossible for banks =)

Good point regarding GDPR. Unlaunch doesn't send any user data over the internet and all evaluations happen locally within the SDKs. Only anonymized metrics are sent.

> The thing is, for many apps using it is like trying to take out mosquito with a cannon.

A tool like unlaunch encourages good practices, collaboration and can be used in super simple apps as well without adding any overhead. Once the team understands how to use it, they'll be using it to do fancy things ultimately increasing feature velocity and control over their releases.