Some of the deeper aspects of programming for the mobile first world

1. 'Deeper Programming' for
the Mobile First World
Sriram V Iyer
Head - Innovation Labs @ Myntra
Twitter: @sviyer

2. Agenda
Introduction - What do I mean by ‘Deeper
Programming’?
Understand ‘Wireless’ in Mobile Tech
Reactive / Async is the way to go
Not just mobile - Devices / IoT
Backend Challenges
Newer Architectures

3. Deeper
Programming
On the top-level everything changes.
But fundamentals remain (more or
less) same - Remember COBOL was
super hot once!
Key to great work is to go ‘Deep’
How to know if you are deep? (Clue:
StackOverflow)

5. Depth - To see
ऋिषः

7. Know Wireless

8. Wired != Wireless
Most software developed still
developed for the wired world
(unfortunately)
[How many of you still use sockets?]
TCP Windows / ARQ
Fast TCP / ZeroMQ (etc.)

9. TCP Over Wireless
BER / PER in Wireless >> Wired
(non-existent)
Packet Loss == Congestion (In
Wired)
ARQ Window Management

11. Facebook: Performance and network segmentation on Android
(Connection and Year Class)

12. Async / Reactive

13. What is Async /
Reactive
I/O Needs to be done differently
I/O Latencies: (Representative)
L1 - 3 Cycles
L2 - 14 Cycles
RAM - 250 Cycles
Disk - 41 * 10 ^ 6 cycles
Network - 240 x 10 ^ 6 cycles

15. Apache vs nginx

17. Not ‘just’ Mobile
Phones

19. Programming for IoT !=
Programming for Mobile
May not have ‘always on’ internet access
Identity / Provisioning / Life Cycle
Management
Multi-hop
Network always not available
Backend implications? (Points to Ponder)

20. New Architectures

21. Newer Architectures
Split Architectures - Edge Computing
Function as Service / Serverless
GPU / FPGA (?)

22. Thank you!