simplified business event processing

33

Upload: nigel-green

Post on 20-Jun-2015

1.233 views

Category:

Business


2 download

DESCRIPTION

Simplified Business Event Processing presentation made by Nigel Green at the Enterprise Architecture Conference (EAC) London June 2010

TRANSCRIPT

Page 1: Simplified Business Event Processing
Page 2: Simplified Business Event Processing

Nigel Green 5Di Limited

Page 3: Simplified Business Event Processing

1986 2010

Page 4: Simplified Business Event Processing
Page 5: Simplified Business Event Processing
Page 6: Simplified Business Event Processing

Joint Tactical Information Distribution System

**** **** ****

A full picture of what’s going on ….but avoiding information overload to any one individual or team.

Page 7: Simplified Business Event Processing

  Postal and express parcel companies for item tracking   Transportation and logistics businesses to manage vehicle fleets

more effectively

  Bankers looking for fraud, money laundering, or breaches of financial regulations

  Service providers seeking to minimize the mean-time-to-repair of faults

  Automobile part suppliers providing parts to manufacturers for "just in time" production.

  … and other business value networks such as: ◦  Distribution Networks - Airline Code Sharing Networks - Networked Air travel Services - Mobile

Team Collaboration - Cold Value Chains - Franchised Operations - Multi-Modal Logistics - Collaborative Government - Seaport Security Networks - International Customs - Sensor Automation Networks - Secure Information Networks - Transportation Networks - Traffic Networks - Field Service Collaboration - Meshed information

networks - Demand-driven Supply Chains…etc…etc

In all these cases and more, there is an inherent requirement to handle large volumes of data in close-to

real time.

IBM believe there are enormous financial and strategic benefits to implementing event-driven business processes, because they suit the inherently event-driven nature of many aspects of the real world.

Page 8: Simplified Business Event Processing

“A design pattern for the processing of simple events in a way that is consumable by business users which indicates an actionable business situation and enables the business to respond rapidly to opportunities and threats”.

Knowing about events helps me deal

with problems before they get out-of-hand. !

Business events are just something I’d rather know about

than not!!

A pattern for creating business Situational Awareness

Knowing about events helps me

spot opportunities

early?!

Page 9: Simplified Business Event Processing

The access to information on the Web

The use of external information and data processing services by people and corporate IT

Pervasive business event visibility within the enterprise

Visibility of business events outside the enterprise

The opening-up of data from within corporate applications and making it available in near-real-time to customers and trading partners.

1

2

3

4

5

Enterprise Enterprise IT Applications

Web

1

2

3

4 Processing

Services

5

Page 10: Simplified Business Event Processing

1

1 1 1 1

2

Page 11: Simplified Business Event Processing

  Event Processing Technical Society:

◦  Event: Anything that happens, or is contemplated as happening.

◦  Simple event: An event that is not an abstraction or composition of other events.

◦  Complex event: An event that is an abstraction of other events ..

Page 12: Simplified Business Event Processing

Think event messaging ecosystem not database….

An ecosystem! A

Database!

Page 13: Simplified Business Event Processing

Event Publishers to whom I’m Subscribing

RESTful Pub-Sub

API

Searchable event logs

Subscribers waiting to consume events

Short event messages with hyperlinks to

further content

Imagine for a moment if physical objects could Tweet, what would they tell us?

Page 14: Simplified Business Event Processing

Publishers

Staging Queues collect fulfil haul sort haul sort store haul deliver Event

Messages

Web of Business Events

People, applications and appliances publish event messages to staging queues (logs) that exist inside a

web of business-events.

Page 15: Simplified Business Event Processing

Publishers

Staging Queues collect fulfil haul sort haul sort store haul deliver Event

Messages

Subscribers

Business Intelligence

Customer Service

Enquiries Network Capacity Planning

Client-facing Solutions

Billing

Operation Reporting

Inter-company Inter-operation Third Party

Integration

People, applications and appliances subscribe to event messages via their staging queues (logs) that also exist

inside a web of business-events.

Page 16: Simplified Business Event Processing

