Is there any there any scenario where we have to publish "Orchestration as WCF Service" and not "Schema as WCF service"

Question

Hi All,
Recently in one interview a senior architect asked me this question-
Q- In which scenario we have to publish "Orchestration as WCF Service" and not "Schema as WCF service".
He also told there are some scenarios which can't be accomplished by exposing schema as WCF Service.
As per my understanding below are the benefits of exposing Orchestration as a web service, but there is no such scenario where we can't be achieved by exposing Schema as WCF Service.
Publishing orchestrations is a way to go when:
Implementing simple solutions with small number of dependencies when we have control over both consumer and service endpoints
* Rapid prototyping, proof-of-concepts, service stubs
* Developing local scoped services, when collaboration is not an issue
* Don’t care much about interoperability
* No skilled XML Schema, WSDL developers available
(http://geekswithblogs.net/paulp/archive/2006/03/21/72943.aspx)
Please share your inputs.
Thanks,
Prashant
Please mark this post accordingly if it answers your query or is helpful.

Answer 1

First, the answer to the question as written is NO, because there really isn't a difference between the two options.
To be more specific, the only difference is in the Wizard itself in that when you publish an Orchestration, the Wizard reads the request/response schema(s) and Service & Operation name from the Orchestration Port rather than asking for them as it does
when you choose Publish schemas.
Basically, if you choose Publish schemas and enter the same values configured in the Orchestration Port, the output will be the same.  So, publishing an Orchestration is merely a convenient shortcut.
Most importantly though, all of this only affects the metadata publishing.  There is no difference in the Receive Location (BizTalk or IIS), if you chose to create one.  The receive stack is schema agnostic, always.
In practice, the only thing the Wizard does that is difficult to do manually is organize the metadata, but I haven't had to create a metadata endpoint in years.  The only reason I even run the Wizards is to create the IIS app.