Your search page lists all the books that match the criteria and the links on that page are meant to take you to the info for an individual book, right? You need a way to identify a book, like the ISBN. Put that data in the URL, so the paths in the URL look like /book/978-0321503626 or /book/978-0134757599. So your handler for /book needs to take the ISBN from the path and put it in the query to look up the data for that book. You already know how to do queries, so there shouldn't be a problem there. I don't know why you think you need JSON either; that's just overcomplicating things.
You must have at least seen variable routes before - if you've ever used Twitter, their URLs are like https://twitter.com/BobSmith or https://twitter.com/AliceJones. I'm sure you can think of other examples, but in any case, the point is, of course this is possible.
You must have at least seen variable routes before - if you've ever used Twitter, their URLs are like https://twitter.com/BobSmith or https://twitter.com/AliceJones. I'm sure you can think of other examples, but in any case, the point is, of course this is possible.