Build Your Business With Open Source

PCM2 writes "InfoWorld this week is running a ten-page guide to building your business entirely with OSS. The guide highlights OSS alternatives for many enterprise applications categories such as CRM, ERP, content management, and so on. It's not exhaustive, but where it skips the obvious categories like databases and Web servers it includes some others that you might not expect."

Comments

Re:Who is listening?

[TripMaster Monkey]

Actually, I've recommended a few open-source alternatives to my management, and so far we've saved a few grand. My boss will do just about anything to save on the bottom line, and when I tell him that I can fill a particular need with OSS and get out cheaper, he's beside himself wth joy.

Re:Bookkeeping software

[UnderScan]

The only quickbooks that I have used was a version for DOS back in 1995, so take my advice with a grain of salt. I haven't used this product myself, but Linux Canada makes Quasar a GPL'd accounting program. If you need it, you can buy tech support from them & if necessary you can buy the close source edition too.

Re:Huh?

[TheRaven64]

That's a myth. It depends on the vendor. Microsoft is simply not going to close it's doors in our lifetime. I'd bet my life on it.

Vendor lock-in is not about the company going bust. How long will the product you are using be maintained? When it is not, what are your migration options? How much will it cost?

With a Free package, you can pay someone indefinitely to back-port security fixes from the latest branch (which need only be a day or so a month, and can be cheap).

Plus, with databases, vendor-lock in is a moot point. Why? A. No competent business will change it's main database willy-nilly.

Exactly. Which is why you do not want to have to depend on a single source for support. If MS decides to EOL your DB five years after you deploy it, then this is a problem - it means you need to test the latest version, buy copies of it, and migrate. If it still works then all you want is to keep receiving security updates. Sounds like you want a Free DB...

If your company is doing anything with the database more complicated than a recipie list, any competent database developer is going to use stored procedures heavily, which are ALL database-specific.

So there is database lock-in, but not vendor lock-in. These are different things. I can easily use a different consultant to maintain my ultra-stable (only bug fixes allowed) branch of PostgreSQL - I can't do the same with MS SQL.