-
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
Tag Archives: sequencing
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”!