The Mainframe Origin Story • Howard Alken created the first Mainframe at IBM, called the Harvard Mark I in 1944
4
Scale Today
5
Who is still using mainframes Communications
6
How we want to mainframe merges to work
7
How they actually work
8
Technical Challenges
9
6 months in
10
Failed attempts at replacing mainframes
11
My Mainframe Scale Leamings
12
Mainframe Adjacent Systems
13
Gopher phase
14
Experience across an organization
15
Language Background
16
Story: Grace Hopper
17
MVT Objectives
18
Interfaces
19
Typing
20
Library Development
21
Why manually test? Case Study: Systematics
22
Testing Best Practices
23
The Poor (wo)man's Code Review
24
Banking Systems
25
Upsetting Concurrency Findings Where we need it: • Saving into databases (sometimes) • Making parallel calls to dependencies Where don't we need it! . Most of our systems
26
Total Volume
27
IBM Open Enterprise SDK for Go is now available!
Description:
Explore the journey of implementing Go at mainframe scale in this GopherCon 2021 talk by Kaylyn Gibilterra. Discover how Capital One created a distributed system in Go to process account data from modern cores and legacy mainframes, handling peak traffic of 2 million tps and 5Gbps while storing over 20TB across multiple AWS regions. Learn about the challenges and successes of transitioning to Go services, including library creation, scaling issues, and team ramp-up. Gain insights into mainframe history, communication challenges, and technical hurdles faced during the implementation. Understand the importance of interfaces, typing, and library development in Go. Explore testing best practices, concurrency findings, and the availability of IBM Open Enterprise SDK for Go. Get a practical guide on how any company can transition to writing Go services from any language, leveraging Go's simplicity and scalability to achieve linear team growth and exponential service scaling.