Question 1

How do I add a new API route in Deno REST?

Accepted Answer

Follow the Model-Controller-Service pattern by creating new files in each directory, then register the route in the main app file using Oak routing. The README outlines the structure but doesn't provide step-by-step examples for custom routes.

Question 2

Deno REST vs Express.js boilerplate – which is better for a new project?

Accepted Answer

Choose Deno REST for modern, secure APIs with Deno's built-in TypeScript and security features, but opt for Express.js if you need a larger ecosystem and more community support. Deno REST is ideal for teams embracing Deno's advantages over Node.js.

Question 3

Can I use Deno REST with a SQL database instead of MongoDB?

Accepted Answer

Not directly; the boilerplate is designed for MongoDB with deno_mongo. To use SQL, you'd need to replace the database driver and refactor the data layer, which can be complex and time-consuming.

Question 4

How to deploy Deno REST to a serverless platform like Deno Deploy?

Accepted Answer

It's possible but requires adjustments, as the boilerplate includes Docker and traditional server setup. You might need to modify the entry points and remove container-specific dependencies for optimal serverless deployment.

Question 5

Does Deno REST support GraphQL or just REST?

Accepted Answer

It's focused solely on RESTful APIs; adding GraphQL would require integrating a GraphQL server library and restructuring the API layer, which isn't covered in the boilerplate features.

Question 6

How to handle file uploads in Deno REST?

Accepted Answer

The boilerplate doesn't include file upload handling; you'd need to add middleware like Oak's multipart support or a third-party library, as it's not a built-in feature mentioned in the README.

Deno Rest

What is Deno Rest?

Overview

Use Cases

Best For

Related Projects

Found a gem we're missing?

Not Ideal For

Pros & Cons

Pros

Cons

Frequently Asked Questions