Thanks to visit codestin.com
Credit goes to www.scribd.com

0% found this document useful (0 votes)
28 views4 pages

Documentum DFS Vs REST API

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
28 views4 pages

Documentum DFS Vs REST API

Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 4

Documentum DFS vs

REST API
Comparison Overview for Presentation
• DFS: Client → SOAP Request → DFS Service → Content Server
• REST API: Client → REST Request (HTTP) → REST Server → Content
Server
Feature/Aspect Documentum Foundation Services (DFS) Documentum REST API

Release Year Around 2007 (D6.0 onwards) Around 2015 (D7.2 onwards)
RESTful Web Services (HTTP methods: GET, POST,
Architecture Style SOAP-based Web Services (WS-* standards)
PUT, DELETE)
Communication Protocol SOAP over HTTP Pure HTTP/HTTPS
Payload Format XML (heavy, verbose) JSON (lightweight, web-friendly)
Complex, requires client stubs (WSDL, proxy
Ease of Integration Easy, direct URL access (no special stubs needed)
generation)

Any client that can send HTTP requests (JavaScript,


Client Requirements Java/.NET specific client libraries required
Python, Java, etc.)

Performance Slower (due to SOAP overhead) Faster (lightweight JSON + HTTP)


Easier to extend/customize with additional REST
Customization Requires building custom DFS services
endpoints
Easier (especially for web developers familiar with
Learning Curve Steeper (need to understand WSDL, SOAP)
REST)

Security WS-Security (complex, SOAP header based) HTTP basic auth, OAuth (lighter security integration)

Lighter — integrated in Documentum REST services


Deployment Complexity Heavier deployment (EAR/WAR files needed)
server

Modern API Trends Legacy technology Aligned with modern API-first designs

Mobile/Cloud Readiness Difficult for mobile/web applications Mobile- and cloud-friendly

New projects, mobile apps, microservices


Use Case Today Legacy systems needing backward compatibility
integrations

Example Call Needs complex SOAP request envelopes Simple curl http://server/dctm-rest/repositories
Summary for Presentation
• DFS = Good for older, enterprise-grade SOAP integrations (Java/.NET clients).
• REST API = Best choice for new applications, mobile/ web, cloud-native systems.
• Modern Recommendation: → Use Documentum REST API wherever possible for better performance, ease of use, and future scalability.

You might also like