AdonisJS being a complete Web Framework offers a lot of tooling around handling HTTP requests. When coming from a different framework, you may already be familiar with certain terminologies. If not, understanding every part of the framework might take a while, but that's ok.

In this guide, you will get a birds eye view of handling HTTP requests and how different pieces of the framework works together.


Routes are the starting point for your application. Using Routes, you define the URLs for your website and hence without registering any routes, your application is not accessible to the outside world.

You can register routes using the Router module of AdonisJS as shown in the following example:

Routes are registered inside start/routes.ts file

import Route from '@ioc:Adonis/Core/Route'

Route.get('/', async () => {
  return 'Home page'

Route.get('/about', async () => {
  return 'About page'

The output of the handler function is sent back as response. You can send HTML, JSON, XML and many other data types from the route handler and AdonisJS will handle them properly.

Rendering views

import Route from '@ioc:Adonis/Core/Route'

Route.get('/', async ({ view }) => {
  return view.render('home')})

    <h1> Home page </h1>

JSON Response

You can send JSON response by simply returning a JavaScript object from the route handler.

import Route from '@ioc:Adonis/Core/Route'

Route.get('/', async () => {
  return {
    id: 1,
    username: 'virk',
    email: '[email protected]',

Learn more about routes


AdonisJS follows the MVC (Model-View-Controller) architecture. The job of Controllers is to handle and fulfill the HTTP requests by working with the other parts of the application. For example: Using the database model to load the data and then passing it to the view for rendering the HTML.

import Route from '@ioc:Adonis/Core/Route'

Route.get('posts', 'PostsController.index')
import Post from 'App/Models/Post'

export default class PostsController {

  public async index ({ view }) {
    const posts = await Post.all()
    return view.render('posts', { posts })

@each(post in posts)
  <h2> {{ post.title }} </h2>
  <p> {{ post.body }} </p>

Learn more about controllers


The views layer of AdonisJS is powered by Edge template engine. Think of it as HTML with the ability to write logic and render dynamic data. For example:

  @set('users', [
    { username: 'virk' },
    { username: 'tobi' },
    { username: 'romain' }

    @each(user in users)
      <li>{{ user.username }}</li>

All that fancy syntax @set, @each are part of the Edge templating syntax. Make sure to read the views documentation for better understanding.


Models represents the database layer of your application. AdonisJS has inbuilt support for data models built on top of Active Record pattern. You can describe your database tables as JavaScript classes and use JavaScript methods for reading, writing and deleting rows. For example:

Declaring a Model
import { BaseModel, column } from '@ioc:Adonis/Lucid/Orm'

class User extends BaseModel {
  @column({ isPrimary: true })
  public id: number

  public username: string

  public email: string
Using Models
import User from 'App/Models/User'

await User.all() // fetch all
await User.find(1) // find where id = 1

await User.query().where('age', '>', 18) // find where age > 18

// Creating new user
const user = new User()
user.username = 'virk' = '[email protected]'


Along with Models, AdonisJS also gives you robust API for database migrations, seeders and ability to construct and execute queries using the Database query builder.


Middleware is an established terminology used by many frameworks across multiple programming languages. Some frameworks might also call them Pipelines.

In AdonisJS, the middleware are executed before the request reaches the route handler. Middleware can perform various tasks of different nature. For example:

  • Perform authentication and abort request when the user is not logged in.
  • Preload data using Models.
  • Perform usage monitoring by tracking every HTTP request.
import { HttpContextContract } from '@ioc:Adonis/Core/HttpContext'

export class AuthMiddleware {
  public async handle ({ session, response }: HttpContextContract, next) {
    if (!session.userId) {
      return response.status(401).send('Unauthorized')

    await next()

Learn more about middleware.

Http Context

AdonisJS creates a unique context object for every HTTP request it receives. The Context (aka ctx) is then passed to every middleware and finally to the route handler.

The purpose of the context is to hold the information related to the current request. For example:

  • The current request url, body, headers, cookies and so on.
  • Currently logged in user.
  • Session module to store and read session values.
  • Template engine object to render views in context of current request, and much more.

You also can attach additional properties to the context. For example: A multitenant application can preload tenant details inside a middleware and then pass it around using the request context.

Reference to Context

Following is an abstract example of accessing the context inside the route handler.

Route.get('/', async (ctx) => {


In this guide you briefly learned about the concepts and terms used by AdonisJS. The entire framework revolves around the same concepts and hence being familiar with them is very important.

In the upcoming guides, you will learn about the same terms and concepts in more depth along with their practical use cases.