Daniel Jilg

Description

Because Swift on the Server is not as well-known as, say, Node or Django, sometimes it's hard to find examples of what problems developers encounter once they scale beyond a certain point. There are hidden traps of technical debt that people will fall into, and there are surprising shortcuts if you know they're there. Sometimes it's just hard to choose a solution without any real-world examples.

I built a reasonably successful Software-as-a-Service startup entirely based on Swift, and I want to lay all my cards on the table: what services and SDKs are we using, how our project structure, architecture and testing looks like, how we solved technical and security problems, and of course what songs I sing to myself while SwiftNIO compiles for the 38th time today. There may also be sprinkles on how to use analytics properly and ethically, and I might just find one or two edge cases where Swift is not the right answer.