PAY API CLIENT

In the project X resiliency track, we want to protect QBO's remote calls using Hystrix with minimum effort for client to integrate while we can control Hystrix naming conversion across Intuit!

DRY ProblEM

1. Any clients who want to call Pay Api, they have to write THE SAME INTEGRATION CODE!
2. If they want to protect the Pay Api calls with Hystrix, they have to write THE SAME HYSTRIX WRAPPING CODE!

DESIGN GOALS

1 - dumB client

2 - MINIMUM DEPENDENCY

3 - Loosely coupled payloads

4 - Convention over configuration

5 - ENFORCED HYSTIRX NAMING

6 - CLI

THANK YOU!