4 ms·
This is a subject near and dear to my heart, albeit from the "enterprise" side of the table, not the scrappy startup side. I've spent a non-trivial amount of e
by davidmr 10y ago
This is a subject near and dear to my heart, albeit from the "enterprise" side of the table, not the scrappy startup side.
I've spent a non-trivial amount of effort trying to convince software companies to spin an on-premise version of their software. Sometimes with success, and sometimes not. I understand that it's quite attractive to rely on AWS or GCE abstractions to the point where it would be nearly impossible to break it apart for installation on my boxes, but it seems like it's leaving quite a lot of money on the table.
There are perfectly valid reasons to require on-premise applications: in-house interpretation of regulatory requirements, protection of intellectual property, etc.
Of course, I have a right to ask and they have a right to say no, but I wish more companies would consider making an on-premise solution. (Slack, I'm looking in your direction. Please come take the money I'm currently giving to Atlassian.)
- tomjen3 10y agoGiven how much code is on github, I no longer think protection of intellectual property is a valid excuse. It may be a requirement from your boss.
- mseebach 10y agoThat's not really how thinking about security works. "But everybody else is doing it" wasn't a valid argument in school, still isn't. As a thought experiment, (ignoring the fact that it's not an appropriate store for such things, and only thinking about security towards third parties) how would you feel about a company storing your PII/medical records/credit card number in a private repo on GitHub? That's how your boss thinks about the company's intellectual property.
- tomjen3 10y agoWhy would I feel any different if they stored it on Amazon cloud, github or on their own systems?
- davidmr 10y agoI'm sorry, but I have absolutely no idea what you're trying to say. Would you mind providing an alternate phrasing for your comment?
- kordless 10y agoThe problem is with licensing and trusted deployments. Having done the high level of the architecture for one possible solution, I can tell you we are about 3-4 years out before this is common practice.