Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat: [DB] RDB와 트랜잭션 #29

Open
wants to merge 3 commits into
base: main
Choose a base branch
from
Open

feat: [DB] RDB와 트랜잭션 #29

wants to merge 3 commits into from

Conversation

junseoplee
Copy link
Collaborator

@junseoplee junseoplee commented Jan 5, 2025

개요

  • RDB와 NoSQL의 차이에 대해 설명해 주세요.
  • 트랜잭션이 무엇이고, ACID 원칙에 대해 설명해 주세요.
  • 트랜잭션 격리 레벨에 대해 설명해 주세요.

체크리스트

  • PR 제목을 Commit Convention에 맞게 작성
  • Label 추가
  • 리뷰어 팀 등록했나요?
  • Assignee 등록했나요?

@junseoplee junseoplee added the DB label Jan 5, 2025
@junseoplee junseoplee requested a review from a team January 5, 2025 14:37
@junseoplee junseoplee self-assigned this Jan 5, 2025
@junseoplee junseoplee requested review from eunsoA, kimjunha1231 and cywin1018 and removed request for a team January 5, 2025 14:37
Comment on lines +37 to +41
### 읽기 작업에도 트랜잭션을 걸어야 할까요?

- 일관된 스냅샷을 보장해야 하는 경우 - 데이터의 정확성
- 읽기 후 쓰기 작업이 연결된 경우
- 다중 읽기 작업이 일관성을 유지해야 하는 경우
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

흥미롭군요

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

디비를 공부하면 RDB랑 NoSQL 중에 무엇을 골라서 프로젝트에 참여해야하는지 고민되는 일이 많았는데, 혹시 고르는 기준 같은게 있을까요?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants