The document discusses the use of Go programming language in the travel industry, specifically within Ryanair's payment system, highlighting reasons for its adoption such as speed, efficient memory management, and reduced dependencies. It provides insights into inter-process communication, parallelism, and compliance with PCI standards for sensitive data handling. The speaker also emphasizes the operational improvements and cost savings achieved through the implementation of Go.

1. Go-ing Places
Go in the travel industry

2. Introduction
Paul Mooney
Host, insidethecpu.com
Architect, Ryanair Labs
Programming with Go for 1 year

3. Schedule
Why
Where
How

4. Disclaimer
I’m not a recruiter

5. Why
Reasons we chose Go

6. Speed
Inter-process communication
Dependency analysis
Reduced dependency on C
Efficient mark-and-sweep garbage collection

7. Beauty
Promotes idiomatic code
Structure and documentation are part-and-parcel
Parallelism is eas[y](ier)
Superb data-transfer and memory management

8. Price
Linux VMs are cheaper than Windows
33% approx. saving per VM

9. Goroutines vs. threads
Smaller memory footprint
Disconnected from OS threading mechanism
More scalable stack
Encapsulated preemption, synchronisation

10. Where
Where we run Go

11. Payment system
50K+ daily transactions
Multiple facets of execution
Encapsulated complexity

12. Payment card validation
BIN-range lookup
Luhn check
Sensitive data-retrieval
External security
Internal security
Fraud-detection
Dynamic currency-conversion (DCC)

13. Sensitive data retrieval

14. Making a payment

15. PCI compliance

16. How
How Go works

17. Static types
Variables retain specified type
Problems identified at compile-time

18. Memory management
Variables live on the stack or heap
Generally favour the local call stack
Heap reserved for long-life or large objects

19. –You
“Just show me the damn code!”

20. Final thoughts
Backbone of Ryanair finance
Reduced cost
Increased speed of operation
Standardised developement

21. Shameless plug
Source code
https://github.com/daishisystems/fallback
https://github.com/daishisystems/month
ie.linkedin.com/in/daishisystems
@daishisystems