3 ms·
> Use accounts/permissions from Active Directory If users want that, they tend to be enterprise customers, and you can charge money for your software. That's g
by perlgeek 7y ago
> Use accounts/permissions from Active Directory
If users want that, they tend to be enterprise customers, and you can charge money for your software. That's good for the programmer :-)
Users who want AD integration also want (generalizing a bit, of course):
* Audit logs
* Metrics export to common BI tools
* APIs
* Separate billing address
* Role-based access control
* a way to sync data between different environments
... and so on. It's amazing how much work you as a programmer could spend "enterprisifying" a simple application.
I kinda wish for better tooling to make enterprise-ready applications, so that many of these things are less effort.
- PaulRobinson 7y agoEnterprise tooling probably needs to make event sourcing out of the box easy to do, with metrics being either a real time stream they can tap into, or an ETL process fed by that stream. Having a decent integration layer is important: I'm about to spend my Christmas "enjoying" Apache Camel installs to get up to speed there, and it's probably wise to move all auth out to something like Keycloak so that it's just "done" and federation back to AD is config, not code. As to getting data synching between environments, well... that gets fun all by itself...
- AndrewDucker 7y agoNot just Enterprise customers in the "the Enterprise is the customer" sense - if you work as a software dev in an enterprise then your users want to be able to use their normal password, and not create a new one for your app.
- blowski 7y agoBasically, SOC II certification. Having that significantly increases the opportunity to sell into enterprises, because they don’t need to do a lot of security audit work before buying.