OHS Vs OTD (Oracle Traffic Director)

OHS	OTD
OHS is primarily an Apache based web server  and can do forward and reverse proxy functionality	OTD is primarily a high performant HTTP and TCP software load balancer, designed for scalability and high throughput
a Web Server is required to serve static content and also to do proxy capability, then OHS is a better choice.	If full fledged software load balancer with request throttling, draining, Quality of Service, is required then OTD is probably a better choice
OHS can be used to deploy some static content.	OTD does not expose the ability to serve static contents.
OHS is used when high throughputs are not required.	Used when looking for better monitoring / troubleshooting / tuning for high throughput deployment requirements
Used when it is fine to restart the web servers occasionally for configuration changes.	No Downtime required for applications as backend servers can be added/removed dynamically.
	HTTP responses from the backend servers can be cached. OTD provides a built-in mechanism for caching .