Upgrade to Pro — share decks privately, control downloads, hide ads and more …

From iOS- to Vapor Developer (Øredev)

9993186221ec65f6f10db0dc9cff7c07?s=47 Steffen D. Sommer
November 09, 2017
Programming
0
720

From iOS- to Vapor Developer (Øredev)

Diving into server-side Swift can seem straightforward at first if one knows the programming language, but it might be harder than you think since it involves developing on a new platform. I will walk you through my journey coming from iOS into Vapor, what challenges I faced, and which strengths I had coming from the iOS platform. I will talk about how these challenges can be overcome and I will share my experiences after working with Vapor in production for 6 months.

Talk given at Øredev 2017 on the 9th of November 2017.

9993186221ec65f6f10db0dc9cff7c07?s=128

Steffen D. Sommer

November 09, 2017
Tweet

More Decks by Steffen D. Sommer

See All by Steffen D. Sommer
9993186221ec65f6f10db0dc9cff7c07?s=48 steffendsommer
0
130
9993186221ec65f6f10db0dc9cff7c07?s=48 steffendsommer
0
47
9993186221ec65f6f10db0dc9cff7c07?s=48 steffendsommer
0
79
9993186221ec65f6f10db0dc9cff7c07?s=48 steffendsommer
0
130
9993186221ec65f6f10db0dc9cff7c07?s=48 steffendsommer
0
140

Other Decks in Programming

See All in Programming
8ffce1486e39ee3f43f52be5580b9966?s=48 luiznasciment0
1
150
7867fe52a9be4257508a516d4df61578?s=48 tkmnzm
1
300
8284465a94bbdf1ea82cf1a67d55f447?s=48 kilometer
2
340
E83cdc415df47ab3eae30957ae7e2d33?s=48 ykpythemind
0
210
F6baf93a0833a98bdc8184c214f4c468?s=48 rgoswami
1
150
15934fa2aa7b2ce21f091e9b7cffa856?s=48 manfredsteyer
PRO
1
180
706ea99a045bb3f273ab518a3db3e113?s=48 kamiokan
0
230
28410ec97da16f250a154d9b335c8a32?s=48 quannt
1
120
67de06c6cee3ece0f56494e91e48117e?s=48 tkitsunai
6
2.5k
942bb606679caf4c57b38927f83178e1?s=48 qsona
26
6.5k
D76231a2114896dfcc7b79ac69558b79?s=48 yosuke_furukawa
PRO
1
640
E505897a79eede1a676f92740261e8f8?s=48 kubode
2
240

Featured

See All Featured
E4f5d494ebdc9e7cce1aecf3ce3e8bc1?s=48 shpigford
370
42k
96270e4c3e5e9806cf7245475c00b275?s=48 addyosmani
1346
200k
88bc30284c6a424b63a92aad27d0ba36?s=48 jnunemaker
PRO
40
4.7k
64827b31aef81498662e8af4bd6d5157?s=48 jonrohan
1021
390k
Aff5641764408271f7bc398f2097edd0?s=48 denniskardys
219
120k
9952dfcd5d338f8a8e7175c8a8f65fb5?s=48 wjessup
340
16k
A60068bce2e73de3a37ca9d2dbe36092?s=48 bryan
32
3.5k
F29327647a9cff5c69618bae420792ea?s=48 tenderlove
55
3.6k
Ef32e0b1ac5082450dc8c1fca3a26b5c?s=48 cherdarchuk
73
270k
B47b288784fda77a94aeb234ca743c24?s=48 keavy
108
14k
E76911cbe088e5b850d966de3fc7435b?s=48 robhawkes
53
2.9k
Dafc4723e9a1c067796c0fec6f509774?s=48 lemiorhan
629
48k

