There a wealth of server frameworks out there and it can be hard to make a decision on what framework to use. When opting for Swift as a server side programming languages there's a wealth of possibilities. However, two standout: Vapor and Hummingbird. Making a decision can be difficult, especially if one isn't aware of the tradeoffs picking one over the other entails. This talk aim is twofold: firstly, to compare and contrast both server-side frameworks. Secondly, to draw on their strengths and weaknesses to identify what use cases fit best with one or the other, giving attendees a way to evaluate their options, consider the different tradeoffs and ultimately make a better, more informed decision.

I'll start by rapidly introducing the benefits of writing Swift on the Server, the different options that are available to developers, some dead projects before narrowing down to the two Giants, Vapor and Hummingbird.

The first part of the talk will compare and contrast both frameworks. I'll run through the basic features of modern HTTP servers (routing, persistence, CORS, …) and compare how Vapor and Hummingbird have implemented them, specifically focusing on the Developer Experience.

The second part of the talk will be more opinionated and focus heavily on the advantages of picking one over the other. What are you sacrificing when picking Hummingbird over Vapor? What about the other way around? The second part of this talk should leave you with a sense of how to make those decisions and what framework to use when making decisions.

Ultimately my goal is for you to walk away from this talk being able to answer these two questions:

• What are the main differences between Vapor and Hummingbird? What are their similarities?
• What are the main tradeoffs when picking one over the other?