WF Rules and MS BRE – Comparing Performance

I’ve been asked a few times how the performance of WF (Windows Workflow Foundation) Rules compares with that of the Microsoft Business Rules Engine (MS BRE). Having done no testing, I could only guess at the answer.
I’ve now undertaken some initial performance testing to compare WF and MS BRE, and decided to publish the results. You can read my write-up of the results here.
http://geekswithblogs.net/cyoung/archive/2007/08/12/114597.aspx

OFC409 – Workflow in Microsoft SharePoint Products and Technologies 2007: Deep Dive for Developers – Session Wrap up

Wow what a session!! Being a Level 400 session my expectation (from
those who make teched) was to go reasonably deep. I had a fantastic crowd with standing
room only in the theatre room – my last session of the day (being my 3rd) I was knackered
and ready to go out with a bang.

So I decided to jump into the Workflow Foundation and discuss *what is actually done
behind the scenes* with Sharepoint’s WF management. This was well received (and I’m
sure a few people in the audience were saying ‘So I just want to know how to approve
something’….we got onto that later) and opened up a few concepts explaining why
we do the things we do within our Sharepoint Workflows.
e.g. Task Correlation
Tokens and new Task IDs, why we need to generate new ones if we handle a task changed
event.

I then got onto some of the Sharepoint Workflow Implementations and wanted to highlight
the use of a State based workflow as opposed to the usual SequentialWorkflow.

*** DEMO CODE WILL BE POSTED SOON FOLKS *** (don’t have my vpc with
my to extract out my projects for you right now)
Slide Deck:OFC409_Mick_Badran_Workflow_Deep_Dive.v1.2.pdf
(977.98 KB)

BizTalk Pattern For Scheduled “Fan Out” Of Database Records

We recently implemented a BizTalk design pattern where on schedule (or demand), records are retrieved from a database, debatched, returned to the MessageBox, and subscribed to by various systems.

Normally, “datastore to datastore” synchronization is a job for an ETL tool, but in our case, using our ETL platform (Informatica) wasn’t a good fit for the […]

WF Down-under

WF Down-under

I’ve had alot of people ask when I am teaching WF next – if you are interested in
sitting through me talking about WF for four intense days – come to laid-back Australia.  Pluralsight is
teaming up with Readify to offer the course. 
I’m super excited since this will be my first trip to Australia.  I can’t wait. 
If you are in the area – or just want an excuse to come to Australia – sign up 😉

Applied
Windows Workflow Foundation in Australia Nov 13-17th
  



Check out my BizTalk
R2 Training.

CON309 – Advanced BizTalk R2 Concepts – my TechEd 2007 Session Wrap Up

Having 3 sessions in 1 day at the conference, this was session number 2.
 

We had a great session here and all my demos came off again!!! Except for the screen
size and the projector this particular ‘room’ used.
I was presenting at 800×600 – talk about feeling techno chlostrophobic.
I feel like I was in quick sand, trying to gasp for air…but we use what we have.

I was hoping to do an RFID demo but ‘last minute technical difficulties’ forced that
one on the back burner – I had more than enough demos for this session.

Thanks to all the folks that attended this – I had fun as I hope you did.
This session made the top ten sessions at TechEd! Whooo hooo

The demos went something like:

  1. Publishing and Consuming WCF Services from R2 – published a couple
    of Orchestrations and consumed the published WCF WS Service from a basic client app.
    I then moved the published IIS WCF WS Service into the BTS Instance host by using
    a custom WCF Adapter and configuring it accordingly.
    Next I exposed the same service as a Socket Address – all called
    from the same client with no code recompile. Which is what we want to highlight using
    WCF Services.

    I then fired up a WCF WF Webservice and consumed it from BizTalk – all pretty simple,
    but good to highlight.

  2. For the second major demo I created a WF workflow and using the BizTalk Extensions
    for Workflow, hosted this within BizTalk.

Slide Deck:
Demos: BizTalk
TechEd2007 demos.zip

CON308 – My BAM TechEd 2007 Session Wrap Up + Demo Code

Well firstly what a fantastic TechEd and all my 3 sessions went very well (with respect
to all the demos – 15 in ONE day! 🙂

For this session – CON308 Building an Enterprise-Wide Instrumentation Solution
Using the Microsoft BizTalk BAM Infrastructure
 
I had the pleasure of Rahul Garg our
great local Microsoft BTS TS. I had the pleasure of being his first
ever Microsoft presentation (virgin presenter).

So to set the scene – we discussed earlier that during the session we would both be
up on stage together and he would do a bit (20 slides) and I would do a bit (15 sldies)
then a demo. He was driving my slides (i.e. moving next through them while I was talking)

BSOD
Slide.pptx (361.73 KB)

SOA isn’t response request

<br /> Gobbledygooks · SOA isn’t response request<br />

Aug 10, 2007

I’ve often been told that one of the biggest mistakes people make when implementing a service oriented architecture is that they don’t re-architect their current architecture to become service oriented. I’ve never really understood what they meant by that until I read this article. SOA is not about adding a service based call to expose your current procedure calls as a service – it’s so much more. It’s about enabling ease of change and to create a more agile architecture.

Each of these assumptions exist in a Remote Procedure Call. They are forms of coupling, pure and simple. They fly in the face of SOA.
>
>

What do you think? Does it make sense in your world?

SOA isn’t response request

I’ve often been told that one of the biggest mistakes people make when implementing a service oriented architecture is that they don’t re-architect their current architecture to become service oriented. I’ve never really understood what they meant by that until I read this article. SOA is not about adding a service based call to expose your current procedure calls as a service […]