The trainer won’t be able to answer your question. It’s depend on
For pure swift and you prefer Fluent like Laravel Fluent with supported databases without touching low-level C.
Low learning curved for web developers who simple wants to serve contents similar to Blogs like WordPress or eCommerce. It has easy to use permission control.
Performance should be better once Swift 4 or 5 release with support on those Rust, Go, other models.
Note: Vapor behind Nginx will be slower.
Choose Vapor if you don’t mind to contribute Vapor code frequently to iron out bugs, see their #release in Slack channel.
It’s toward an MVC web framework just like Laravel.
Support some existing C libraries to reuse existing code, just like Scala and Kotlin reuse Java libraries. You get to leverage your Perfect website with Enterprise-class e.g. Kafka, etc as Perfect team adopting them. You have the best of both world and you will only need to write in Swift code.
Performance in Perfect is excellence and use battle-tested HTTP.
Fairly learning curved for a start, as long as the community helps you with some tips and do a bit of research, you’ll gains lot of ideas to build any applications that demand performance.
What if we do not need Nginx or Apache for reverse proxy in Perfect? It’s possible with a bit of workaround to maximize performance.
Choose Perfect: If you prefer stability and less disruption to your and clients’ projects.
In my experience, you could build it like MeteorJS in some way, it’s more than MVC web framework and you could choose your folder structures.
Kitura is useful for first-class support in IBM cloud services that aims to be performent and less memory usages than Java.
To the end of comparison, use both. One for purely serving on Internet and that what makes Vapor as popular as PHP community. One for working on the backends if you can’t afford downtime or need to work with commercial application.
Important, if you prefer to write HTTP level, you could choose either Vapor or Perfect HTTP module and write in your own way with a little more verbose code to gain better performance for specific tasks. Both could built like WordPress. It’s your chance to try both out for a few months and decide which is you prefer.
Remember to monitor memory and CPU usage on both frameworks.