The Success and Failure of Moving to a Message-Based Architecture

The Success and Failure of

Moving to a Message-Based

Architecture

[email protected]://twitter.com/beefarinohttp://www.beefycode.comhttps://github.com/beefarino

Jim ChristopherCode Owls LLC

http://www.codeowls.com

SELECT *FROM STUFF

WHERE TYPE=‘AWESOME’

Message

Persisted representation of work to be done across an application seam.

• Database Insert• Web Service Request

Queue

A place to which to write messages.A place from which to read messages.

• MSMQ• RabbitMQ• Azure / Windows Service Bus• SQL Server Service Broker• Filesystem & SQLite

Queue

A place to which to write messages.A place from which to read messages.

• FIFO• Transactional• Reliable, Persistent, Durable• Routing Features

Queue Consumer

A process that pulls messages from queue.

QUEUECONSUMER

I NEED DATA

QUEUECONSUMER

QUEUECONSUMER

I NEED DATA

???

QUEUECONSUMER

I NEED DATA

QUEUECONSUMERALL THE DATAS

QUEUECONSUMER

ALL THE DATAS

QUEUECONSUMER

CLIENT O C

Display( 2500 )

Web Service SQL Server

VendorServices

VendorServices

ADLOG AD

PLAYPROOF OF

PLAY

UNRELIABLE

2 MBX 2500 ~ 5GB

ADLOG

VendorServices

ADLOG AD

PLAYPROOF OF

PLAY

VendorServices

PROOF OF PLAY

ADPLAY

ADLOG

QUEUECONSUMER

ADLOG

QUEUECONSUMER

ADPLAY

ADPLAY

QUEUECONSUMER

!

ADPLAY

VendorServices

PROOF OF PLAY

ADPLAY

ADLOG

20 1025000

VendorServices

25000 25 10

VendorServices

VendorServices

MSMQ!

MSMQ!

MSMQ!

MSMQ!

[email protected]://twitter.com/beefarinohttp://www.beefycode.comhttps://github.com/beefarino

Jim ChristopherCode Owls LLC

http://www.codeowls.com

The Success and Failure of Moving to a Message-Based Architecture

Technology

Transcript of The Success and Failure of Moving to a Message-Based Architecture