10 Ragioni per usare Alfresco invece che un Database
•Als PPTX, PDF herunterladen•
2 gefällt mir•3,930 views
Che cosa distingue un sistema ECM da un database relazionale? Ci sono almeno 10 buone ragioni per cui è meglio utilizzare Alfresco al posto di un database relazionale per gestire e ricercare tutti i contenuti aziendali strutturati, come documenti Office, file di testo, HTML, XML, PDF, immagini, video, ecc.
![Contenuti salvati su file system, per prestazioni ottimali (al posto dei BLOB) ,[object Object]](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Empfohlen
Empfohlen
Weitere ähnliche Inhalte
Empfohlen
Empfohlen (20)
10 Ragioni per usare Alfresco invece che un Database
- 1. 10 Ragioni per usare Alfresco invece che un Database
- 3. Conservare I documenti su un database aggiunge strati di complessità.Il content model di Alfresco salva le informazioni nel loro formato nativo, direttamente nel file system, per prestazioni ottimali di I/O dei file
- 7. Prodotti Gli “Aspect” vi consentono di far evolvere il vostro modello documentale nel tempo, naturalmente
- 8. 3. Applicare una configurazione di sicurezza granulare, a livello di singolo documento (invece che a livello di tabella o tramite applicazione ad hoc) La UI di Alfresco vi fornisce controllo diretto sulla configurazione di sicurezza di cartelle e documenti.
- 16. Domande?
- 17. Grazie! Maurizio.Turatti@Alfresco.com http://www.alfresco.com/it/ Alfresco QuickTake series
Hinweis der Redaktion
- While modern database products can store many types of information, an RDBMS construct is fundamentally designed to process text and numbers - not images and documents. To the DB, these are treated as opaque items housed in a catch-all column type known as a BLOB (Binary Large OBject).Storing documents in this way only adds another layer of processing - exactly what is NOT needed when serving up files that by definition are in the multi-megabyte to gigabyte size range.Alfresco's content model stores assets in their native format, directly on the filesystem - for maximum file I/O.
- Every CMS has its own way of representing a content model - allowing you to configure the fields, or metadata, that define each type of asset. For example, a Contract document type might need to indicate: customer id effective date total amount product(s)To achieve this with a database, you need to predefine your fields (columns). This is fine initially, but over time, requiring new fields can prove tricky. The other extreme is to pre-allocate placeholder columns - which leads to a "sparse matrix" design that is suboptimal.Alfresco allows you to naturally evolve your content model over time using metadata groups, called Aspects. You can easily define and layer these on at any time and with varying levels of granularity - to individual assets, complete asset types, or systemwide depending on your needs.
- Another area where granularity matters is security. Databases are great for defining access down to a table (type) level. However, individual row (document) security would need to be custom coded. A true CM environment needs to accommodate both.Alfresco's UI gives you direct control over document and folder security settings - and these can be inherited where needed to minimize administration.
- 4. Collaborate on how content is authored (vs just storing them)A database is a storage engine. Period. It knows nothing about collaborative elements: dealing with teams to generate interim versions of a draft that shared and reviewed.Alfresco is a full content application server. It stores assets and makes all CM features available against them - including collaboration functions.
- 5. Search - across full text and metadata to facilitate reuse (vs metadata only)All databases can index and search basic text fields (metadata); some can also index the contents of documents such as Word, PDF, etc. However, your milage may vary...Alfresco includes full text indexing and search features on all common mimetypes. And if you happen to use one that we don't accommodate out-of-the-box, our framework is completely extensible so that you can wire in new ones now, or in the future
- 6. Rules - configure asset processing based on common events (vs custom coding)A database can provide some automation via "stored procedures", but this requires coding expertise to enable.Alfresco's UI allows you to configure common tasks based on conditions (called Rules), and apply these much like security (e.g. can be inherited / re-used to ease administration). Rules are a powerful way to ensure assets are processed in a consistent fashion, regardless of how they arrive in the repository.
- 7. Workflow - control and audit how changes are finalized (vs custom coding)Databases have no native concept of workflow. Anything here would be custom code as well.Alfresco includes a complete workflow engine that can control revisions and approvals of assets - all of which are monitored / audited.
- 8. Notification - proactive alerts to inform users of recent changes (vs custom coding)Databases have no native concept of notifications. Anything here would be custom code as well.Alfresco Share can provide a unified "news feed" of activity for your review, customized based on your access level and preferences (think Facebook news feed).
- 9. Access the repository from numerous "on ramps" such as CIFS, IMAP, WebDAV, FTP, SPP (vs custom coding)Manipulating content stored in a DB is typically done thru SQL and / or a custom application.Alfresco allows content contributors to use their native authoring tools directly by providing support for filesystem (CIFS), email (IMAP), WebDAV, FTP, and SharePoint protocols (SPP).
- 10. CMIS - Leverage SQL geared for DM (vs plain SQL that you have to contort)Plain SQL is great for normal database access, but falls short when dealing with more complex asset types (as noted in point #1 on storage).CMIS (Content Management Interoperability Services) includes a query language, based on SQL-92, but with extensions for CM specific functions. Do more OOTB with the right tool, versus having to morph a different standard to do "unnatural things".