All blogs / Software / engineering practice
David Hurtado's Integration Traces
learn.microsoft.com/en-us/archive/blogs/dhtoran
Yet another blog about BizTalk, Architecture, and some fuzzy acronyms such as EAI, SOA, ESB, EDA, CEP, MSFLA, etc.
Software / engineering practiceC# / .NETMicrosoft blogsMSDN archive
- Posts
- 33 from 6 Apr 2005 to 16 Jul 2009
- Posting
- archived, read-only
- Kind
- personal blog
- Feed
- https://learn.microsoft.com/en-us/archive/blogs/dhtoran/feed.xml
2009 9
- Introduction to xRM. One Platform. Many Applications
- Bumptop and User Experience: Creating new problems and solving them
- Book review: SOA Patterns with BizTalk Server 2009 (II) – WCF Primer
- ESB Toolkit 2.0 released
- Book review: SOA Patterns with BizTalk Server 2009 (I) - Refresher
- Cite: SOA, build or buy
- New book and free chapter: SOA Patterns with BizTalk Server 2009
- Connecting systems – From Object Oriented to ESB for dummies
- New BizTalk HotRod Magazine – Issue 6 Q2 2009
2008 1
2005 23
- Workflow matters
- BizUnit 2.0 released
- Easy Promotion of Context Properties
- Fun with BAM and orchestration execution time
- Calling A Receive Pipeline Inside an Orchestration in BizTalk 2006
- Why (good) Xml is much better than plain text
- Fun with ConfigFramework (updated)
- Compiled BizTalk 2004 Help File (.chm), indexed with MSN Desktop Search
- New whitepaper about BizTalk Messaging Internals
- BizTalk messages based on .NET types instead of Xsd schemas
- What Videogame character are you?
- Real asynchronous vs. Simulated asynchronous
- Question: Secure the access or secure the content?
- Orchestration Error handling: Fix-and-Log
- Suddenly SOA does not exist!...
- Hierarchical naming convention for messaging artifacts
- Integration with messaging: Command messages and Document messages
- Team development with BizTalk: new white paper
- Schema design: do include support for Errors and Warnings
- Programming inside orchestrations: Where should I put the code?
- Orchestrations as Business Processes, not Technical Processes (Part 2, Development)
- Orchestrations as Business Processes, not Technical Processes (Part 1, Design)
- Introducing the blog (and myself)