Let's say I have Clients and Tests tables. A client will register for many tests. And keep registering for the same test again. So I create a client_test table. The normal procedure I use is creating a model called ClientTest and also a controller for model as ClientTestController. Also a route named clienttest to implement the crud functionalities for the table.
Is it the best practice or is there any better way to handle it?