The Why, Where, and How we leverage Go at Ryanair Labs.

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. But first, why not
Not another language!
Not pervasive enough
Low-yield talent pool

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

8. Beauty
Promotes idiomatic code
Structure and documentation are part-and-parcel
Parallelism is eas[y](ier)
Communicating Sequential Processes (CSP)

9. Parallelism
Communicating
sequential processes
Multithreading is hard
Often not worth the
overhead

10. Parallelism
High-level concurrency
support
Goroutines
Channels

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

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

13. Where
Where we run Go

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

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

16. Sensitive data retrieval

17. Making a payment

18. PCI compliance

19. How
How Go works

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

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

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

23. What exactly is Go
Functional
Object Oriented

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

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

26. That’s it…