[사전 미션 - CSR을 SSR로 재구성하기] - 초코(강다빈) 미션 제출합니다.#26
Open
00kang wants to merge 5 commits into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
🤔 생각해 보기
1. CSR과 SSR에서 초기 페이지 로딩 시간에 어떤 차이가 있었을까? 그 이유는?
SSR (Server-Side Rendering):
서버에서 모든 데이터와 콘텐츠가 준비되어 있어 클라이언트 측에서 추가적인 데이터 요청이 필요 없기 때문에 페이지가 더 빨리 렌더링됨
CSR (Client-Side Rendering):
CSR 방식은 클라이언트에서 모든 UI 구성 요소를 동적으로 생성하므로, JavaScript와 데이터 요청이 완료되어야 페이지가 완전히 렌더링됨. 따라서 더 오래 걸림.
csr.mp4
ssr.mp4
2. 서버 측에서 데이터를 가져오는 방식과 클라이언트 측에서 데이터를 가져오는 방식을 비교해서 설명한다면?
SSR (Server-Side Rendering)
CSR (Client-Side Rendering)