3 ms·
If you hark back to the days before, say even 2010, there just weren't many SaaS's that worked or were affordable. We ran our own ticking system, chat, accounti
by marquis 13y ago
If you hark back to the days before, say even 2010, there just weren't many SaaS's that worked or were affordable. We ran our own ticking system, chat, accounting, hosting, email servers, error reporting, server load checks.. it was all handmade cobbled together from open source and when we were running as fast as we could to get products together it was quite a mess yes, but there was no Github, Google Apps, Hipchat, OpenHosting, whathaveyou, and looking at our own list I see we have now a huge amount of stuff we used to build ourselves thanks mostly I suppose to what we find on HN as it comes up, and the article is spot on - definitely costs less than a full time employee to run all this.
However my point? This is all terrible for security, we're reliant on someone else's data integrity, and I would assume it's safe to say that if we had the time to have someone do all this in-house and maintain good documentation we wouldn't hesitate, given the security and data integrity tradeoffs.
- pm 13y agoYou make some good points, and HN has been such a boon for finding new services to integrate. Of course, if we could all do it in-house reasonably we'd all be doing that no doubt, but it's just not feasible, even for large corporations. Who can justify the cost? Security is always a concern, and I do hope most services have taken heed of online security breaches in recent history. However, I don't find it an argument against using SaaS because most of the time, the security from doing software in-house is dispelled by poor security in meatspace, i.e., social engineering (which is WAY easier to do than people suspect).