what not to build using the Alfresco repository

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-13-2014 11:24 PM
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.
I guess I'm asking… what kinds of systems are not a good fit for the Alfresco data store?
thanks.
Labels:
- Labels:
-
Archive
2 REPLIES 2
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2014 07:38 AM
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.
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.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
12-14-2014 12:14 PM
