DEV Community

with-heart
with-heart

Posted on • Edited on

High level technical overview

To build discord-server-info, we'll need a few separate pieces:

  • bot
  • db
  • app

A diagram showing the bot, db, and app pieces and how they relate to each other

bot will be a Discord bot. This bot reads data from the servers it's connected to and stores it in our database (db).

db is a Prisma database that provides an API for storing and accessing server data.

app is a Next.js application that allows users to authenticate with Discord and explore data from their servers.

If you're wondering why we need this structure rather than having the app read data directly from the Discord API, it's because the Discord API intentionally provides access to very little data. A bot account is required for full access.

The discord-server-info repo will eventually be a monorepo with a package for each piece.

Sentry image

Hands-on debugging session: instrument, monitor, and fix

Join Lazar for a hands-on session where you’ll build it, break it, debug it, and fix it. You’ll set up Sentry, track errors, use Session Replay and Tracing, and leverage some good ol’ AI to find and fix issues fast.

RSVP here →

Top comments (0)

Heroku

Build apps, not infrastructure.

Dealing with servers, hardware, and infrastructure can take up your valuable time. Discover the benefits of Heroku, the PaaS of choice for developers since 2007.

Visit Site

👋 Kindness is contagious

Please leave a ❤️ or a friendly comment on this post if you found it helpful!

Okay