Embed Size (px)
DESCRIPTION
After completing a POC typically we are left with a lot of open questions, most importantly how do we adopt this thing across the organization? How do you begin to integrate the new message patterns and concepts into your legacy code bases? How will your development teams adopt the new tools and more importantly all the new concepts? In this session, discover how using NServiceBus transforms the way we think about design and how we approach our work. Learn how typical three tiered designs just seem to disappear and how business processes start to become workflows. See the recorded session here: https://particular-1.wistia.com/medias/t9lt8x1xyh
Citation preview
Beyond the POCAdopting NServiceBus
Introduction Adam Fyles
Solution Architect
Using NSB since v1.9
NServiceBus Champ
Upstate NY, US
Contact Info
adamfyles.blogspot.com
The tablescape Regional Grocery Retailer
- Wine & Spirits
- Restaurants
90+ Stores in 6 states
Millions of customers
Medium to large IT department (~250)
Extremely high volume stores
Let me in! Lots of competitive products, why do we need another one?
Batch jobs work just fine!
Lack of SOA understanding
Operations used to FTP
The progression
SagasPub/SubPoint to
PointLoad
Balancing
Load Balancing: OMS Determines how to best source product in the supply chain based on demand
Inherently batch based due to wave planning in either WMS or MFG
Requires massive throughput (by order line item) in a tight window
No commercial system could do it without heavy custom configuration and a ridiculous amount of hardware
Team was experienced PowerBuilder developers
Solution Solution was to decompose orders and optimize by distribution “network”
Run aggregate demand through with the Distributor
Distributor
Worker 1 Worker 2
DB
WMS
Transportation
Publish
Ord
ers
Order Entry
Order Entry
Order Entry
Distributor Demo
Store
Corporate
Supply Chain Proliferation
PurchasedWMS
Integration Endpoint
HTTP
PurchasedCAO
Master DataForecasted
Orders
DataBus
Other Systems
DataBus Customization Demo
Takeaways… Replaying messages!!
Required more DevOps
MSDTC Tricks
Stay inside the stack
Point 2 Point: Mobile Built an entire REST API around all of our Marketing tools Products Recipes Shopping Lists Online Ordering Search Ratings and Reviews
It must be fast and durable!
Request/Response is not an option
Mobile Solution Solution was point to point integration to backend systems of record
FlakyDB
Mobile
API
View ModelReads
Writes
Web
3rd Party
NSB
Writes
Customer Facing Proliferation
API
Reads
RX PortalOffisite Vendor RX
System
WritesNSBWrites
Customer Care
RX Service Desk
Custom Fault Manager Demo
Takeaways… Asynchronous performs well
Messaging trumps fragile backends
Leverage local resources
Pub/Sub: Pricing Legacy Mainframe System
Lots of price changes
Wide Distribution Network All Stores – POS, Scales, Signs Online – Web, mobile, email
Legacy Integration Find the weak point where you can enter the host
Solution
DB
Publisher
Email WebMobile
Signs
Scales
POS
Mainframe
CDC
Workflow: Benefits Registration Series of questions
Plan selection
Open window of opportunity
Solution
Step 1
Step 2
Step 3
Saga Storage
SharePoint Site
NServiceBus
Metrics
Reporting
Takeaways… Don’t reinvent the wheel
Focus on business process
Sum it up!
Efficiency
Focus
