0Pricing
AI Powered SaaS: Stripe + Auth + Billing + Deploy · Aula

Esquema de banco de dados e ORM

Projete um esquema de banco de dados eficiente para as entidades principais do SaaS e integre um mapeador objeto-relacional (ORM) para interagir com os dados.

Esquema de banco de dados e ORM é uma aula grátis de AI Powered SaaS: Stripe + Auth + Billing + Deploy no CoddyKit. Esta é a aula 2 de 4. Você pode ler a aula completa abaixo gratuitamente — depois pratica ao vivo no navegador com um editor de código integrado e um tutor de IA 24/7. Faz parte do caminho de aprendizado de AI Powered SaaS: Stripe + Auth + Billing + Deploy, e seu progresso é sincronizado entre a web e o app CoddyKit. O curso de AI Powered SaaS: Stripe + Auth + Billing + Deploy inclui 4 aulas no total.

Partes desta aula ainda não foram traduzidas e aparecem em inglês.

Database Schema: The Blueprint

Imagine building a house. You wouldn't just start laying bricks, right? You'd need a blueprint!

A database schema is exactly that: a blueprint for your database. It defines the structure of your data, including the tables, columns, data types, and relationships between them.

For a SaaS application, a well-designed schema ensures your data is consistent, easy to manage, and performs efficiently as your user base grows.

Core SaaS Entities

Every SaaS application deals with certain fundamental pieces of information. These are often called entities.

Common entities you'll find in most SaaS apps include:

  • Users: Who uses your service?
  • Products/Plans: What do you offer?
  • Subscriptions: How do users pay for your service?
  • Payments: Records of transactions.

Each entity will become a table in your database.

Designing the User Table

Let's start with the User entity. What information do we need for each user?

A basic users table might look like this:

  • id (Primary Key, unique identifier for each user)
  • email (Unique, for login)
  • password_hash (Securely stored password)
  • created_at (Timestamp when the user registered)
  • updated_at (Timestamp for last profile update)

Each column has a specific data type, like text, number, or date.

Designing Product & Subscription Tables

Next, let's consider products and subscriptions.

Products Table:

  • id (Primary Key)
  • name (e.g., 'Basic Plan', 'Premium Plan')
  • description (Features included)
  • price (Cost of the product/plan)

Subscriptions Table:

  • id (Primary Key)
  • user_id (Foreign Key, links to the users table)
  • product_id (Foreign Key, links to the products table)
  • status (e.g., 'active', 'canceled')
  • start_date, end_date

Foreign Keys are crucial for linking related data across tables.

Introducing the ORM

Interacting with databases directly using SQL can be repetitive and error-prone. This is where an Object-Relational Mapper (ORM) comes in.

An ORM acts as a bridge between your application's object-oriented code (like Java classes) and your relational database tables. It allows you to interact with your database using familiar programming language objects instead of writing raw SQL queries.

Think of it: you work with 'User' objects, and the ORM translates that into database commands.

ORM: Mapping Objects to Tables

With an ORM, each database table often corresponds to a model or entity class in your code. Each row in the table becomes an instance of that class.

For example, your users table would map to a User class in your programming language.

The ORM handles the complex details of mapping class properties (like email) to database columns (like email).

ORM in Action: Data Manipulation

Instead of writing SQL like INSERT INTO users (email, password_hash) VALUES ('...', '...'), an ORM lets you do this:

public class Main {
  // Represents a User entity/model
  static class User {
    int id; // Maps to 'id' column
    String email; // Maps to 'email' column
    String passwordHash; // Maps to 'password_hash' column

    public User(String email, String passwordHash) {
      this.email = email;
      this.passwordHash = passwordHash;
    }

    // In a real app, ID would be set by DB or ORM upon saving
    public void setId(int id) { this.id = id; }

    @Override
    public String toString() {
      return "User{id=" + id + ", email='" + email + "'}";
    }
  }

  // Mock Repository to simulate ORM interaction
  static class UserRepository {
    private int nextId = 1;

    public User save(User user) {
      // Simulates ORM inserting into DB and setting ID
      user.setId(nextId++);
      System.out.println("Simulating saving user: " + user.email + " with ID " + user.id);
      return user;
    }
  }

  public static void main(String[] args) {
    UserRepository userRepository = new UserRepository();

    // Create a new User object
    User newUser = new User("alice@example.com", "hashedpass123");
    
    // Use the ORM (via repository) to save the user
    userRepository.save(newUser);

    System.out.println("User object after save: " + newUser);
  }
}

ORM in Action: Retrieving Data

Similarly, fetching data becomes working with objects. No more `SELECT * FROM users WHERE id = 1;`

