While I was at the San Francisco launch of Visual Studio 2005, SQL Server 2005 and BizTalk Server 2006, it struck me what an important milestone the event was in BizTalk’s life cycle. For the first time, BizTalk has been elevated to a high-profile position among Microsoft’s developer toolset. For many developers that have never really had any exposure to BizTalk, this makes it real and should get their attention. If you’re a BizTalk developer, then you’re in a great position right now as demands for you skills are about to go ballistic. Scott Woodgate just did an excellent post on his blog about this.

In fact, if you’re a REALLY good BizTalk developer (architect type with multi-years BTS experience that at night dreams about pipeline components and messaging patterns) and you’re looking for a new gig working with a highly-talented team, I’d love to hear from you. Drop me a note and CV at my first name, plus a “.“, plus my last name, at “Neudesic“, plus a “.com“.

This seems like a great time for me to share something I came across while doing an “architectural dig” (that’s what I call the every-year-or-two cleanup of my office). I don’t know how many of these CDs were run, but I don’t think it was very many.

Yes, that’s “copyright 1999”.

What a long way we’ve come, in a short period of time, from this CD to the current gig I’m on in the Bay area. We’re building an ESB to support SOA and EAI, featuring 56 procs of BizTalk. I can’t imagine how I would do this without BizTalk. I suppose it _could_ be done, but it’d take a TON of custom app dev, cost orders of magnitude more, and take a very looong time to deliver. We’re building it with a relatively small, fast moving team and the end result will be highly extensible, scalable, and reliable.

BizTalk developers…. The next couple of years are going to hold a lot of opportunities. Enjoy the ride!