-
Top Three Posts
Free updates by email
-
Recent Posts
Categories
- Agile
- API
- Architecture
- Automation
- AWS
- Booking Practice
- Business Rules
- Cloud
- Conferences
- Connectivity
- Continuous Integration
- Data Flow
- Data Mapping
- Databases
- Derivatives Industry
- DevOps
- Docker
- Domain Model
- EMIR
- Enterprise Integration
- Enterprise Wide Data
- Eurex 13
- FpML
- High Frequency Trading
- Home Computing
- Humour
- ISDA
- Jenkins
- JMeter
- Kanban
- MariaDB
- Message Queue Software
- Messaging
- Messaging Standards
- MiFID
- Models
- MTFs
- Music Production
- Oracle
- Orchestration
- Project Management
- Rapid Application Development
- Regression
- Regulatory Reporting
- Replay
- Risk Management
- Rogue Trader
- Routing Rules
- Rule Engines
- Scrum
- Security Exchanges
- Smoke Testing
- Static Data
- STP
- Test Automation
- Test Data
- Testing
- TICK
- Time Recording
- Trade Flow
- Trade Organisations
- Travel
- Uncategorized
- Vendors
- VirtualBox
- Virtualisation
- WaveMaker
Tags
- adapter framework
- agile
- Asynchronous
- AWS
- break
- CCP
- ClearVision
- Cloud computing
- Consolidated Tape
- Continuous Deployment
- Continuous Integration
- devops
- Docker
- EC2
- edge case
- Enterprise Integration
- Enterprise Integration Patterns
- eurex 13
- family
- FFastFill
- fpml
- Google App Engine
- HTTP API
- IDX
- infrastructure
- Jenkins
- logging
- Messaging Systems
- Middle Office
- OTC
- Post-Trade
- Project Scope
- regression test packs
- rules
- Rules engine
- screen time
- SEALS
- security
- sequencing
- static data
- STP
- SunGard
- testing
- use case
- workflow
Category Archives: Business Rules
Success with Matching Engines – what does that look like?
Implementing a Matching Engine application presents a host of challenges. If you’re responsible for such a project then you need to give serious consideration to a number of critical system components. Here are just a few of the questions … Continue reading
Posted in Business Rules, Messaging, Models, Project Management, Regression, Risk Management, Routing Rules, Rule Engines, Test Automation, Testing
Tagged automated, complexity, data set, downstream, engine, false positives, freeze, implementation, legacy design, matching, overlap, overlapping, problem space, regression, release, requirements, result set, rework, rule management, rules, slice and dice
Comments Off on Success with Matching Engines – what does that look like?
Improving operational efficiency – Kanban and Basecamp
We’re big fans of Basecamp here at Red Hound. We use it to collaborate on projects, to run our management activities, drive our recruitment and even for booking and approving leave. I wanted to share with you our recent experiences … Continue reading
Posted in Business Rules, Kanban, Project Management
Tagged Basecamp, Kanban, unplanned, workflow
1 Comment
Not modelling your workflow? Here there be monsters!
I wanted to share a recent project experience with you that further strengthened my belief that a picture paints a thousand words. It helped to identify the root cause of a show-stopping problem where other efforts to do so had … Continue reading
Posted in Business Rules, Data Flow, Domain Model, Messaging, Models, Replay, Risk Management, Routing Rules, Rule Engines, Smoke Testing, Trade Flow, Uncategorized
Tagged adapter, adapter framework, complex, conflict, deep dive, entry rule, exit rule, infrastructure, logging, Messaging Systems, refactor, regression test packs, root cause, Rules engine, test rig, testing rig, the code documents itself, trade capture system, upstream, walk through, walkthrough, workflow
Comments Off on Not modelling your workflow? Here there be monsters!
5 Things you need to know about Routing Rules
Here at Redhound, we have a wealth of experience of enterprise integration and messaging projects. Here we’ll share some more of that experience with you around the Routing Rule Engine (RRE). At the end of it, you’ll have a better … Continue reading
Posted in Business Rules, Models, Routing Rules, Rule Engines, Uncategorized
Tagged adapter framework, Asynchronous, breaks, business rules, choke points, complex routing, Enterprise Integration, messaging project, mi, regression test packs, Rules engine, workflow
Comments Off on 5 Things you need to know about Routing Rules
Business Rules and Engines
This topic expands on my previous post “Increasing STP Rates – the Fantastic Four“. Specifically, I’m going to expand on the role of the centralised Rules Engine, what it does and how to use it. (). You’ll no doubt have … Continue reading
Posted in Business Rules
Tagged break, data handling, drools, enrichment, filtering, regression test packs, routing rules, Rules engine, schema, sequencing, STP, validation, wolf framework, xml
Comments Off on Business Rules and Engines
Don’t dis the “As Is”!
So, your project has kicked off. It’s big. It’s strategic. A career maker. Your task? To design and implement a new strategic messaging platform to replace the existing legacy system. This constitutes a myriad of SQL scripts, staging tables, tactical … Continue reading
Posted in Business Rules, Data Mapping, Domain Model, Trade Flow
Tagged agile, As Is, break, domain boundary, edge case, Messaging Systems, Post-Trade, sequencing, sql script, test driven, To Be, use case
Comments Off on Don’t dis the “As Is”!