public class Main {
  static class User {
    int id;
    String email;
    String passwordHash;

    public User(int id, String email, String passwordHash) {
      this.id = id;
      this.email = email;
      this.passwordHash = passwordHash;
    }

    @Override
    public String toString() {
      return "User{id=" + id + ", email='" + email + "'}";
    }
  }

  static class UserRepository {
    // Mock data storage for demonstration
    private java.util.Map<Integer, User> users = new java.util.HashMap<>();

    public UserRepository() {
      users.put(1, new User(1, "bob@example.com", "hashed_bob"));
      users.put(2, new User(2, "charlie@example.com", "hashed_charlie"));
    }

    public User findById(int id) {
      System.out.println("Simulating finding user with ID: " + id);
      return users.get(id);
    }
  }

  public static void main(String[] args) {
    UserRepository userRepository = new UserRepository();

    // Use the ORM to find a user by ID
    User foundUser = userRepository.findById(1);

    if (foundUser != null) {
      System.out.println("Found user: " + foundUser);
    } else {
      System.out.println("User not found.");
    }

    User anotherUser = userRepository.findById(99);
    if (anotherUser == null) {
        System.out.println("User with ID 99 not found (as expected).");
    }
  }
}

Benefits of Using an ORM

ORMs offer several advantages for SaaS development:

  • Reduced SQL Code: You write less boilerplate SQL, focusing on business logic.
  • Type Safety: Work with objects in your programming language, leveraging its type system to prevent common errors.
  • Database Portability: Many ORMs allow you to switch databases (e.g., from PostgreSQL to MySQL) with minimal code changes.
  • Improved Productivity: Faster development cycles due to abstraction.

Popular ORMs include Hibernate (Java), SQLAlchemy (Python), and Entity Framework (.NET).

Schema & ORM Check

Consider a simple SaaS application that allows users to create tasks. Each task belongs to a user.

Which of the following statements is TRUE regarding the database schema and ORM interaction for this scenario?

Recap: Schema & ORM

In this lesson, we explored the critical role of a database schema as the blueprint for your SaaS data, defining tables, columns, and relationships.

We designed basic schemas for core entities like User, Product, and Subscription, highlighting the importance of primary and foreign keys.

Finally, we introduced Object-Relational Mappers (ORMs) as powerful tools that simplify database interactions by allowing you to work with objects instead of raw SQL, boosting productivity and code maintainability.

Perguntas Frequentes

A aula “Esquema de banco de dados e ORM” é grátis?

Sim — o texto completo de “Esquema de banco de dados e ORM” é grátis para ler aqui na web. Para praticá-la interativamente (um editor de código integrado e um tutor de IA 24/7) e desbloquear o restante do curso de AI Powered SaaS: Stripe + Auth + Billing + Deploy, atualize para CoddyKit PRO. O curso de AI Powered SaaS: Stripe + Auth + Billing + Deploy inclui 4 aulas no total.

O que vou aprender em “Esquema de banco de dados e ORM”?

Projete um esquema de banco de dados eficiente para as entidades principais do SaaS e integre um mapeador objeto-relacional (ORM) para interagir com os dados. Você pratica AI Powered SaaS: Stripe + Auth + Billing + Deploy com código prático que executa diretamente no navegador, e um tutor de IA 24/7 responde suas dúvidas enquanto trabalha na aula.

Preciso ter experiência prévia para começar AI Powered SaaS: Stripe + Auth + Billing + Deploy?

Nenhuma experiência prévia é necessária. AI Powered SaaS: Stripe + Auth + Billing + Deploy no CoddyKit é estruturado para alunos iniciantes até avançados, então você pode começar aqui ou desde o início e aprender no seu ritmo. Esta é a aula 2 de 4.

Quanto tempo leva a aula “Esquema de banco de dados e ORM”?

A maioria das aulas CoddyKit leva cerca de 5–10 minutos. Cada uma é compacta e interativa, então você faz progresso constante e retoma exatamente de onde parou entre web e app.

Posso escrever e executar código nesta aula de AI Powered SaaS: Stripe + Auth + Billing + Deploy?

Sim. Cada aula de AI Powered SaaS: Stripe + Auth + Billing + Deploy inclui um editor de código integrado, então você escreve e executa código real direto no navegador e recebe feedback de IA instantaneamente — nenhuma configuração local necessária.

Todas as aulas deste curso

  1. Princípios de design de APIs RESTful
  2. Esquema de banco de dados e ORM
  3. Primeiros endpoints de API
  4. Paginação, Filtragem e Ordenação de APIs
← Voltar para AI Powered SaaS: Stripe + Auth + Billing + Deploy