O slideshow foi denunciado.
Utilizamos seu perfil e dados de atividades no LinkedIn para personalizar e exibir anúncios mais relevantes. Altere suas preferências de anúncios quando desejar.
Billing & Payments Meetup II
March 18th, 2015
Billing & Payments Meetup II
• Mathieu Chauvin
Payment Processing in the Cloud
• Sangeeta Handa & John Brandy
Billing Work...
Payment Processing in the
Cloud
Mathieu Chauvin
Payments Engineering
(src: Nintendo)
• > 57M members
• ~ 50 countries
• 12 currencies
• 9 payment types
• 15+ payment processors
& verification services
• 2M t...
Payments Application
• Method Of Payment (MOP)
– Secure storage
– Management
• Connection to 3rd party
– Payment processor...
Historical Payments Application
• Data center
• Difficulties integrating
new payment types
• Sedimentary layers of
legacy ...
Historical Payments Application
Cloud
Proxy
Client Apps
from DC
Payments
App
Payments
ORA DB
tunnel
File/Batch
Apps
File/B...
Netflix ♥ Cloud
• 1997: Netflix founded
• 2007: Streaming
• 2010: Microservices -
AWS adopted
• 2013: Ready for payments
(...
Payments in the Cloud!
• Compliance
– AWS PCI compliance level 1
– Cassandra PCI compliant
• Division of labor
– Token ser...
Cassandra
• Tunable consistency
• Multi-region support
• CAP theorem
– Consistency above all
– Local quorum reads & writes...
Technologies & Framework
• Enterprise integration pattern framework
– Apache Camel
• Batch application
– Spring Batch
• Da...
New Architecture Design
Cloud
Payments
App
Tokenizer
Client Apps
from AWS
3rd Party
Processors
3rd Party
Processors
3rd Pa...
region B
load balancers
region A
Multi-Region Availability
zone a zone b zone c zone a zone b zone c
load balancers
How Do We Go There?
• Decoupling
• Shadow write (roman riding)
• Staggered migration by country
(src: Nintendo)
Decoupling
Cloud
Proxy
Client Apps
from DC
Payment
App
Payment
ORA DB
tunnel
Client Apps
from AWS
Cloud
Payment
App
Tokeni...
Shadow Write
Cloud
Proxy
Client Apps
from DC
Payment
App
Payment
ORA DB
tunnel
Client Apps
from AWS
Cloud
Payment
App
Toke...
Staggered Migration
• Migration by country
• Sole requirement: All processors for the
country have to be cloud-ready
Risks
• Troubleshooting
• Depth of existing business logic
– by country,
– by processors,
– by use cases
• Cloud compatibi...
Questions ?
(src: Nintendo)
Próximos SlideShares
Carregando em…5
×

3/18/15 Billing&Payments Eng Meetup II - Payments Processing in the Cloud

77.247 visualizações

Publicada em

http://www.meetup.com/Netflix-Billing-Payments-Engineering/events/220552423/

  • Hey guys! Who wants to chat with me? More photos with me here 👉 http://www.bit.ly/katekoxx
       Responder 
    Tem certeza que deseja  Sim  Não
    Insira sua mensagem aqui

3/18/15 Billing&Payments Eng Meetup II - Payments Processing in the Cloud

  1. 1. Billing & Payments Meetup II March 18th, 2015
  2. 2. Billing & Payments Meetup II • Mathieu Chauvin Payment Processing in the Cloud • Sangeeta Handa & John Brandy Billing Workflows in the Cloud • Shankar Vedaraman Payment Analytics at Netflix • Poorna Udupi & Rudra Peram Security for Billing & Payments • Rahul Dani Escape from PCI Land
  3. 3. Payment Processing in the Cloud Mathieu Chauvin Payments Engineering (src: Nintendo)
  4. 4. • > 57M members • ~ 50 countries • 12 currencies • 9 payment types • 15+ payment processors & verification services • 2M transactions per day • … and counting!
  5. 5. Payments Application • Method Of Payment (MOP) – Secure storage – Management • Connection to 3rd party – Payment processors – Verification services • A lot of batch processing • Agnostic interface to clients
  6. 6. Historical Payments Application • Data center • Difficulties integrating new payment types • Sedimentary layers of legacy code
  7. 7. Historical Payments Application Cloud Proxy Client Apps from DC Payments App Payments ORA DB tunnel File/Batch Apps File/Batch Apps File/Batch Apps 3rd Party Processors 3rd Party Processors 3rd Party Processors 3rd Party Processors Client Apps from AWS
  8. 8. Netflix ♥ Cloud • 1997: Netflix founded • 2007: Streaming • 2010: Microservices - AWS adopted • 2013: Ready for payments (http://techblog.netflix.com/2010/12/four-reasons-we-choose-amazons-cloud-as.html)
  9. 9. Payments in the Cloud! • Compliance – AWS PCI compliance level 1 – Cassandra PCI compliant • Division of labor – Token service – Secure key storage w/ cloudHSM • Technical evaluation – NoSQL vs. RDBMS
  10. 10. Cassandra • Tunable consistency • Multi-region support • CAP theorem – Consistency above all – Local quorum reads & writes • Data model – Rethink and denormalize
  11. 11. Technologies & Framework • Enterprise integration pattern framework – Apache Camel • Batch application – Spring Batch • Data migration – Apache Storm • Netflix OSS • AWS
  12. 12. New Architecture Design Cloud Payments App Tokenizer Client Apps from AWS 3rd Party Processors 3rd Party Processors 3rd Party Processors 3rd Party Processors
  13. 13. region B load balancers region A Multi-Region Availability zone a zone b zone c zone a zone b zone c load balancers
  14. 14. How Do We Go There? • Decoupling • Shadow write (roman riding) • Staggered migration by country (src: Nintendo)
  15. 15. Decoupling Cloud Proxy Client Apps from DC Payment App Payment ORA DB tunnel Client Apps from AWS Cloud Payment App Tokenizer + Country Code + Country Code + Routing Logic + Routing Logic
  16. 16. Shadow Write Cloud Proxy Client Apps from DC Payment App Payment ORA DB tunnel Client Apps from AWS Cloud Payment App Tokenizer
  17. 17. Staggered Migration • Migration by country • Sole requirement: All processors for the country have to be cloud-ready
  18. 18. Risks • Troubleshooting • Depth of existing business logic – by country, – by processors, – by use cases • Cloud compatibility of processors (src: Nintendo)
  19. 19. Questions ? (src: Nintendo)

×