Transcript

  1. From iOS- to Vapor developer @steffendsommer

  2. None
  3. None
  4. None

  5. Pla$orm support for all Apple pla*orms as well as Linux

  6. None
  7. None

  8. Swi$ on the server

  9. None

  10. !

  11. ♻

  12. !"

  13. None

  14. !"

  15. !

  16. • Swi% • Fast • Code share • More fullstack

    developers • Xcode • Big community • Be part of the development

  17. Swi$ on the server

  18. None

  19. !

  20. None
  21. None

  22. ☁

  23. !

  24. • New language • New package manager • New framework

    • Xcode • Limited hos9ng op9ons • Less libraries compared to other web frameworks

  25. Programming languages in the making

  26. • JavaScript (1995): 22 years • Java (1996): 21 years

    • Ruby (1996): 21 years • Swi$ (2014): 3 years

  27. Web frameworks in the making 1 1 Since their version

    1.0 release.

  28. • Spring MVC (2002): 15 years • Ruby on Rails

    (2004): 13 years • Express (2010): 7 years • Kitura/Perfect/Vapor (2016): 1 year

  29. The future is bright for server-side Swi/

  30. None

  31. Kitura Perfect Vapor

  32. Kitura Perfect Vapor

  33. Kitura Perfect Vapor

  34. None

  35. Hi, my name is Steffen D. Sommer !

  36. Steffen iOS

  37. Steffen ❤ iOS Swi*

  38. Swi$ as a language, not iOS as a pla/orm

  39. None

  40. import Vapor let drop = try Droplet() drop.get("hello") { req

    in return "Hello, world." } try drop.run()
  41. None
  42. None

  43. iOS != Vapor

  44. iOS != Vapor Number of users

  45. ! • 1

  46. • It's all about the requests

  47. iOS != Vapor Performance

  48. ! • Not an issue

  49. • Users do not want to wait for requests to

    return

  50. • Users do not want to wait for requests to

    return • More performance = more money

  51. iOS != Vapor Crash handling

  52. ! • "We'll fix it in the next app update"

  53. • Fix it now

  54. iOS != Vapor Pla$orms

  55. ! • One pla(orm to rule them all

  56. • macOS + Linux

  57. iOS != Vapor Foundation

  58. ! • !

  59. • !

  60. iOS != Vapor The Xcode project file

  61. ! • Merge madness

  62. • .. what file?

  63. iOS != Vapor Third party frameworks

  64. ! • Which one to pick?

  65. • Roll out your own

  66. iOS != Vapor User Interfaces

  67. ! • Storyboards and auto layout

  68. • HTML, CSS, JavaScript & template languages

  69. iOS != Vapor Persistence

  70. ! • Used to some extent

  71. • Used heavily

  72. iOS != Vapor Security

  73. ! • Mostly handled by the OS

  74. • Needs to be taken care of

  75. iOS != Vapor Consumers

  76. ! • None

  77. • "Hey backend dev, I can't get this endpoint to

    work.."

  78. iOS != Vapor Releasing

  79. ! • iTunes Connect

  80. • Deploying

  81. Tips to overcome these challenges

  82. Tip #1 RTFM & get involved

  83. Tip #2 Learn about databases

  84. Tip #3 Consider when to use Foundation

  85. Tip #4 Start repor)ng

  86. Tip #5 Setup CI or a VM

  87. Tip #6 Write (API) tests

  88. Tip #7 Document your APIs

  89. Tip #8 Use security packages

  90. Tip #9 U"lize the template language

  91. Tip #10 Use Vapor Cloud

  92. The last 10 months in hindsight

  93. Challenges

  94. • Lots of moving targets (Swi2, Vapor, Vapor Cloud)

  95. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea,ng and maintaining open source packages

  96. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea?ng and maintaining open source packages • Lack of documenta.on

  97. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea?ng and maintaining open source packages • Lack of documenta?on • Outdated resources

  98. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea?ng and maintaining open source packages • Lack of documenta?on • Outdated resources • Few experts

  99. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea?ng and maintaining open source packages • Lack of documenta?on • Outdated resources • Few experts • Lots of boilerplate

  100. • Lots of moving targets (Swi3, Vapor, Vapor Cloud) •

    Overhead in crea?ng and maintaining open source packages • Lack of documenta?on • Outdated resources • Few experts • Lots of boilerplate • Linux quirkiness

  101. How things have improved

  102. • Updates are slowing down (Swi2 and Vapor)

  103. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable

  104. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore

  105. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore • Documenta*on is improving

  106. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore • DocumentaDon is improving • More and more resources

  107. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore • DocumentaDon is improving • More and more resources • Bigger community - more experts

  108. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore • DocumentaDon is improving • More and more resources • Bigger community - more experts • Less boilerplate

  109. • Updates are slowing down (Swi3 and Vapor) • Vapor

    Cloud reached 1.0 and is stable • We don't create as many open source packages anymore • DocumentaDon is improving • More and more resources • Bigger community - more experts • Less boilerplate • Swi$ on Linux is more mature

  110. Our results

  111. • 25+ customer projects

  112. • 25+ customer projects • 30+ open source packages created

  113. • 25+ customer projects • 30+ open source packages •

    Hos$ng fees are going down

  114. • 25+ customer projects • 30+ open source packages •

    Hos7ng fees are going down • More and more of our iOS developers starts to catch up

  115. • 25+ customer projects • 30+ open source packages •

    Hos7ng fees are going down • More and more of our iOS developers starts to catch up • We develop faster

  116. • 25+ customer projects • 30+ open source packages •

    Hos7ng fees are going down • More and more of our iOS developers starts to catch up • We develop faster • Less bugs than before making the switch

  117. No major issues since we made the switch

  118. Resources • Vapor docs: h-ps:/ /docs.vapor.codes/2.0/ • Vapor Slack: h-p:/

    /vapor.team • Vapor @Nodes: h-ps:/ /github.com/nodes-vapor • SwiBConf '17 @gtranchedone: h-ps:/ /www.youtube.com/ watch?v=IuW_hLCsIeQ