• Like
  • Save
Evolution of wcf
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

Evolution of wcf

  • 215 views
Published

This Presentation elaborates on how WCF evolved gradually.

This Presentation elaborates on how WCF evolved gradually.

Published in Technology
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
215
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. COM (Component Object Model)DCOM (Distributed COM)COM+.NET RemotingWeb ServicesWCF (Windows Communication Foundation)Object OrientationMonolithic Applications5/30/2013 WCF Evolution by Sunny Kumar 1
  • 2. Monolithic Applications• Fox Pro and MS-Access application (Data andcode at same place).• SQL Server/ Oracle were used on network butthe application was still a monolithic one.• Problem: Takes lot of time and no reusability.5/30/2013 WCF Evolution by Sunny Kumar 2
  • 3. Object Orientation – (1980’s)• Polymorphism• Encapsulation• Sub-Classing (Inheritance)• Problem: it by itself didn’t facilitate the dynamicevolution of software at runtime. Once anapplication was built, it was static. There wasn’t aneasy way to infuse new code into an application.5/30/2013 WCF Evolution by Sunny Kumar 3
  • 4. COM (Component Object Model)• Write code once and use in multiple applications.• Location Transparent• Tight Coupling• Runtime Metadata (Self Describing System)• Problem: worked well on single machine (usingmethod invocation on an object reference) we hitscaling problems when we tried to stretch it outand apply it as a substrate for distributed softwareintegration(across machines)5/30/2013 WCF Evolution by Sunny Kumar 4
  • 5. DCOM (Distributed COM)• Network version of COM – Sharing COM over anetwork.• Biggest Failure of Microsoft as not at all reliableand scalable.5/30/2013 WCF Evolution by Sunny Kumar 5
  • 6. COM+• DCOM +MTS (Transaction Services)• Object Pooling and Just In Time Activation5/30/2013 WCF Evolution by Sunny Kumar 6
  • 7. .NET Remoting• Option for .NET developers for distributedapplication development.• Best option only when both client and server areon the same network.5/30/2013 WCF Evolution by Sunny Kumar 7
  • 8. Web Services• Provides Object Functionality over HTTP.• Data is exchanged over the network in XML format.• SOAP is the protocol used for communication.5/30/2013 WCF Evolution by Sunny Kumar 8
  • 9. WCF (Windows Communication Foundation)• Next Generation of web services withenhancements.• Supports sending messages not only using HTTPbut TCP, Named Pipe and MSMQ.• Support for sending messages using formats otherthan SOAP including REST and PLAIN OLD XML(POX).• Facility of Managing Transactions and reliablesessions which are NOT in Web Services.5/30/2013 WCF Evolution by Sunny Kumar 9
  • 10. 5/30/2013 WCF Evolution by Sunny Kumar 10