collect fulfil haul sort haul sort store haul deliver

Components Applying Rules

Software components (agents) apply filtering and aggregation rules that control the flow of messages and

ensure the subscribers only see the events they’re interested in.

Page 17: Simplified Business Event Processing

Business knowledge in here

Action Agents

Event-Triggered Business Logic

Agents do specialist tasks that can create

new events

No business knowledge here but really good at moving lots of messages around and making

them searchable

Other software agents execute specific business logic: e.g. verify information, execute transaction or notify

customer

Page 18: Simplified Business Event Processing

Get only the events that are needed

Staging Q

ueues

Similar to searching on the Web. If you need the latest event you can search rather than subscribe.

e.g. Customer Service Request

Searching in parallel across publishers

Page 19: Simplified Business Event Processing

Think event messaging ecosystem not database….

An ecosystem! A

Database!

Page 20: Simplified Business Event Processing

In the first quarter of 2010, 4 billion tweets per quarter were posted.

There are 600 million search queries on Twitter per day (April 2010).

Twitter gets 3 billion requests a day through its API.

Page 21: Simplified Business Event Processing
Page 22: Simplified Business Event Processing

Web Oriented Architecture: •  e.g. REST, micoblogs, RSS •  mainstream since mid’00s

Message Oriented Middleware : •  e.g. Asynchronous Transactions, Pub-Sub Channels, Control Queues •  Mainstream mid-90s

Staged Event-Driven Architecture: •  e.g. Staged Queues, Traffic Throttling •  Since 2000

Auto ID and RFID Architecture: •  e.g. Edge-processing, EPCIS, Object ID •  Started circa 1999

A foundation for Business Situational Awareness without the need to buy or build exotic software.

Page 23: Simplified Business Event Processing
Page 24: Simplified Business Event Processing

24

Container: Human Brains

Container: Applications & Databases

Container: The Organisation

Container: Web Communities

Highly Internalised Highly Externalised

Page 25: Simplified Business Event Processing

25

Container: Human Brains

Container: Applications & Databases

Container: The Organisation

Container: Web Communities

Highly Internalised Highly Externalised

Information is either not visible or not available outside its container.

Not all business processes automated by

IT and customer/partner information

limited

Applications & Databases are built to meet vertical needs

Shadow IT is used to

support gaps in corporate IT

Blind Spot

Blind Spot

Blind Spot

Blind Spot

Blind Spot

Blind Spot

Blind Spot

Useful Information and services might be out there… Is my business visible to these

communities?

Page 26: Simplified Business Event Processing

26

Container: Human Brains

Container: Applications & Databases

Container: The Organisation

Container: Web Communities

Highly Internalised Highly Externalised

Differing values, trust issues, poorly considered policies and narrowly-focused change methods strengthen barriers

Barrier

Values

Policies

Trust

Methods

Barrier

Values

Policies

Trust

Methods

Barrier

Values

Policies

Trust

Methods

Page 27: Simplified Business Event Processing

Systems Behaviour

Events

Values

Policies Content

Trust

VPEC-T

Page 28: Simplified Business Event Processing

http://www.morguefile.com/archive/?display=199341&

Page 29: Simplified Business Event Processing

synchronous transactions

duplicate event message handling

eventual consistency versus strong consistency

information confidence marking event granularity

configurability versus unintended

consequences

event network control mechanisms

edge processing strategies

idempotency

value network analysis versus six sigma

fuzzy versus precise events event taxonomies

object identity

event payload content state machine versus event ecosystem

Page 30: Simplified Business Event Processing
Page 31: Simplified Business Event Processing

ç

Page 32: Simplified Business Event Processing

1.  Can you see an opportunity for improved Situational Awareness in your organisation?

2.  How would you design information systems if: ◦  every business activity could make process state changes

broadly available ◦  physical objects could tell you their whereabouts and status

…in near-real-time?

Page 33: Simplified Business Event Processing

[email protected] www.5dinnovation.com

Twitter: 5Di Twitter hash tag: #sbep

Simplicity By Design