Derby renders it's client-side views on the server. This means that there's no "delay" in serving the content to the browser when the user requests it. It's also very helpful for SEO purposes.
Derby seems to have a small community of followers, at least compared to other Node full-stack frameworks. So it could be difficult for a beginner to find examples or help if they get stuck somewhere in their development.