what not to build using the Alfresco repository

As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.

rocketboy2000

sorry that I'm rather new to Alfresco. in my environment it has been suggested that we build a product that has been traditionally done using MS Access. thus, there is no ECM requirement. is using the Alfresco repository as a traditional data store problematic? my impression is that reporting would be greatly hampered over traditional relational models.

I guess I'm asking… what kinds of systems are not a good fit for the Alfresco data store?

thanks.

mrogers

alfresco is not a replacement for Ms Access.    A relational db like SQL server is what you should be using if you have a heavy relational requirement. (No one should use Access for a serious application.).    For example

Where alfresco comes in is if you have content (documents) to manage.   So technical drawings,  policies and procedures, music archives, sales proposalls.  Those sorts of things.

You don't write something like your accounts system with alfresco (because that's relational data).  However you could use alfresco as part of a bigger system e.g.  To store  invoice documents.