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.

Sign up for GitHub

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

Jump to bottom

[refactor] Divide service logic into business and DAO #133

Open

2 tasks

geeneve opened this issue Mar 23, 2022 · 1 comment

Open

2 tasks

[refactor] Divide service logic into business and DAO #133

geeneve opened this issue Mar 23, 2022 · 1 comment

Assignees

Labels

3️⃣ priority: low 🌈 refactor

Milestone

Member

geeneve commented Mar 23, 2022

🧐 Refactoring Target

현재 Service 레이어가 비즈니스 로직과 DB처리 로직에 대한 코드를 같이 담고 있는데, 이 둘을 분리할 생각입니다.
데이터에 엑세스하는 계층을 따로 정의함으로서 재사용성을 높일 수 있습니다.

📝 To Do

DAO 만들기
서비스 로직에서 DB에 접근하는 부분을 DAO를 사용하는 것으로 변경하기

✅ Issue check list

Assignees, Labels 확인하기
Milestone 연결 확인하기

geeneve added 🌈 refactor 3️⃣ priority: low labels

Member

holmir97 commented Mar 24, 2022

DAO를 사용하여 중복되는 DB접근 쿼리문의 사용을 최소화할 수 있을것 같습니다

holmir97 added this to the v3.0.0 milestone

seohyun-106 assigned geeneve

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment