| 장 1 | | | | 사무실 |
| | | | ì§Âì›Âì- |
| 소개: - | | | | ì˜Ã-´ ì´ì |
| ôë¼ì´ì-¸ | | | | „ì- ì |
| ÃS¸/서버 | | | | œê³µëÂÂœ ê³¼ì |
| 가장 | | | | -ì„ ì œê³µÃ- |
| 새로운 | | | | 수 있다. |
| ì»´Ã"¨Ã„° | | | | ì´ì˜ |
| 산ì-... ë° | | | | ê²°Ã-©Ã-Âœ |
| 가장 | | | | Ú¨ë ¥ì€ |
| 뜨거운 ì | | | | ì±...ìƒÂì- |
| „ë¬¸ì  ìœ | | | | 사ì-...ê³¼ |
| Ã-‰ì-´ì˜ | | | | 기ìˆ ì Âì¸ |
| Ã-œê°œëS" | | | | ë (TM) Ã-Â¥ |
| ì´다. | | | | 개ì¸ì˜ |
| 성격, 발ì | | | | 개ì¸ |
| „, ë° | | | | Ã-ˆê°€ì´닠|
| anticipateologiesì˜ depist | | | | ¤. PCëS" 개ì¸ |
| 수 | | | | ìƒÂ산ë Â¥ |
| 사용ëÂÂœ | | | | ë° |
| 대로 | | | | ëÂ...립ì„ ì |
| ôë¼ì´ì-¸ | | | | œê³µÃ-œë‹¤, |
| ÃS¸ | | | | 그러나 |
| 서버ì˜ | | | | PCì˜ |
| ì¼반ì Âì¸ | | | | 거대Ã-Âœ |
| ì -ì˜가 | | | | 수ì- ì˜Ã-´ |
| ì-†ë‹¤. | | | | ê³±Ã-Âœ ì´ |
| 그러나 | | | | 개체ëS" |
| ì¼반 | | | | ë˜ÂÃ-Âœ, 무ì |
| ì-„ì´ë""ì-´ëS" | | | | -부를 |
| ôë¼ì´ì-¸ | | | | 창조Ã- 수 |
| ÃS¸ì (TM) € | | | | 있다. |
| 서버가 | | | | ôë¼ì´ì-¸ |
| ì-...무를 | | | | ÃS¸ 서버ëS" |
| 달성Ã-˜ê¸ | | | | ì´ 문ì |
| ° 위Ã-˜ì-¬ | | | | œë¥¼ |
| 네ÃS¸ì›ŒÃ | | | | 결심Ã-˜ëS" |
| ¬Ã¬- | | | | 것ì„ |
| 주ì˜를 | | | | ëÂ-ëS"다. |
| Ã-¨ê»˜ ìž'ë (TM) | | | | (서버 |
| Ã-˜ëS" | | | | Ã"Œëž«Ã¼ì- |
| 분리ë˜ëS" | | | | ì œê³µë˜ëS") |
| ë...¼ë¦¬ | | | | ôë¼ì´ì-¸ |
| ì-"˰Ë°ì´ | | | | ÃS¸ì˜ |
| «Â‹Â¤ ì´다. | | | | 사용 |
| ôë¼ì´ì-¸ | | | | ê³µìœ |
| ÃS¸ 서버ëS" | | | | ìžÂì›Â, ì |
| ì-„주 ìœ Ã-‰ | | | | -당Ã-˜ì§€ |
| ì´다. | | | | ì-Sì€ 개ì¸ |
| ë"±ê³¼ ê° (TM) | | | | ìžÂì›Â; |
| ì€, 다만 | | | | ôë¼ì´ì-¸ |
| 임시ì | | | | ÃS¸ 서버 |
| Âì¸ | | | | 구조ëS" |
| ìÂ¼ì‹œì  ìœ | | | | 모ë" |
| Ã-‰ì¼지ë | | | | 소Ã"„ÃS¸ì›¨ |
| „ 모르다; | | | | ì-´ì (TM) € |
| 그러나 | | | | Ã-˜ë"œì›¨ì-´ |
| 기본 ì | | | | ìžÂì›Âì„ |
| ÂìÂ´ê³ | | | | ê±´ì¶-ê³¼ |
| ê´'ë²"위Ã-Âœ | | | | 관리 Ƶì |
| 무ì-¸ê°€ì | | | | ϓ˜ ë°'ì- |
| 다 ì¼반ì | | | | 있ëS" |
| Âì¸ | | | | 가ëSÂ¥Ã-˜ê²Œ |
| ìS¹ì¸ì´ | | | | Ã-œë‹¤. |
| 있다; | | | | 그것ì€ |
| 예를 | | | | 개ì¸간 |
| ë"¤ë©´, Gartner | | | | 계산Ã-˜ê³ |
| 그룹ì€ | | | | enterprise-wide |
| ì´ 분ì-¼ì- | | | | 계산으ë |
| 있ëS" 주ìš" | | | | Âœ 개ì¸ |
| 산ì-... | | | | 측ì -ì„ |
| 분ì„Â가ì | | | | 변Ø-시Â |
| ¸, ì €ê²ƒì„ | | | | ¨Ã«Â‹Â¤. ì´ |
| 예ì-¸Ã-ˆë‹¤ | | | | ÃS¹ì„±ì€ |
| | | | 사ì-... ê³¼ì |
| "1995ë...„ | | | | -ì˜ 순서, |
| ôë¼ì´ì-¸ | | | | 워ÃÂ¬ê·¸ë£ |
| ÃS¸ | | | | ¹ 단결ë Â¥, |
| 서버까ì | | | | ìƒÂ산ë Â¥ |
| € | | | | ë° |
| ì´ì‹Â시ì | | | | 융Ƶ성ì |
| ¤ 계산ì„ | | | | „ |
| 위Ã-Âœ ë (TM) | | | | 창조Ã-˜ëS" |
| ì˜ì-´." | | | | 것ì„ |
| 처ìÂÂŒ | | | | ëÂ-ëS"다. |
| ôë¼ì´ì-¸ | | | | 개ì¸ |
| ÃS¸/서버 | | | | Ã"Œëž˜ÃS¸à (TM) |
| 성공담ì | | | | ˆì´ |
| ˜ | | | | ôë¼ì´ì-¸ |
| 대부분ì | | | | ÃS¸ 서버ì- |
| € ìœ 산 | | | | 움ì§Â임ì |
| 체계ì- | | | | „ 위Ã-Âœ |
| 있ëS" 처리 | | | | 주ìš" ê²½ì |
| ìžÂ료ì- | | | | ϓ (TM) € 기ìˆ ì |
| ì§Âì ' ì | | | | Âì¸ ì›Âë (TM) |
| ÂìÂ´ê³ 간ì ' | | | | ë |
| ì-¡ì„¸ìS¤ë¥¼ | | | | ¥ì´ëÂ"ë¼ë |
| ì œê³µÃ-˜ëS" | | | | „, 단면ë„ |
| 소규모 | | | | 2ì˜ 시ìž'ì- |
| ì‹ ì²Âì„ | | | | à (TM) -ì¸ëÂÂœ |
| ìÃ-¨Ã-œë‹¤. | | | | 5개ì˜ |
| ê²°ì - ì | | | | 기ìˆ ì Âì¸ |
| œìž'ìžÂì- | | | | 성분ì˜ |
| ë°ì´Ã€ ì | | | | 단지 |
| 'ê·¼ì„, | | | | 첫번째ì |
| ôë¼ì´ì-¸ | | | | ´Ã«Â‹Â¤. |
| ÃS¸/서버 | | | | |
| 공구 밠| | | | 서버 |
| 기ìˆ ì˜ | | | | Ã"Œëž«Ã¼: - |
| 관계ë˜ëS" | | | | |
| ë¯¸ìˆ (TM) ì | | | | 우리ëS" |
| œê³µÃ-˜ëS", | | | | 서버 |
| 사ì-... Ã-„ìš" | | | | Ã"Œëž«Ã¼ì |
| ê´'ì- ë„¤ÃS¸ | | | | 다ìŒ과 |
| 워Ó˜ | | | | ê° (TM) ìÂÂŒ ì |
| 진à (TM) " | | | | -ì˜Ã-œë‹¤: |
| 사용 밠| | | | |
| ôë¼ì´ì-¸ | | | | 소Ã"„ÃS¸ì› |
| ÃS¸/서버 ì | | | | ì-´ê°€ |
| „문 기ìˆ | | | | 그것ì„ ì |
| ì˜ | | | | œê³µÃ-˜ëS" |
| 부족ì€ | | | | ì»´Ã"¨Ã„° |
| ì´ 매ë Â¥ | | | | Ã"Œëž˜ÃS¸à (TM) |
| 그러나 ì | | | | ˆì€ |
| €ìœ„Ã-˜ | | | | 체계ì-Â선|
| ì-ˆë‚´Ã-˜ëS" | | | | œ 사용ì„ |
| Ã-©ìž'ì„ | | | | 위Ã-´ |
| 만ë" 다. | | | | 다른 |
| ì¡°ì§Âì´ | | | | ê³³ì- |
| 성과 | | | | 서비ìS¤Ã-Âœ |
| ì¤'시 ì‹ | | | | «Â‹Â¤. |
| ì²Â으로 | | | | 서비ìS¤ëS" |
| ì´ | | | | 개ì¸ |
| 소규모 | | | | Ã"Œëž˜ÃS¸à (TM) |
| Ã"„ë¡œì | | | | ˆì- ê¶Âê·¹ì |
| ÂÃS¸ì-Â서 Ã- | | | | Â으로 |
| (TM) ìSµ 곡ì„ | | | | 사용ëÂœë |
| ì„ 위로 | | | | ¤; 그러나 |
| ì´ë (TM) Ã-˜ê³ | | | | 서비ìS¤ëS" |
| 기 ë-Œë¬¸ì-Â, | | | | ë˜ÂÃ-Âœ |
| 성과 | | | | 다른 |
| 기대, | | | | 서버 |
| 가ë (TM) | | | | Ã"Œëž«Ã¼ì- |
| 시간 | | | | 사용ì„ ì |
| Ã-„ìš"ì¡°ê±´à | | | | œê³µëœ다. |
| ªÂ³Â¼ 가ë (TM) | | | | 서버 |
| 가ëSÂ¥Ã-˜ê¸°à | | | | Ã"Œëž«Ã¼ì |
| «Â„ Ã-˜ê³ | | | | 개ì¸ |
| 오를 수 | | | | Ã"Œëž˜ÃS¸à (TM) |
| 있 남ì-„ | | | | ˆìœ¼ë¡œ |
| 있ëS" | | | | ìžÂ격ì„ |
| Ã-„ìš"ì-Â서 | | | | 주지 ì-SëS" |
| 대ìÂ' | | | | ì˜존Ã-˜ëS" |
| ì¦Â가가 | | | | 맨ëÂÂì„ |
| 있다. | | | | ƵÃ-´ |
| 그런 | | | | 서비ìS¤ë¥ |
| 지나치ê | | | | ¼ ì œê³µÃ- |
| ÂŒ ìš"구Ã-˜ëS" | | | | 지ë„ |
| 대본ì-Â선| | | | 모른다. |
| œÃ«S", ì ÂÃ-©Ã-Âœ | | | | ê±°ì˜ |
| ê±´ì¶-ìˆ ì˜ | | | | 온ê°- |
| ì„ Ãƒ | | | | ì»´Ã"¨Ã„° |
| 그리ê³ | | | | Ã"Œëž˜ÃS¸à (TM) |
| 실시ëS" | | | | ˆì€ 서버 |
| 긴ìš"Ã-˜ê²Œ | | | | Ã"Œëž«Ã¼으 |
| ëœ다. 실ì | | | | 로 ìž'ë (TM) Ã- |
| œë¡œ | | | | 수 있다. |
| 개ì-...ìžÂ가 | | | | 그러므ë¡ |
| ê±´ì¶-ìˆ ì´ | | | | Âœ, 최ê³ |
| ì´ Ã"„ë¡œì | | | | ì»´Ã"¨Ã„°ì-Âà |
| ÂÃS¸ë¥¼ | | | | ¬Â„Âœ PCì- |
| 위Ã-´ ëÂ" ì | | | | 서버 |
| Â당Ã-Âœ ê° | | | | Ã"Œëž«Ã¼ì˜ |
| ôë¼ì´ì-¸ | | | | 많ì€ |
| ÃS¸/서버 | | | | 다른 |
| Ã"„ë¡œì | | | | 공급잠|
| ÂÃS¸ì˜ | | | | 밠많ì€ |
| 시ìž'ì-Âì (TM) | | | | 가ëSÂ¥Ã-Âœ |
| € 싸워ì-¼ | | | | ì¢...류가, |
| Ã-˜ëS" 기본ì | | | | 있다. |
| Âì¸ | | | | ê°Âê°Âì€ |
| 질문ì˜ | | | | Ã'œì¤€ ë...¸ë |
| Ã-œê°œ - "- 2ì¤' | | | | (TM) 량ì˜ ÃS¹ì |
| ë˜ÂëS" 3 | | | | - ì¢...류, |
| 층ì€?" | | | | 다른 |
| ì´다. | | | | Ã'ˆì§ˆ |
| 재미있, | | | | Ã-„ìš"ì¡°ê±´, |
| 모ë" 성과 | | | | ë° |
| ì¤'시 | | | | 가격과 |
| ôë¼ì´ì-¸ | | | | 성과 ìS¤ÃÂŽ |
| ÃS¸/서버 | | | | (TM) ÃS¸ëŸ¼ì˜ |
| ì‹ ì²Âì˜ 17%ëS" | | | | 다른 |
| 층층 | | | | 지ì-Âì-Â서 |
| 3ìÂ´ê³ ë (TM) | | | | 좋다. |
| Ã-¥ì€ Standish Group | | | | 사용잠|
| International, Inc. ì˜ | | | | 기ì-...ì€ |
| 시장 | | | | 다른 |
| 조사 | | | | 다른 |
| 단체ì- | | | | Ã-„ìš"ì (TM) € |
| ë"°ë¥´ë©´, | | | | ì¼치Ã-˜ê¸° |
| 성장Ã-˜ê³ | | | | 위Ã-˜ì-¬ |
| 있다. | | | | Ã"Œëž˜ÃS¸à (TM) |
| ê±´ì¶-ìˆ ì€ | | | | ˆì„ ì„ ì -Ã- |
| 소Ã"„ÃS¸ì›¨ | | | | 수 있다. |
| ì-´ | | | | ì„ ÃƒÂì˜ |
| ë""ìžÂì¸과 | | | | ì´ ÃÂÂì€ |
| ê¸°ìˆ | | | | ë³´ì-¬ì£¼ëS" |
| 설계ì˜ | | | | 숫잠|
| 모ë" | | | | 3ì-Â서 |
| ì-'ìƒÂì- | | | | 개ì¸ |
| ì˜ÂÃ-¥ì„ | | | | Ã"Œëž˜ÃS¸à (TM) |
| 미친다. | | | | ˆì- |
| ê±´ì¶-가ëS" | | | | 사용ìžÂëS" |
| ì‹ ì²Âì˜ | | | | 많ì€ |
| ë³µÃ-©ì„±, | | | | 서버 |
| ì-„¤Ã...Âì² | | | | Ã"Œëž«Ã¼ì- |
| ìœ Ã˜-ì- | | | | 서비ìS¤ì- |
| ê²°ì -Ã-˜ê¸° ì | | | | ì 'ê·¼ì´ |
| „ì-Â, | | | | 있ì„지ë |
| 사용ìžÂì | | | | „ 모른다 |
| ˜ 수, | | | | 설ëª...ëÂœë‹ |
| 네ÃS¸ì›ŒÃ | | | | ¤. ì´것ì€ |
| ¬Ã¬Â˜ | | | | ë˜ÂÃ-Âœ |
| ê·¸ë"¤ì˜ | | | | 지금 |
| 지리ì | | | | ì»´Ã"¨Ã„° |
| Âì¸ 분산, | | | | Æµì‹ |
| 본질 ë° | | | | ë§Âì-Â서 |
| ì‹ ì²Âì˜ ì | | | | 많ì€ |
| „ë°˜ì Âì¸ | | | | 다른 |
| 처리 | | | | ê·¼ì›Âì-Â선|
| Ã-„ìš"를 | | | | œ 다른 |
| ìš"구ëÂÂœ | | | | ê³³ì- |
| ƵÃ-©ê³¼ | | | | 서비ìS¤Ã-˜ |
| ì¡°à (TM) | | | | «S" 그것ì„ |
| "시¤기ì | | | | ì„ ÃƒÂÃ- |
| ˜ 수준 ê³ | | | | 지ë„ |
| ë ¤Ã-œë‹¤. | | | | 모른다 |
| 부ì Â당Ã-Âœ | | | | 개ì¸ |
| ê±´ì¶- | | | | Ã"Œëž˜ÃS¸à (TM) |
| 설계 ë˜ÂëS" | | | | ˆì- ë‹¨ëÂ... |
| ì†ÂìƒÂë˜ëS" | | | | 사용ì- |
| 실시ëS" | | | | 초ì Âì˜ |
| 쯤ì°ÂÃ-Âœ | | | | êµÂ대를 |
| ìÂ'답 | | | | 설ëª...Ã-œë‹ |
| 시간 | | | | . |
| 귀착ë | | | | ôë¼ì´ì-¸ |
| 수 | | | | ÃS¸ì (TM) € |
| 있ì-ˆë‹¤. | | | | 서버 |
| ê±´ì¶-ìˆ ì˜ | | | | Ã"Œëž˜ÃS¸à (TM) |
| ì„ ÃƒÂì€ | | | | ˆìœ¼ë¡œ |
| ë˜ÂÃ-Âœ ì‹ | | | | 체계ì˜ |
| ì²Âì˜ | | | | 분극ì€ |
| 개발 | | | | 개ì¸ì˜ì (TM) |
| 시간ì- | | | | € ê³µìœ |
| 밠미래 | | | | ìžÂ웠|
| 융Ƶ성 | | | | 사ì´ |
| ë° ì -비 | | | | 구별ì„ |
| ì˜ÂÃ-¥ì„ | | | | ì¸ì‹ÂÃ-œë‹ |
| 미친다. | | | | ¤. 갠개ì¸ |
| Ø„재 문Ã- | | | | Ã"Œëž˜ÃS¸à (TM) |
| (TM) ì€ | | | | ˆì€ ì´ë (TM) |
| 충분Ã-˜ê² | | | | Ã- 수 있ì„ |
| | | | 지ë„ |
| ôë¼ì´ì-¸ | | | | 모르ê³ |
| ÃS¸/서버 | | | | 다 우ì-°Ã-Âœ |
| ê±´ì¶-ìˆ ì˜ | | | | ì†Â실 |
| ì´ ì-'ìƒÂì„ | | | | ì†ÂìƒÂì˜ |
| 모ë" | | | | 위Ã-˜ì- |
| 다루지 | | | | ë"œëŸ¬ë‚´ëS" |
| ì-SëS"다. ì´ | | | | ëÂ...립ì Âì¸ |
| 서류ëS" | | | | 개ì¸ |
| ôë¼ì´ì-¸ | | | | ìžÂì›Âì´ë |
| ÃS¸/서버 | | | | ¤. ì-Â으로, |
| ê±´ì¶-ìˆ ì˜ | | | | 서버 |
| 기본 | | | | Ã"Œëž«Ã¼ì |
| 개ë...Âì„ ì | | | | ê³µìœ |
| -ì˜Ã-˜ê³ , 2ì¤' 3 | | | | ìžÂì›Âì„ |
| 층 ê±´ì¶-ìˆ | | | | 보ظÃ-˜ê³ , |
| ì„ 기ìˆ | | | | ê³ 치ê³ , |
| Ã-˜ê³ | | | | 주ì˜ê¹S게 |
| ê·¸ë"¤ì˜ | | | | 처리Ã-Âœ à (TM) |
| ê°Âê° | | | | ˜ê²½ì„ ì |
| ì´ë" ë° ì | | | | œê³µÃ-œë‹¤. |
| ÂœÃ-ϓ„ | | | | |
| 분ì„ÂÃ-œë‹ | | | | 숫ìžÂì-Â선|
| ¤. | | | | ì„ ÃƒÂÃ- |
| 재사용ì | | | | 것ì´다 |
| ˜ 개발 ë...¸ë | | | | 3개ì˜ |
| Â¥, 융Ƶ성 | | | | 많ì€ |
| 밠| | | | 서버 |
| 용ì´Ã-¨ì- | | | | Ã"Œëž«Ã¼ ë |
| 있ëS" | | | | (TM) ì¼Ã-Âœ |
| 다름ì€ | | | | 기ìˆ ì´를 |
| ë˜ÂÃ-Âœ ì-´ë-¤ | | | | 위Ã-´ |
| 주ì-´ì§„ | | | | ôë¼ì´ì-¸ |
| Ã"„ë¡œì ÂÃS¸ë" | | | | ÃS¸ì (TM) € |
| 지를 | | | | 서버 |
| 위Ã-Âœ ì | | | | Ã"Œëž˜ÃS¸à (TM) ˆ |
| ÂÃ-©Ã-Âœ | | | | (기계설ë |
| ê±´ì¶-ìˆ ì˜ | | | | ¹Â„ì˜ ë (TM) |
| ì„ Ãƒ ëÂ"를 | | | | ì¼Ã-Âœ |
| ë³´ì¡°Ã-˜ê¸° | | | | ì¢...류를 |
| 위Ã-˜ì-¬ | | | | 가진 |
| 비êµÂëÂœë | | | | 예를ë"¤ë©´ |
| ¤. | | | | PCì (TM) € 운옠|
| | | | 체계) |
| 장 2 | | | | 사용ëÂœë |
| | | | ¤ |
| ì-Â사 & defintion: - | | | | ì-´ë""ë¼ë„, |
| | | | 개ì¸과 |
| ì-Â사ëS" | | | | ê³µìœ |
| 워ĸ루ì | | | | ìžÂ웠|
| ˜ 대Ã- (TM) | | | | 사ì´ ì´ |
| 1996ë...„ì˜ | | | | 구별 |
| 5ì›"ì-Â서 Oracle ì | | | | 만ë"¤ì-´ì |
| -부 금융 | | | | ¸ì-¼ Ã-œë‹¤. |
| (OGF)를 | | | | Ã-œê³„ì-Â서 |
| 실Ã-‰Ã-ˆë‹¤ | | | | «S", ë (TM) ì¼Ã-Âœ |
| . Solaris ë˜ÂëS" ìœ | | | | 기계ëS" |
| 닉ìS¤ à (TM) | | | | 개ì¸ |
| ˜ê²½ì- | | | | Ã"Œëž˜ÃS¸à (TM) ˆ |
| ê·¸ë¦¬ê³ | | | | 밠서버 |
| 멀리 IBM/VMì- | | | | Ã"Œëž«Ã¼ ë'˜ |
| Ø„지ì- | | | | 다ì¼지ë |
| 개발ëÂÂœ | | | | „ 모른다 |
| ì장ì-Â선| | | | (예를ë"¤ë© |
| 납Ã'ˆì-...잠| | | | ë (TM) 료 ì- |
| 지ì›ÂëÂÂœ | | | | ë (TM) 료 |
| ì장ì- | | | | 네ÃS¸ì›ŒÃ |
| ì´ë (TM) ëÂÂœ | | | | ¬Ã¬-Â서; 3.2를 |
| UWì˜ ì¤'Ã-µ | | | | ë³´ì‹Â시ì |
| ڌ계 ì | | | | ¤). ì-¸ì œë‚˜, |
| ϑ„. | | | | 서버 ì-ÂÃ- |
| 계ÚÂì€ | | | | ì€ ê³µìœ |
| ê·¸ë-ÂŒ (ê·¸ë | | | | ìžÂì›Âì˜ |
| ‡ì§€ | | | | 가용성 |
| ì-S으면 | | | | ê·¸ë¦¬ê³ ì (TM) |
| 모ë" ) 사ì-... | | | | „ì „성ì„ |
| 체계를 | | | | 보장Ã-˜ëS" |
| ëÂ" 단 | | | | ì˜무를 |
| Ã-˜ë‚˜ | | | | 가ì |
| 납Ã'ˆì-...ìžÂà | | | | ¸ì˜¨ë‹¤. |
| ¡œ ì´ë (TM) | | | | |
| Ã-˜ê³ 단 | | | | ôë¼ì´ì- |
| Ã-˜ë‚˜ | | | | ÃS¸ 서버 |
| ë°ì´Ã€ë² | | | | 미ë"¤ì›¨ì-´: |
| ì´ìS¤ | | | | - |
| Ã"Œëž˜ÃS¸à (TM) ˆ | | | | |
| (ë'˜ 다를 | | | | 우리ëS" |
| 위Ã-Âœ Oracle)ì- | | | | ôë¼ì´ì-¸ |
| Ã'œì¤€à (TM) | | | | ÃS¸ 서버 |
| "Ã-˜ê¸° 위Ã-Âœ | | | | 미ë"¤ì›¨ì-´à |
| 것ì´ì-ˆë‹ | | | | «Â¥Â¼ |
| . ì-„주 ð | | | | 다ìŒ과 |
| 최ì‹ 신Solaris | | | | ê° (TM) ìÂÂŒ ì |
| 체계ëS" | | | | -ì˜Ã-œë‹¤: |
| OGF를 가진 | | | | |
| ë (TM) ì¼Ã-Âœ | | | | ôë¼ì´ì- |
| 체계ì- | | | | ÃS¸ 서버 ì- |
| ì´ 다른 | | | | Ã"Œë¦¬ì¼€ì |
| Oracleì- | | | | ì...˜ |
| ì˜Ã-˜ì-¬ | | | | 소Ã"„ÃS¸ì›¨ |
| 공급ëÂÂœ | | | | ì-´ì˜ |
| 서비ìS¤ CO | | | | 분리ë˜ëS" |
| 위치ì˜ | | | | 부분ì„ |
| ë...¸ë ¥ìœ¼ë¡œ | | | | 지ì›ÂÃ-˜ê³ |
| 구매ë˜ì-ˆ | | | | Ã-¨ê»˜ |
| 다. Ã-‰ì - | | | | ì¼Ã-˜ëS" |
| 네ÃS¸ì›ŒÃ | | | | 가ëSÂ¥Ã-˜ê²Œ |
| ¬, ì˜ì -서 | | | | Ã-˜ëS" |
| ì-¬ê³¼ê¸°ì (TM) | | | | ì장ëÂÂœ |
| € à (TM) œë (TM) ì | | | | 소Ã"„ÃS¸ì›¨ |
| Âì¸ | | | | ì-´. |
| 소Ƶ량 | | | | ì´것ì€ |
| ê°Â시를 | | | | Û¨ì"¬ |
| 가진 ê·¸ | | | | ôë¼ì´ì-¸ |
| 네ÃS¸ì›ŒÃ | | | | ÃS¸ 서버 |
| ¬Ã«Â¥Â¼ | | | | 기ìˆ ì˜ |
| 벽으로 | | | | 가장 |
| 막ëS" 불ì„ | | | | 복잡Ã-Âœ |
| ê³ | | | | 지ì-Âì´닠|
| 립시¤ëS" | | | | ¤. |
| ìÃ-¨Ã-Âœ | | | | ì-¬ê¸°ì-Â서 |
| 네ÃS¸ì›ŒÃ | | | | ë³µÃ-©ì„±ì- |
| ¬ ë³´ì-ˆ | | | | ì§'ì¤'Ã-´ì„œ |
| ì-„¤Ã...Âì² | | | | 우리ëS" |
| ëS" | | | | 다른 |
| 계ÚÂë˜ì- | | | | 지ì-Âì„ |
| 다. | | | | 관계ë˜ |
| 체계ëS" ì € | | | | 간단Ã-Âœ ìœ |
| ë³´ì-ˆ | | | | 지Ã- 수 |
| ì-„¤Ã...Âì² | | | | 있다. |
| 를 | | | | 그것 |
| 실Ã-‰Ã-˜ê¸° | | | | ìžÂì²´ |
| 위Ã-˜ì-¬ | | | | ê°Âê°Âì´ |
| 구매ëÂ˜ê³ | | | | 배부ë |
| 배치ë˜ì-ˆ | | | | 지ë„ |
| 다. | | | | 모른다, |
| 다량ì€ | | | | 그리ê³ |
| ê·¸ë (TM) ì-ˆ | | | | 최대량ì |
| 변à (TM) | | | | ´ 서로 |
| "Ã-ˆë‹¤. 모ë" | | | | 관계를 |
| 사ì-... | | | | 가지ëS" |
| 체계를 | | | | ìÃ-¨Ã-œë‹¤ |
| ì´ë (TM) Ã-˜ëS" | | | | 기ëS¥ì˜ |
| 위Ã-˜ì-¬ | | | | 많ì€ |
| OGF가 지금 | | | | ì¢...류를. |
| 1996ë...„ Ã-Âœ 벌 ì | | | | ì-´ë-¤ìÂۓ˜ |
| €ìª½ì- | | | | 주ìš" 지ì-Â: |
| 서비ìS¤ë¥ | | | | |
| ¼ ëÂ" 계Ú | | | | • |
| ìÃ-¨Ã-˜ëS" ë | | | | 네ÃS¸ì›ŒÃ‚ |
| (TM) ì-ˆ | | | | ¹ 서비ìS¤ |
| 실ÃάÃ-ˆë‹ | | | | |
| ¤. 주목Ã- | | | | • 분산 |
| 만Ã-˜ê²Œ, | | | | ì- |
| 우리ëS" | | | | Ã"Œë¦¬ì¼€ì |
| (4분기 | | | | ì...˜ |
| 1998ë...„ì-Â서 | | | | 서비ìS¤ |
| 배치ë˜ëS") | | | | |
| 사람ë"¤ Soft/SIS | | | | • 분산 |
| (Ã- (TM) 샠| | | | 시ìS¤Ã...Âœ |
| ì-ˆë‚´ë¶€)ì (TM) | | | | 관리 |
| € 가진 | | | | |
| 급ì-¬ë¶€ë¥ | | | | •ëS" ì-ˆì |
| ¼ 위Ã-´ | | | | „ì„ |
| 사람ë"¤ Soft/HRMS | | | | 배부Ã-ˆë‹ |
| (ìÂ¸ì  | | | | ¤ |
| ìžÂ웠| | | | |
| 관리 | | | | •ëS" 목Ã'Âœ |
| 체계)가 | | | | 관리를 |
| 그러므ë¡ | | | | 배부Ã-ˆë‹ |
| Âœ Oracle가 | | | | ¤ |
| 우리ì˜ | | | | |
| 사ì-...ì„ | | | | • |
| 위Ã-Âœ ì´ | | | | 사용잠|
| 주ìš" | | | | ì¸Ä°ÃŽ˜ì |
| 성분ì„ ì | | | | ´ìS¤ 관리 |
| „달Ã- 수 | | | | |
| ì-†ìSµë‹ˆë‹¤ | | | | • ì¸쇄 |
| 몇 ë...„ì„ | | | | 관리 |
| ë"°ë¥¼ | | | | |
| 것ì„ | | | | • |
| ìš"구Ã-œë‹¤. | | | | ë°ì´Ä° |
| ë˜ÂÃ-Âœ | | | | 관리 |
| 우리ëS" | | | | |
| 다른 ì‹ | | | | • 거래 |
| ì²Âì´ 지ì | | | | 관리 |
| -ë ë-Œ | | | | |
| ë°ì´Ã€ë² | | | | • ìž'ì-... |
| ì´ìS¤ë¡œ | | | | ÃÂÂ름 |
| Oracle를 | | | | 관리 |
| ìš"구Ã-˜ëS" | | | | 숫잠4ëS" |
| 것ì´ ì | | | | ôë¼ì´ì-¸ |
| Â당Ã-Âœ, | | | | ÃS¸ 서버 ì- |
| 그것 Oracle | | | | Ã"Œë¦¬ì¼€ì |
| ë°ì´Ã€ë² | | | | ì...˜ |
| ì´ìS¤ ë° | | | | 소Ã"„ÃS¸ì›¨ |
| ë˜ÂëS" ë°'ì- | | | | ì-´ë¥¼ 위Ã-Âœ |
| 있ëS" 운옠| | | | ì´ |
| 체계ì˜ | | | | 미ë"¤ì›¨ì-´ |
| ë (TM) ì¼Ã-Âœ | | | | 지ì›Âì˜ |
| 버ì | | | | ìƒÂì§- |
| „으로 | | | | 대Ã'ϓ´닠|
| ì¦Âëª...ë | | | | ¤. 그것ì€ |
| 것ì´ëÂ¼ê³ | | | | ôë¼ì´ì-¸ |
| 예ìƒÂÃ-˜ëS" | | | | ÃS¸ 서버 |
| 것ì´ | | | | 기ìˆ ì„ |
| 무리Ã-˜ë‹ | | | | 사용ìžÂì |
| 그러나, | | | | ˜ ì-...무ì- ì |
| 발견Ã-ˆë‹ | | | | Â당Ã-Âœ ì |
| . 기ìˆ ì€ | | | | „ì²´ 사ì-... |
| 너무 | | | | ë²"위ì˜ |
| 빨리 변à | | | | 맞ì€Î¸ì- |
| (TM) "Ã-œë‹¤: | | | | ìž'ë (TM) Ã-˜ëS" |
| 최ì‹ 신Solaris | | | | 가ëSÂ¥Ã-˜ê²Œ |
| 체계ëS" ëÂ" | | | | Ã-˜ê¸°ì- |
| ì´샠| | | | 있ëS" |
| Ø„재가 | | | | 미ë"¤ì›¨ì-´à |
| ì-„니다. | | | | ¬Â˜ |
| 네ÃS¸ì›ŒÃ | | | | ì¤'ìš"성ì„ |
| ¬Ã«S" "빨간 | | | | ê°-ì¡°Ã-œë‹¤. |
| ë°©"ì- ìžˆëS" | | | | ì´것ì€ |
| Ã-‰ì - 체계 | | | | 기ì-... |
| ë° êµÂì -ì„ | | | | 경계ì˜ |
| ƵÃ-˜ì-¬ | | | | 맞ì€Î¸ì- |
| Ã-‰ì - | | | | 부문과 |
| 사용ìžÂë¥ | | | | 기ëS¥ì Âì¸ |
| ¼ ê³ | | | | 경계ì˜ |
| 립시¤ê | | | | 맞ì€Î¸ì- |
| ° 위Ã-˜ì-¬ | | | | ìƒÂظ |
| 개조ë˜ì-ˆ | | | | ìž'용ì„, |
| 다. | | | | ê·¸ë¦¬ê³ |
| 그러나, | | | | ì-„마 |
| Ã-‰ì - | | | | ìÃ-¨Ã- |
| 방ظ벽 | | | | 지ë„ |
| ë° à (TM) œë (TM) ì | | | | 모른다. |
| Âì¸ | | | | |
| 소Ƶ량 | | | | 숫잠4 |
| ê°Â시ìžÂëS" | | | | ôë¼ì´ì-¸ |
| ê²°ì½" | | | | ÃS¸ 서버 |
| 실Ã-‰ë˜짠| | | | 미ë"¤ì›¨ì-´ |
| € ì-Sì-˜ë‹¤ - | | | | |
| 최근ì- ì² | | | | ôë¼ì´ì- |
| ê±°ë˜ì-ˆë‹ | | | | ÃS¸ 서버ëS" |
| . | | | | ë„구로 |
| | | | 만ë"¤ê³ |
| ì -ì˜: | | | | 서비ìS¤Ã-Âœ |
| ôë¼ì´ì-¸ | | | | «Â‹Â¤: - |
| ÃS¸/서버 | | | | ôë¼ì´ì-¸ |
| 계산ì˜ | | | | ÃS¸ 서버 |
| 다량 | | | | 체계ëS" |
| ë³´ë„ | | | | 복잡Ã- |
| ë²"위ì-Âë„ | | | | 것ì´ |
| 불구Ã-˜ê³ , | | | | 지ë„ |
| ì¸ | | | | 모르지ë§ |
| ôë¼ì´ì-¸ | | | | ÂŒ, 잘 ƵÃ-© |
| ÃS¸/서버 | | | | 체계 ë° |
| 진짜로 | | | | 잘 |
| 무ìS¨ ì | | | | 설계ë˜ëS" |
| -ì˜ì˜ | | | | 사용잠|
| 주위ì- | | | | ì¸Ä°ÃŽ˜ì |
| 다량 | | | | ´ìS¤ë¡œ |
| Ø¼ëž€ì´ | | | | 기ìˆ ì Âì¸ |
| 있다. | | | | ë³µÃ-©ì„±ì |
| ôë¼ì´ì-¸ | | | | |
| ÃS¸ì (TM) € | | | | 사용ìžÂì- |
| 서버ëS" | | | | 게 |
| 소Ã"„ÃS¸ì›¨ | | | | ë³´ì´면 |
| ì-´ì (TM) € | | | | ì-ˆëœ다; |
| 기계설ë | | | | 근본ì |
| „ 실재물 | | | | Â으로 |
| ì-„ë‹ (TM) | | | | ìÂ'용 |
| 니다ì´ë | | | | Ã"„로그랠|
| ¤. | | | | 개발잠|
| ôë¼ì´ì-¸ | | | | ë° |
| ÃS¸/서버 | | | | 서비ìS¤ ì |
| 그것ì˜ | | | | œê³µìžÂ를 |
| 기본ì Âì¸ | | | | 위Ã-Âœ 문ì |
| 모ì-'ì-Â서ëS | | | | ϓ´다. |
| " 성취ë˜ëS" | | | | ê·¸ë"¤ì€ |
| 다른 | | | | 소Ã"„ÃS¸ì›¨ |
| 소Ã"„ÃS¸ì›¨ | | | | ì-´ 개발 |
| ì-´ | | | | 공구ì (TM) € ì |
| 실재물 | | | | „문ì Âì¸ |
| (서버)ì- | | | | ì-...무를 ì´ |
| ì˜Ã-˜ì-¬ | | | | ë³µÃ-©ì„±ì |
| 구체ì Âì¸ | | | | 처리Ã-˜ê³ |
| ìš"구를 | | | | 숨기ëS" |
| 만ë"ϑS" | | | | 것ì„ ëÂ-ëS" |
| 소Ã"„ÃS¸ì›¨ | | | | Ã-„ìš"로 |
| ì-´ | | | | Ã-œë‹¤. |
| 실재물 | | | | Ã-„ìš"로 Ã-Âœ |
| (ôë¼ì´ì- | | | | ì-¸ì œë‚˜ |
| ÃS¸)를 | | | | 공구 ë° |
| ìÃ-¨Ã-œë‹¤. | | | | 서비ìS¤ì |
| 숫잠1ëS" | | | | ˜ 많ì€ |
| ôë¼ì´ì-¸ | | | | 것ì€ ë (TM) |
| ÃS¸/서버 | | | | ì¼Ã-˜, |
| êµÂà (TM) ˜ì„ | | | | 그러나 |
| 설ëª...Ã-œë‹ | | | | ë˜ÂÃ-Âœ |
| . | | | | ôë¼ì´ì-¸ |
| ôë¼ì´ì-¸ | | | | ÃS¸ 서버 |
| ÃS¸ ê³¼ì -ì€ | | | | 체계ì- |
| 서버ì- | | | | Ã-„ìš"로 |
| ìš"구를 | | | | Ã-œë‹¤ |
| 보낸다. | | | | ÃS¹ì„±ì„ |
| 서버ëS" | | | | 있다. |
| ë©"시지률| | | | ì¤'ìš"Ã-Âœ |
| ¼ Ã-´ì„ÂÃ-˜ê³ | | | | ì¼반ì Âì¸ |
| ê·¸ Û„ì- | | | | ì Âì€ |
| ìš"구를 | | | | ì장Ã-Âœ |
| 성취Ã-˜ëS" | | | | ("shrink-wrapped") ìÂ'용 |
| 것ì„ | | | | 소Ã"„ÃS¸ì›¨ |
| 시ë„Ã-œë‹ | | | | ì-´, 기ì-...ì´ |
| ¤. ìš"구를 | | | | Ã"„로그랠|
| 성취Ã-˜ê¸ | | | | ê±´ì¶- |
| 위Ã-˜ì-‘S", | | | | 공구를 |
| 서버ëS" | | | | Ã-„ìš"로 |
| 지신| | | | Ã-˜ì§€ ì-SëS" |
| 근웠| | | | 사용ìžÂë¥ |
| (ë°ì´Ã€ë | | | | ¼ 위Ã-´ ì |
| ì´ìS¤), | | | | €ê²ƒì´다. |
| 가공 | | | | ì장Ã-Âœ |
| ìžÂ료를 | | | | ôë¼ì´ì-¸ |
| (계산ì„ | | | | ÃS¸ 서버 ì- |
| 실Ã-‰Ã-˜ì‹ | | | | Ã"Œë¦¬ì¼€ì |
| 시오) | | | | ì...˜ ì ÂœÃ'ˆì€ |
| ì-¸ê¸‰Ã-˜ê±°à | | | | 지금 |
| «Â‚˜, 주변 | | | | ë„"게 ìœ |
| 장치를 | | | | Ú¨Ã-˜ê²Œ |
| Ƶì | | | | ëÂ˜ê³ |
| ÂœÃ-˜ê±°ë‚˜, | | | | 있다 |
| 다른 | | | | (예를ë"¤ë© |
| 서버ì˜ | | | | 분배ëÂÂœ |
| ì¶"가ì Âì¸ | | | | 사무실ê |
| ìš"구를 | | | | ¼ |
| 만ë"¤ì-´ì-¼ Ã- | | | | 그룹웨ì- |
| 지ë„ | | | | ì‹ ì²Â, |
| 모른다. | | | | 사ì-... |
| 다량 | | | | ڌ계 ì‹ |
| ê±´ì¶-ìˆ | | | | ì²Â, ì¸웠|
| ì-Â서ëS", | | | | ë° |
| ôë¼ì´ì-¸ | | | | 급ì-¬ë¶€ ì‹ |
| ÃS¸ëS" 다수 | | | | ì²Â). 똠|
| 서버ì˜ | | | | 다른 |
| ìš"구를 | | | | ì¤'ìš"Ã-Âœ ë (TM) |
| 만ë"¤ê³ | | | | Ã-¥ì€ |
| 서버ëS" | | | | 다른 |
| 다수 | | | | 공구 (밠|
| ôë¼ì´ì-¸ | | | | ì-¸ì-´) |
| ÃS¸ë¥¼ | | | | 모ë"ˆë¼ |
| 서비ìS¤Ã- | | | | ìÂ'용 |
| 수 있다. | | | | 시ìS¤Ã...ϓ˜ |
| | | | 다른 |
| 숫잠1 - | | | | 부분ì„ |
| ôë¼ì´ì-¸ | | | | 위Ã-´ |
| ÃS¸/서버 | | | | Ã-„ìš"Ã-˜ë‹¤ë |
| 거래 | | | | S" 것ì„ |
| | | | ì´다. |
| ôë¼ì´ì- | | | | 주ìš" |
| ÃS¸ì (TM) € | | | | 구별ì€: |
| 서버 | | | | |
| 사ì´ | | | | • |
| 관계가 | | | | 사용잠|
| ëª...ë ¹ ë˜ÂëS" | | | | ì¸Ä°ÃŽ˜ì |
| Ƶì Âœ | | | | ´ìS¤: |
| 관계다ëS" | | | | 그래Ã"½ |
| 것ì„ | | | | 사용잠|
| ì´Ã-´Ã-˜ëS" | | | | ì¸Ä°ÃŽ˜ì |
| 것ì´ | | | | ´ìS¤ì˜ |
| ì¤'ìš"Ã-˜ë‹¤. | | | | ê±´ì¶- ë° |
| ì-´ë-¤ | | | | ì-´ë-¤ ì‹ ì² |
| 주ì-´ì§„ | | | | ë...¼ë¦¬ë" |
| êµÂà (TM) ˜ë" | | | | 지를 |
| 지ì-Â서ëS", | | | | 위Ã-Âœ ì-¸ì-´ |
| ôë¼ì´ì-¸ | | | | 그리ê³ |
| ÃS¸ëS" | | | | 공구ëS" |
| ìš"구를 | | | | ê·¸ë"¤ |
| 개시Ã-˜ê³ | | | | 친밀Ã-˜ê² |
| 서버ëS" | | | | 관ë |
| ê·¸ëŸ¬ë¯€ë¡ | | | | ¨ì‹œì¼°ë‹¤; |
| œ | | | | 예를ë"¤ë©´ |
| 반ìÂ'Ã-œë‹¤. | | | | GUI 공구ì (TM) € |
| 서버ëS" | | | | Visual Basic. |
| ôë¼ì´ì-¸ | | | | |
| ÃS¸ë¥¼ | | | | • |
| 가진 대à | | | | ë°ì´Ã€ë² |
| (TM) "를 | | | | ì´ìS¤: ì‹ ì² |
| 개시Ã- 수 | | | | ë...¼ë¦¬ì˜ |
| ì-†ë‹¤. | | | | ë°ì´Ã€ë² |
| ôë¼ì´ì-¸ | | | | ì´ìS¤ì˜ |
| ÃS¸ì (TM) € | | | | ê±´ì¶-ì„ |
| 서버가 | | | | 위Ã-Âœ ì-¸ì-´ |
| 소Ã"„ÃS¸ì›¨ | | | | 그리ê³ |
| ì-´ | | | | 공구ëS", |
| 실재물ì | | | | ÃŒŒì¼ |
| ´ê¸° | | | | 시ìS¤Ã...Âœ |
| ë-Œë¬¸ì- | | | | 밠목Ã'Âœ |
| ì-´ë-¤ ì | | | | ìƒÂì  ë° |
| ÂÃ-©Ã-Âœ | | | | ê±´ì¶- ê·¸ë"¤ |
| 기계설ë | | | | 친밀Ã-˜ê² |
| „ë" 지ì- | | | | 관ë |
| 있ì„ 수 | | | | ¨ì‹œì¼°ë‹¤; |
| 있다. | | | | 예를ë"¤ë©´ |
| ôë¼ì´ì-¸ | | | | ìžÂ료 |
| ÃS¸ ê³¼ì -ì€, | | | | ì¡°ìž' ì-¸ì-´ì |
| 예를 | | | | (TM) € |
| ë"¤ë©´, | | | | 관계Ø- |
| 네ÃS¸ì›ŒÃ | | | | ë°ì´Ã€ë² |
| ¬ 서버 | | | | ì´ìS¤ 4GLs. |
| 기계설ë | | | | |
| „ì- ìžˆì„ | | | | • |
| 수 ìžˆê³ , | | | | 비즈니ìS |
| 다른 | | | | ¤ 로ì§Â: |
| 서버 | | | | 사용잠|
| 기계설ë | | | | ì¸Ä°ÃŽ˜ì |
| „ì- ë˜ÂëS" | | | | ´ìS¤ì (TM) € |
| PCì- ë‹¬ë¦¬ëS" | | | | ë°ì´Ã€ë² |
| 서버 | | | | ì´ìS¤ì-Â서 |
| Ã"„로세ìS¤ | | | | 분리ë˜ì- |
| ¬-Â서 | | | | ë...¼ë¦¬ì |
| ìžÂ료를 | | | | Â으로 ì¸ |
| ìš"구Ã-œë‹¤. | | | | ì‹ ì² |
| 다른 | | | | ë...¼ë¦¬ì˜ |
| 대본ì-Â선| | | | ê±´ì¶-ì„ |
| œÃ«S", | | | | 위Ã-Âœ ì-¸ì-´ |
| ôë¼ì´ì-¸ | | | | 그리ê³ |
| ÃS¸ì (TM) € | | | | 공구; |
| 서버 ê³¼ì | | | | 예를ë"¤ë©´ |
| -ì€ ë (TM) | | | | COBOL. |
| ì¼Ã-Âœ | | | | |
| 육체ì Âì¸ | | | | • 분산 |
| 기계설ë | | | | 처리: |
| „ ìƒÂìžÂì- | | | | ì-¸ì-´ì (TM) € |
| 있ì„ 수 | | | | 공구ëS" |
| 있다. 실ì | | | | 분산 |
| œë¡œ, prototyping | | | | 처리 |
| 단계ì-Âì„ | | | | 그리ê³ |
| œ, | | | | 모ë" ìƒÂ기 |
| 개발ìžÂì- | | | | 기ëSÂ¥ |
| ëS" ë (TM) ì¼Ã-Âœ PC | | | | ì-Âì-´ë¦¬ì-´ ì |
| Ã-˜ë"œì›¨ì-´ì- | | | | „문à (TM) |
|  ë°œÃ'Âœ | | | | "Ã-ˆë‹¤ (ì (TM) € |
| ôë¼ì´ì-¸ | | | | 다른 ê³¼Ã- |
| ÃS¸ 그리ê³ | | | | (TM) 기ìˆ ê³¼ |
| ë°ì´Ã€ë² | | | | 조짠|
| ì´ìS¤ | | | | 경계를) |
| 서버가 | | | | 뼘으로 |
| ë'˜ 다 있ëS" | | | | 재기를 |
| 것ì„ ì„ | | | | 위Ã-´; |
| ÃÂÃ- 지ë„ | | | | 예를ë"¤ë©´ |
| 모른다. | | | | ì›Â격 |
| 서버ëS" ì‹ | | | | Ã"„로시ì € |
| 철| | | | ظ출 (RPC) |
| ë...¼ë¦¬ì˜ | | | | 공구. |
| 대부분 | | | | |
| Û„ì- | | | | • |
| 시Ã-˜Ã-˜ëS" | | | | 시ìS¤Ã...Âœ |
| ëÂ" ì „ | | | | 관리: |
| ìƒÂ산ì„ | | | | 소Ã"„ÃS¸ì›¨ |
| 위Ã-Âœ 대Ø- | | | | ì-´ì˜ ì „ìž |
| ì ϑ„ì- | | | | 배급ì„ |
| 나ì¤'ì- | | | | 위Ã-Âœ ë°©ë²- |
| (배부Ã-˜ëS") | | | | 밠공구, |
| ì´ë (TM) Ã- 수 | | | | ë° |
| 있ê³ | | | | ôë¼ì´ì-¸ |
| ìžÂ료 | | | | ÃS¸ 서버 |
| 구조 | | | | 체계ì˜ |
| 발달ì€ ì | | | | 가ë (TM) ë° |
| (TM) „ì „Ã-˜ë‹¤. | | | | ì¡°ì -. |
| ôë¼ì´ì-¸ | | | | |
| ÃS¸ì (TM) € | | | | ì´ |
| 서버가 | | | | 공구ì˜ |
| ë (TM) ì¼Ã-Âœ | | | | 대부분ì |
| 기계ì- | | | | € |
| 있ì„ 수 | | | | 미ë"¤ì›¨ì-´à |
| 있ëÂ"ë¼ë | | | | ¬Â˜ 대ìÂ' |
| , ì´ | | | | 지ì-Âê³¼ |
| 서류ëS" | | | | ì-°ê´€ëœ닠|
| 분산 ì- | | | | ¤. |
| Ã"Œë¦¬ì¼€ì | | | | |
| ì...˜ì„, i.e | | | | 장 6 |
| ê·¸ë"¤ | | | | |
| 창조Ã-˜ê¸° | | | | ôë¼ì´ì- |
| 위Ã-˜ì-¬ | | | | ÃS¸ 서버 |
| ì´용ëÂÂœ | | | | ê±´ì¶-ìˆ : |
| ê±´ì¶-ìˆ ì- | | | | ìÂ´ì „ |
| ôë¼ì´ì-¸ | | | | 섹ì...˜ì-Â선|
| ÃS¸ì (TM) € | | | | 기ìˆ ëÂÂœ |
| 서버가 | | | | 기ìˆ ì-Â, |
| 분리ë˜ëS" | | | | ôë¼ì´ì-¸ |
| 육체ì Âì¸ | | | | ÃS¸ 서버 |
| 장치ì- | | | | ê±´ì¶-ìˆ ì˜ |
| 있ëS" ê³³ì- 1 | | | | 3개ì˜ |
| 차로 ì-¼ë | | | | ì¢...류ëS" - |
| ¤Ã-œë‹¤. | | | | Û„ì- |
| Ã-´ë¦¬ì- | | | | ë´Â서 - |
| ë"°ë¥´ë©´ | | | | ì‹Â별ë |
| (ê·¸ ì (TM) ¸ | | | | 수 있다. |
| ì-¬ëŸ¬ë¶„), | | | | |
| 네ÃS¸ì›ŒÃ | | | | 기본ì Âì¸ |
| ¬Ã¬Â˜ 다른 | | | | ôë¼ì´ì-¸ |
| 마ë""ì- | | | | ÃS¸ 서버: - |
| 수Ã-‰Ã-˜ê³ | | | | 기본ì Âì¸ |
| ê³µë (TM) | | | | ôë¼ì´ì-¸ |
| 목Ã'œë¥¼ | | | | ÃS¸ 서버 |
| 달성Ã-˜ê¸ | | | | ê±´ì¶-ìˆ , |
| ° 위Ã-˜ì-¬ | | | | 개ì¸ |
| Ø'ë Â¥Ã-˜ëS" | | | | ì§'권ëÂÂœ ì‹ |
| 분리ë˜ëS" | | | | ì²Âì-Â서 - |
| 부ì†Âì´ | | | | 2개 |
| 분산 ì- | | | | 부Ã'ˆìœ¼ë¡ |
| Ã"Œë¦¬ì¼€ì | | | | 나뉜다: |
| ì...˜ì- | | | | 개ì¸ |
| ì˜Ã-˜ì-¬ | | | | Ã"Œëž˜ÃS¸à (TM) |
| ì´루ì-´ì ¸ | | | | ˆì- |
| 있다. | | | | ôë¼ì´ì-¸ |
| 지웠| | | | ÃS¸ 부ì†Â, |
| 기반ì€ | | | | 밠서버 |
| ë˜ÂÃ-Âœ | | | | Ã"Œëž«Ã¼ì- |
| 분산 | | | | 서버 |
| 처리ì˜ ê³ | | | | 부ì†Â. |
| ìœ Ã-Âœ | | | | Û„ìžÂëS" |
| ë³µÃ-©ì„±ì | | | | 수시로 |
| 최ì¢... | | | | ê³µìœ |
| 사용ìžÂì- | | | | ìžÂ웠|
| 게 | | | | ÃŒŒì¼ |
| ë³´ì´지 | | | | 서비ìS¤ì (TM) |
| ì-SëS" | | | | € ê° (TM) ì€ |
| 만ë"¤ì-´ì-¼ | | | | ì¸쇄 |
| Ã-œë‹¤. | | | | 서비ìS¤, |
| ôë¼ì´ì-¸ | | | | ë°ì´Ã€ë² |
| ÃS¸/서버 | | | | ì´ìS¤, ë˜ÂëS" |
| ê±´ì¶-ìˆ ì- | | | | ì-´ë-¤ application-specific |
| 있ëS" | | | | 기ëS¥ì´닠|
| ôë¼ì´ì-¸ | | | | . 기간 |
| ÃS¸ëS" | | | | ôë¼ì´ì-¸ |
| 그래Ã"½ | | | | ÃS¸ì (TM) € |
| 사용잠| | | | 서버ëS" |
| ì¸Ä°ÃŽ˜ì | | | | Ã-˜ë"œì›¨ì-´ |
| ´ìS¤ (GUI)를 | | | | Ã"Œëž˜ÃS¸à (TM) ˆ |
| Ã-„ìš"ì-†ë‹¤, | | | | ë° ìÂ'용 |
| 그러나, | | | | 소Ã"„ÃS¸ì›¨ |
| ôë¼ì´ì-¸ | | | | ì-´ |
| ÃS¸ | | | | 분대를 |
| 서버ì˜ | | | | ì-¸ê¸‰Ã-˜ëS" |
| 질량 | | | | ì´용ëÂœë‹ |
| ìƒÂÃ'ˆà (TM) "ëS" GUI | | | | ¤ (수시로 |
| ôë¼ì´ì-¸ | | | | ì-½ê°„ ì- |
| ÃS¸ì˜ à (TM) | | | | 매Ã-˜ê²Œ). |
| -산 ë-Œë¬¸ì- | | | | 기본ì Âì¸ |
| ð | | | | ôë¼ì´ì-¸ |
| 부분ì-Âì„ | | | | ÃS¸ 서버 |
| œ 대략 ì (TM) | | | | ê±´ì¶-ìˆ ì€ |
| "다. ì¸쇄 | | | | 숫잠|
| (i.e | | | | 9ì-Â서 |
| 네ÃS¸ì›ŒÃ | | | | 설ëª...ëÂœë‹ |
| ¬ ì¸쇄 | | | | ¤ (ì´미 |
| 대기ì-´) | | | | 숫잠|
| ê°Âê³ ëS" | | | | 6ì-Â서 ëÂ" |
| ë˜ÂëS" 발Ã'Âœ (i.e | | | | ìžÂ세Þˆ |
| X ì°½)ì (TM) € ê° (TM) | | | | ë³´ìÂ´ê³ ). |
| ì€ | | | | |
| ôë¼ì´ì-¸ | | | | 숫잠9 |
| ÃS¸/서버 | | | | 기본ì Âì¸ |
| 시ìS¤Ã...Âœ | | | | ôë¼ì´ì-¸ |
| 지웠| | | | ÃS¸ 서버 |
| ë†'게 ÃS¹ì | | | | ê±´ì¶-ìˆ |
| -Ã-Âœ 기ëSÂ¥ | | | | 기본ì Âì¸ |
| 서비ìS¤. | | | | ôë¼ì´ì-¸ |
| ì´ ÃS¹ìˆ˜ | | | | ÃS¸ 서버 |
| 목ì  | | | | 윤곽ì€ |
| 실시가 | | | | 근거리 |
| ì¤'ìš"Ã-Âœ ë (TM) | | | | 네ÃS¸ì› |
| ì-ˆ, ì´ | | | | (근거리 |
| 서류ëS" | | | | Æµì‹ |
| 기ëS¥ì- | | | | ë§Â)ì˜ |
| 있ëS" | | | | 주위ì- |
| 융Ƶ성ì | | | | ì¼반ì |
| „ ìš"구Ã-˜ëS" | | | | Â으로 |
| 분배ëÂÂœ | | | | ÃŽ¸ì„±ëÂœë |
| ôë¼ì´ì-¸ | | | | ¤. ì „ì²´ |
| ÃS¸/서버 | | | | ì§'Ã-©ì- |
| ê±´ì¶-ìˆ ì- | | | | ì˜Ã-˜ì-¬ |
| 우위Ã-˜ê² | | | | PC-LAN로 보Ƶ |
| | | | 기ìˆ ëÂ˜ê³ , |
| 관지Ã-œë‹ | | | | Ã-œê°œ |
| ¤ | | | | ì´샠공ë |
| | | | (TM) PC (서버 |
| 장 3 | | | | Ã"Œëž«Ã¼) |
| | | | Ã"ŒëŸ¬ìS¤ |
| ôë¼ì´ì- | | | | 개ì¸ |
| ÃS¸ | | | | 사용 |
| 서버ì˜ | | | | (개ì¸ |
| ì˜미: - | | | | Ã"Œëž˜ÃS¸à (TM) |
| | | | ˆ)를 위Ã-Âœ |
| ôë¼ì´ì- | | | | 많ì€ PC가, |
| ÃS¸ | | | | ì´루ì-´ì ¸ |
| 서버ì˜ | | | | 있다. |
| 사ì-... | | | | ì´ì- ì§€ì- |
| ì˜미: - | | | | 서버 |
| ôë¼ì´ì-¸ | | | | Ã"Œëž˜ÃS¸à (TM) |
| ÃS¸ 서버ëS" | | | | ˆì€ |
| 사ì-... ì -ë³´ | | | | ê·¸ë"¤ì- |
| 시ìS¤Ã...ϓ˜ | | | | enterprise-wideì (TM) € ì (TM) |
| ì¡°ìž'샠| | | | ¸ë¶€ |
| ڨ과ì-Â선| | | | 네ÃS¸ì›ŒÃ |
| 다ìÂÂŒ | | | | ¬Ã«Â¡Âœ, |
| 단계ì´ê | | | | 그리ê³ |
| ì¼반ì | | | | 서버ì- PC LANs |
| Â으로 | | | | 보Ƶ |
| ì-žìœ¼ë¡œ | | | | 출ìž...구률|
| ê°Â지ëÂœë | | | | ¼ ì |
| ¤. ì´것ì€ | | | | œê³µÃ-œë‹¤. |
| ØÂì‹ ì˜ | | | | ì´것ì€ |
| ìS¹ê³„ì-Â서 | | | | 숫잠|
| 누ì ÂëÂÂœ | | | | 10ì-Â서 |
| ì´ìµì„ | | | | 설ëª...ëÂœë‹ |
| 나À내ëS" | | | | ¤. |
| 숫잠| | | | |
| 1ì-Â서 | | | | PCì (TM) € PC LANsì˜ ì |
| 설ëª...ëÂœë‹ | | | | Âì-Â서 1 |
| ¤. | | | | 차로 |
| 비즈니ìS | | | | Ã'ϯ„Ã-´, ì´ |
| ¤ | | | | 기본ì Âì¸ |
| ì»´Ã"¨ÃÂŒ...ì€ | | | | ôë¼ì´ì-¸ |
| ì¼괄 | | | | ÃS¸ 서버 |
| 처리를 | | | | 개ë... |
| 가진 1960 | | | | 숫잠10ëS" ì |
| ë...„대ì-Â선| | | | „Ø-ì Âì¸ PC-LAN |
| œ | | | | 온ê°- |
| 시ìž'Ã-ˆë‹¤. | | | | ì»´Ã"¨Ã„° |
| 1970 ë...„대ì- | | | | ë° |
| 있ëS" 주ìš" | | | | 네ÃS¸ì›ŒÃ |
| ØÂì‹ ì€ | | | | ¬ |
| 온ë¼ì¸ | | | | (예를ë"¤ë© |
| ÃS¸ëžœìžÂì...˜ | | | | PC, ìœ 닉ìS¤, |
| 처리 (OLTP) 2 | | | | 주ìš"골격 |
| ë°"Ã- à (TM) | | | | , LANs ë° WANs)ì- ì |
| "ë©´ì- ì -ë³´ | | | | Â용 |
| 기ìˆ | | | | 가ëSÂ¥Ã-˜ë‹¤. |
| (그것)를 | | | | |
| ê°€ì ¸ì˜¨, | | | | 기초 ì |
| 그것ì-Â게 | | | | €ìª½ì-Â: - |
| 불가결Ã- | | | | 기본ì Âì¸ |
| 부분ì„ | | | | ôë¼ì´ì-¸ |
| 사ì-... ê³¼ì | | | | ÃS¸ 서버 ì |
| -ì˜ | | | | €ìª½ì- - |
| 만ë"¤ì-´ì´à | | | | 가공Ã-˜ê³ , |
| ³ . ì¡°Ã-©ì- | | | | Ø'ë Â¥ |
| 있ëS" ì¼괄 | | | | 가공Ã-˜ê³ |
| 처리 | | | | ëÂ...립 |
| ê·¸ë¦¬ê³ OLTPëS" | | | | 가공 ë (TM) |
| 최대 | | | | 료 ì- ë (TM) |
| 기ì-...ì˜ ì | | | | 료가 |
| -보 | | | | 있다. |
| 시ìS¤Ã...ϓ˜ | | | | 기간 ë (TM) |
| ì¤'Ã-µì- | | | | 료 ì- ë (TM) |
| 있ëS" 것ì„ | | | | 료 |
| 계ì†ÂÃ-œë‹ | | | | 가공ì€ |
| ¤. ê·¸ ë-ÂŒ | | | | 서버 |
| 1980ë...„대 | | | | Ã"Œëž«Ã¼ì´ |
| 개ì¸ 측ì | | | | ì-†ê³ , ì‹ |
| -ìÂۓ-Â서 | | | | ì²Âì˜ |
| 그것ì„ | | | | 서버 |
| ë³´ÃŽ¸ì | | | | 부ì†Âì´ |
| Â으로 | | | | 개ì¸ |
| 기ì-...ì„ | | | | Ã"Œëž˜ÃS¸à (TM) |
| ƵÃ-˜ì-¬ | | | | ˆì- ìžˆëS" |
| 그것ì´ë | | | | 윤곽ì„ |
| ¼ÃªÂ³ ì | | | | ì-¸ê¸‰Ã-˜ëS" |
| Â당Ã-´ë˜ | | | | ì´용ëÂœë‹ |
| ë° | | | | ¤. ì´ |
| ì´산Ã-˜ëS" | | | | 기초ì- |
| Ã-Âœ ì (TM) "다. | | | | ìž'ë (TM) Ã-˜ëS" |
| 지금 1990 | | | | 네ÃS¸ì›ŒÃ |
| ë...„대ì-Â선| | | | ¬Ã«S" ë (TM) 료 ì- |
| œ, | | | | ë (TM) 료 |
| ôë¼ì´ì-¸ | | | | 네ÃS¸ì›ŒÃ |
| ÃS¸ 서버ëS" | | | | ¬Ã«Â¡Âœ |
| ì -ë³´ | | | | 불린다. |
| 시ìS¤Ã...ϓ˜ | | | | ì´것ì€ |
| 분리ë˜ëS" | | | | ìž'ì€ PC LANs, |
| 부분 | | | | ë"±ë"± |
| Û„ì- | | | | 실Ã-‰ì˜ |
| ƵÃ-©ì˜ | | | | ê°'ì´ 싼 |
| ë°©ë²-ìÂ´ê³ | | | | ë°©ë²-ì´닠|
| ì¼반ì | | | | ; 그러나 |
| Â으로 | | | | 분리ë˜ëS" |
| Ã-¨ê»˜ | | | | 서버 |
| ê°Â지ëÂœë | | | | Ã"Œëž«Ã¼ì˜ |
| ¤. ì €ê²ƒì€ | | | | 부족ì€ |
| 그것ì˜ | | | | 체계 ì (TM) „ì |
| ì-ÂÃ- ë° | | | | „성ì„ |
| 그것ì˜ | | | | ê°Â소시à|
| ì¤'ìš"성ì´à | | | | ¤ê³ |
| «Â‹Â¤. | | | | 시ìS¤Ã...Âœ |
| | | | 관리 ì-´ë |
| 숫잠1 | | | | ¤ì›€ìœ¼ë¡œ |
| ê°Â지ëÂÂœ | | | | ì´ëÂΓ-´ |
| ôë¼ì´ì-¸ | | | | 낸다. |
| ÃS¸ 서버 | | | | 기간 Ø'ë Â¥ |
| ì´러Ã-Âœ | | | | 가공ì€ |
| ìƒÂà (TM) | | | | ìÂ'용 |
| ©ì-Â서 | | | | 소Ã"„ÃS¸ì›¨ |
| ôë¼ì´ì-¸ | | | | ì-´ê°€ |
| ÃS¸ | | | | 분배ëÂÂœ ì |
| 서버ì˜ | | | | -샠|
| 사ì-... | | | | 분리ë˜ëS" |
| 충격ì€ | | | | 서버 |
| (ë˜ÂëS" | | | | Ã"Œëž«Ã¼ì¸ |
| ôë¼ì´ì-¸ | | | | 윤곽ì„ |
| ÃS¸/서버) | | | | ì-¸ê¸‰Ã-˜ëS" |
| 사ì-... ë° | | | | ì´용ëÂœë‹ |
| 기ìˆ ì Âì¸ | | | | ¤, ìƒÂظ |
| Ƶ찰ë Â¥ | | | | ìž'용ì˜ |
| 밠매매 | | | | ôë¼ì´ì-¸ |
| ë©"시지ì | | | | ÃS¸ì (TM) € |
| ˜ 모ë" | | | | 서버 |
| ë°©ë²-ì- ì | | | | ëÂÂì€ |
| ÂœÃ'ˆì˜ | | | | 서버 |
| ê±°ì˜ ê° | | | | Ã"Œëž«Ã¼ì- |
| ì¢...류ì- ì | | | | ë'˜ 다 |
| Â용ë˜ëS" | | | | 있다. |
| 대ì¤'ì Âì¸ | | | | ì´것ì€ |
| ìœ ëª... | | | | ë (TM) ì¼Ã-Âœ ì‹ |
| ìƒÂÃ'œê°€, | | | | ì²Âì˜ |
| 밠| | | | 부분 |
| ë˜ì-ˆë‹¤. | | | | 사ì´ |
| ì´것ì€ | | | | 분리ë˜ëS" |
| ÃS¹ì -Ã-Âœ | | | | ì‹ ì² |
| ì˜미ì˜ | | | | 사ì´ |
| 그것ì„ | | | | ìƒÂظ |
| 배수Ã-´ | | | | ìž'용ì„, |
| ê²½Ã-¥ì´ | | | | 다만 |
| 있다; | | | | ìÃ-¨Ã-œë‹¤. |
| 그러나 | | | | 기간 |
| ê·¸ë ‡ê²Œ | | | | ëÂ...립 |
| Ã-˜ë¯€ë¡œì | | | | 가공ì€ |
| , 실ì œë¡œ | | | | ì‹ ì²Âì˜ |
| 그것ì˜ | | | | 모ë" |
| 가깠| | | | 부분ì´ |
| ë³´ÃŽ¸ì Âì¸ | | | | 1개ì˜ |
| ìÂ'용성ì | | | | Ã"Œëž˜ÃS¸à (TM) ˆ |
| à (TM) | | | | (보Ƶ |
| -ì¸Ã-œë‹¤. | | | | 개ì¸ |
| | | | Ã"Œëž˜ÃS¸à (TM) |
| ôë¼ì´ì- | | | | ˆ)ì- ìžˆëS" |
| ÃS¸ | | | | 윤곽ì„ |
| 서버ì˜ | | | | ì-¸ê¸‰Ã-˜ëS" |
| 기ìˆ ì Âì¸ | | | | ì´용ëÂœë‹ |
| ì˜미: - | | | | ¤. 부솠|
| ì´Ã-´ | | | | 사ì´ ì-´ë-¤ |
| ôë¼ì´ì-¸ | | | | ôë¼ì´ì-¸ |
| ÃS¸ | | | | ÃS¸ 서버 |
| 서버를 | | | | 관계ë„ ì |
| 위Ã-Âœ ìœ | | | | (TM) ¸ë¶€ì- |
| 용Ã-Âœ | | | | ë³´ì´지 |
| 출발ì | | | | ì-S다. |
| Âì€ Gartner | | | | 사람ë"¤ì |
| 그룹ì´ | | | | ë˜ÂÃ-Âœ |
| 사용Ã-Âœ | | | | ì-¬ëŸ¬ê°€ì§ |
| ì-½ì‹ ì | | | | 다른 |
| -ì˜ì´다: | | | | ì˜미ì (TM) € |
| | | | Ã-¨ê»˜ êµÂà (TM) |
| "ôë¼ì´ì- | | | | ˜Ã- 수 있 |
| ÃS¸ 서버 | | | | 기간 ë (TM) |
| 분리ë˜ëS" | | | | 료 ì- ë (TM) |
| ì»´Ã"¨Ã„°ì- | | | | 료ì (TM) € Ø'ë |
| ì´Ã-‰ë˜ëS" | | | | Â¥ 가공ì„, |
| ì-...무로ì´ | | | | 그리ê³ |
| «Â‹Â¤ ì‹ ì²Â, | | | | 사용Ã-œë‹ |
| ê·¸ì¤' | | | | ¤. ì´것ì€ |
| Ã-˜ë‚˜ì˜ | | | | ؼ란과 |
| 나누ëS"ì´ | | | | 오Ã-´ë¥¼ |
| «Â‹Â¤ | | | | ì¼으¤ëS" |
| Ã'€ê·¸ë¦´ | | | | ì›Âì¸ì´ |
| 워ÓS¤Ã...ÂŒ | | | | ëœ다. |
| ì´ì...˜ | | | | ë˜ÂÃ-Âœ |
| (예를ë"¤ë© | | | | 서버ì (TM) € |
| PC)."ëS" ì´ ì | | | | ê° (TM) ì€ |
| -ì˜ëS" | | | | ì-¬ëŸ¬ê°€ì§ |
| ôë¼ì´ì-¸ | | | | 다른 |
| ÃS¸ | | | | 보다 ì |
| 서버가 | | | | Â게 ìœ |
| 분배ëÂÂœ | | | | ëª...Ã-Âœ ì |
| 계산 | | | | -립ì´ ë˜ÂëS" |
| 그리ê³ | | | | ì˜뢰잠|
| 소Ã"„ÃS¸ì›¨ | | | | ë° |
| ì-´ 구조 (ì‹ | | | | ìƒÂ산잠|
| ì²Âì€ | | | | ë˜ÂëS" |
| 분리ë˜ëS" | | | | 소비잠|
| ì»´Ã"¨Ã„°ì- | | | | 있다. 모ë" |
| 있ì„지ë | | | | 주ìš" ì |
| „ 모른다) | | | | -립ì€ |
| ì-...무로ì- | | | | 숫잠|
| 관Ã-˜ì-¬ | | | | 11ì-Â서 |
| 나뉜다 | | | | Ã-¨ê»˜ |
| 다ëS" 것ì„ | | | | 설ëª...ëÂœë‹ |
| ë°Âތ다. | | | | ¤. |
| 그것ì€ | | | | |
| ôë¼ì´ì-¸ | | | | 진짜로 |
| ÃS¸ | | | | 기본ì Âì¸ |
| 서버가 | | | | ôë¼ì´ì-¸ |
| 온ê°- ì -ë³´ | | | | ÃS¸ |
| 시ìS¤Ã...œìœ¼ | | | | 서버를 |
| 로 PC를 | | | | ì˜미Ã-˜ëS"ì |
| ƵÃ-©Ã-˜ëS" | | | | §Â€ ì-´ëS |
| ë°©ë²- | | | | 것ì´ëÂ¼ê³ |
| ì´다 | | | | ì- ì˜Ã-˜ì-¬) |
| ìƒÂëª... ì | | | | 숫잠11 |
| Âì„ | | | | 불운Ã-˜ì˜ |
| 반Ã-Â¥Ã-œë‹¤. | | | | ôë¼ì´ì-¸ |
| | | | ÃS¸ 서버 |
| ì „ê°ˆì˜ | | | | 시ìS¤Ã...Âœ |
| 3마리ì˜ | | | | 구조ì˜ |
| 발ìƒÂ: | | | | ê°Âì¢... ì |
| | | | -립ì€, |
| ظìS¤ÃS¸ | | | | 많ì€ |
| 기본 | | | | 사람ë"¤ |
| ê±´ì¶-ìˆ | | | | 예리Ã-˜ê²Œ |
| (ôë¼ì´ì- | | | | ôë¼ì´ì-¸ |
| ÃS¸/서버 | | | | ÃS¸ |
| ê±´ì¶-ìˆ | | | | 서버ì-Âì„ |
| ì-„ë‹ (TM) | | | | œ 다른 |
| 니다): | | | | 개ë...Âì„ |
| 주ìš"골격 | | | | 분à (TM) |
| 소Ã"„ÃS¸ì›¨ | | | | "Ã-œë‹¤ (. |
| ì-´ | | | | ì´것ì€ |
| 구조로 | | | | 모ë'Â가 |
| 모ë" ì -ë³´ëS" | | | | 1개ì˜ |
| ì¤'ì- (TM) 주ì | | | | Ƶì¼Ã-Âœ |
| „산기 | | | | 구조 |
| ì-ˆì- ìžˆë‹¤. | | | | 내ì˜ |
| 사용ìžÂëS" | | | | ì´체ìÂ´ë‹ |
| ¤ìS¤ÃS¸ë¡œà | | | | ¤ ìƒÂëª... ì |
| ¬를 ë¶ (TM) | | | | Âì„ |
| ìž¡ê³ | | | | ì-´ë'¡ê²Œ |
| 주ì¸ì- ì € | | | | Ã-œë‹¤: |
| ì -보를 | | | | ôë¼ì´ì-¸ |
| 보내ëS" | | | | ÃS¸ 서버 |
| 맨ëÂÂì„ | | | | ê±´ì¶-ìˆ . |
| ƵÃ-´ì„œ | | | | 그것ì€ |
| 주ì¸과 | | | | ë˜ÂÃ-Âœ |
| ìƒÂظ | | | | 오Ã-´Ã-˜ê¸° |
| ìž'용Ã-œë‹¤. | | | | 쉬운 |
| 주ìš"골격 | | | | 계산서ë |
| 소Ã"„ÃS¸ì›¨ | | | | ¡Âœ |
| ì-´ 구조ëS" | | | | ôë¼ì´ì-¸ |
| Ã-˜ë"œì›¨ì-´ | | | | ÃS¸ 서버 |
| Ã"Œëž˜ÃS¸à (TM) | | | | (ì˜미 |
| ˆì- | | | | 기본ì Âì¸ |
| 묶ì´지 | | | | ôë¼ì´ì-¸ |
| ì-SëS"다. | | | | ÃS¸ 서버)ëS" |
| 사용잠| | | | 소멸Ã-˜ë‹ |
| ìƒÂظ | | | | ¤ ì´ë¼ëS" |
| ìž'용ì€ PCì | | | | 취지ì˜ |
| (TM) € ìœ 닉ìS¤ | | | | ì´ëÂΓ-´ |
| 워ÓS¤Ã...ÂŒ | | | | 내ê³ , Ø'ë Â¥ |
| ì´ì...˜ì„ | | | | 가공과 |
| 사용Ã-˜ì-¬ | | | | ê° (TM) ì€ |
| ëÂÂë‚ 수 | | | | 다른 |
| 있다. | | | | ê¸°ìˆ ë¡œ |
| 주ìš"골격 | | | | 대ì‹ ëÂ˜ê³ |
| 소Ã"„ÃS¸ì›¨ | | | | 있다. |
| ì-´ | | | | |
| 구조ì˜ ì | | | | ì¼반ì Âì¸ |
| ÂœÃ-ϓ€ | | | | ôë¼ì´ì-¸ |
| ê·¸ë"¤ì´ | | | | ÃS¸ 서버 |
| 쉽게 | | | | ê±´ì¶-ìˆ : - |
| 그래Ã"½ | | | | 기본ì Âì¸ |
| 사용잠| | | | ôë¼ì´ì-¸ |
| ì¸Ä°ÃŽ˜ì | | | | ÃS¸ 서버ì (TM) |
| ´ìS¤ë¥¼ | | | | € 3.1ì (TM) € 3.2ì- |
| 지ì›ÂÃ-˜ì§ | | | | 있ëS" 모ë" ì |
| € ì-S거나 | | | | -립ì˜ |
| 지리ì | | | | 기본ì Âì¸ |
| Â으로 | | | | ì ÂœÃ-ϓ€ |
| ì´산Ã-Âœ | | | | ê·¸ë"¤ì´ |
| 위치ì-Â선| | | | Ã-˜ë"œì›¨ì-´ |
| œ 다수 | | | | 구성ì- |
| ë°ì´Ã€ë² | | | | ì˜존Ã-˜ëS" |
| ì´ìS¤ì- ì | | | | ë°©ë²-ì- |
| 'ê·¼Ã-˜ì§€ | | | | 있ëS" |
| ì-SëS"다 | | | | 소Ã"„ÃS¸ì›¨ |
| ì´다. | | | | ì-´ |
| 지난 | | | | 구성ì„ ì |
| 몇ë...„ê°„ì- | | | | -ì˜Ã-œë‹¤ |
| 서ëS", | | | | ì´다. |
| 주ìš"골격 | | | | 게다가, |
| ì€ | | | | 그것ì€ |
| 분배ëÂÂœ | | | | 소Ã"„ÃS¸ì›¨ |
| ôë¼ì´ì-¸ | | | | ì-´ ë˜ÂëS" |
| ÃS¸/서버 | | | | 기계설ë |
| ê±´ì¶-ìˆ ì- | | | | „ê°€ |
| 있ëS" | | | | 기간ì- |
| 서버로 | | | | ì˜Ã-˜ì-¬ |
| 새로운 | | | | ôë¼ì´ì-¸ |
| 사용ì„ | | | | ÃS¸ì (TM) € |
| ì°¾ì-„냈닠| | | | 서버 |
| ¤ | | | | ì-¸ê¸‰Ã-œã„´ |
| | | | «Â‹Â¤Ã«S" 것ì„ |
| 근거리 | | | | 수시로 ì- |
| Æµì‹ 맠| | | | 매Ã-˜ë‹¤. |
| ÃŒŒì¼ ê³µìœ | | | | ì´ ì ÂœÃ-Âœ ë° |
| ê±´ì¶-ìˆ | | | | ì- |
| (ôë¼ì´ì- | | | | 매Ã-¨ì-Â서 |
| ÃS¸/서버 | | | | ë„주Ã-˜ê¸ |
| ê±´ì¶-ìˆ | | | | 위Ã-˜ì-‘S", |
| ì-„ë‹ (TM) | | | | 소Ã"„ÃS¸ì›¨ |
| 니다): - | | | | ì-´ì- ìžˆëS" |
| ì›Â래 PC | | | | ôë¼ì´ì-¸ |
| 네ÃS¸ì›ŒÃ | | | | ÃS¸ 서버 |
| ¬Ã«S" | | | | 관계ëS" |
| 서버가 | | | | ôë¼ì´ì-¸ |
| ê³µë (TM) | | | | ÃS¸ ë˜ÂëS" |
| 위치ì-Â선| | | | 서버로 |
| œ ÃÂìƒÂ용 à | | | | 소Ã"„ÃS¸ì›¨ |
| (TM) ˜ê²½ì- | | | | ì-´ 위치 |
| ÃŒŒì¼ì„ | | | | 그리ê³ |
| 다운로ë" | | | | 근본ì Âì¸ |
| Ã-˜ëS" ÃŒŒì¼ | | | | 기계설ë |
| ê³µìœ | | | | „ì˜ ì-´ë-¤ |
| ê±´ì¶-ìˆ ì- | | | | 분류ë" |
| 근거Ã-ˆë‹ | | | | 지ì€ |
| . ìš"구ëÂÂœ | | | | 별ë„로 ì |
| 사용잠| | | | -ì˜ë˜ì-´ì-¼ |
| ì¼ì€ | | | | Ã-œë‹¤. |
| ÃÂìƒÂ용 à | | | | 근본ì Âì¸ |
| (TM) ˜ê²½ì-Â서 | | | | ì -à (TM) "ëS" |
| ê·¸ ë-ÂŒ (를 | | | | ôë¼ì´ì-¸ |
| ìÃ-¨Ã-˜ì-¬ | | | | ÃS¸ì (TM) € |
| ë...¼ë¦¬ ë° | | | | 서버가 |
| ìžÂ료) | | | | 서비ìS¤ê° |
| 달린다. | | | | € (ê°Âê°Â) |
| ÃŒŒì¼ ê³µìœ | | | | 사용ëÂ˜ê³ |
| ê±´ì¶-ìˆ ì€ | | | | ì œê³µë˜ëS" |
| ê³µë (TM) | | | | ì-ÂÃ- ì´다 |
| 경우ì- | | | | ì´다, ì´ |
| 사용ë²-ì | | | | ì-ÂÃ- ì€ |
| ë‚(R)으면, | | | | ìžÂ치 |
| ê°±ì‹ | | | | 빌ë"© ë¸"ë¡ |
| ë...¼ìŸ | | | | 사ì´ |
| ë‚(R)다 ìž'ë | | | | 관계ì-Âì„ |
| (TM) Ã-˜ê³ , | | | | œ ìƒÂ긴다. |
| ì˜(R)겨질 | | | | 그런 |
| ìžÂ료량ì | | | | 관계ì-Âì„ |
| € ë‚(R)다. 1990 | | | | œÃ«S", |
| ë...„대ì-Â선| | | | 참가ìžÂì |
| œÃ«S", ÃŒŒì¼ | | | | ˜ Ã-œê°œëS" |
| ê³µìœ ì˜ | | | | 서비ìS¤ |
| 수용량ì | | | | (그것 |
| ´ ë-Œë¬¸ì- | | | | 있다 |
| 온ë¼ì¸ | | | | ôë¼ì´ì-¸ |
| 사용ìžÂì | | | | ÃS¸ ì-ÂÃ- |
| ˜ 수 | | | | ì´)를 |
| 성장Ã-ˆê¸ | | | | 사용Ã-œë‹ |
| | | | ¤ 똠다른 |
| 긴장ëÂ˜ê¸ | | | | Ã-œê°œëS" |
| ° ë-Œë¬¸ì- | | | | 서비ìS¤ |
| ë°"뀠PC | | | | (서버 ì-ÂÃ- |
| 근거리 | | | | ì´ |
| Æµì‹ 맠| | | | 있다)를 ì |
| (근거리 | | | | œê³µÃ-˜ê³ . |
| 네ÃS¸ì›Â) | | | | ì´것ì€ |
| 계산ì€ | | | | ôë¼ì´ì-¸ |
| (단지 | | | | ÃS¸ 서버 |
| 대략 | | | | 관계ì´ë |
| 12ëª...ì˜ | | | | ¤. ð ìœ |
| 사용ìžÂë§ | | | | ì-°Ã-Âœ 설ì |
| ÂŒ ë (TM) 시로 | | | | -ì€ ì´ |
| 만족시à| | | | 간단Ã-Âœ |
| ¬ 수 있다) | | | | 개ë...Âì˜ |
| 그래Ã"½ | | | | ì¡°Ã-©ì- |
| 사용잠| | | | ì˜Ã-´ ìŒ"ì-„ |
| ì¸Ä°ÃŽ˜ì | | | | 올릴 수 |
| ´ìS¤ (GUIs) | | | | 있다. |
| 대ì¤'ì  | | | | ì´것ì€ |
| ëÂ˜ê³ | | | | 숫잠|
| (주ìš"골겠| | | | 12ì-Â서 |
| ê³¼ ë ì | | | | 설ëª...ëÂœë‹ |
| „시를 | | | | ¤. |
| 만ë"¤ì-´ì„œ | | | | |
| 구ì‹Âì¸ | | | | ë„Ã'ϓ˜ |
| 것처럼 | | | | 오른쪽ì- |
| ë³´ì´ì‹Âì | | | | 서 |
| œì˜¤). PCëS" | | | | 나À나ëS" |
| 지금 | | | | 것과 ê° (TM) |
| ôë¼ì´ì-¸ | | | | ì´ |
| ÃS¸/서버 | | | | ôë¼ì´ì-¸ |
| ê±´ì¶-ìˆ | | | | ÃS¸ 서버 |
| ì-Â서 | | | | ê±´ì¶-ìˆ ì˜ |
| 사용ëÂ˜ê³ | | | | 숫잠12 |
| 있다 | | | | ì›Â리ëS", |
| | | | 빌ë"© ë¸"ë¡ |
| ì¸Ä°ë„· | | | | 서비ìS¤ì |
| ôë¼ì´ì-¸ | | | | ˜ 사용잠|
| ÃS¸ 서버 | | | | 그리ê³ |
| ê±´ì¶-ìˆ : - | | | | 공급잠|
| ì´ | | | | ë'˜ |
| ì¢...류를 | | | | 다ì¼지ë |
| 위Ã-Âœ | | | | „ 모른다. |
| 목Ã'ϑS" ê³¼ì | | | | 그러므ë¡ |
| -ì˜ | | | | Âœ, 그것ì-ÂëS" |
| 나머지ë | | | | ôë¼ì´ì-¸ |
| ¼ ë°'ì- | | | | ÃS¸ì (TM) € |
| 있ì„ | | | | 서버 ì-ÂÃ- |
| ë°°ê²½ | | | | ì´ 있ê³ |
| 지ì‹Âì˜ | | | | ìÂ㓤ۑ„ |
| 기초를 | | | | 다른 |
| 건설Ã-˜ê¸ | | | | 빌ë"© |
| 위Ã-Âœ | | | | ë¸"ë¡Âì„ |
| 것ì´다. | | | | 가진 |
| 기ìˆ ì˜ | | | | 많ì€ |
| 많ì€ | | | | ôë¼ì´ì-¸ |
| 지ì-Âì-Â서 | | | | ÃS¸ 서버 |
| «S" 사람ì€ | | | | 관계ì- |
| 그것ì˜ | | | | 참가Ã- |
| Ø„재 | | | | 지ë„ |
| 모ì-'ì-Â서 | | | | 모른다. |
| Ã-Â샠| | | | ê³ ë ¤ëÂÂœ ÃS¹ì |
| 존재ë˜ëS" | | | | -Ã-Âœ |
| 것과 ê° (TM) | | | | 관계ì˜ |
| ì´ | | | | 문맥ì-Â선|
| ëSÂ낌ì„ | | | | 서만 |
| 기ìˆ | | | | ôë¼ì´ì-¸ |
| ì-ȑS"다. | | | | ÃS¸ ë˜ÂëS" |
| 그러나, | | | | 서버 |
| 당ì-°Ãžˆ, | | | | ì´다. |
| 기ìˆ ì-ÂëS" | | | | 소Ã"„ÃS¸ì›¨ |
| 다른 ì-´ë-¤ | | | | ì-´ì- ìžˆëS" |
| ìžÂì-° ì | | | | ôë¼ì´ì-¸ |
| ÂìÂ´ê³ | | | | ÃS¸ 서버 |
| 부ìžÂì-°ìS¤à | | | | ê±´ì¶-ìˆ ì˜ |
| «ÂŸÂ¬Ã¬ÂšÂ´ | | | | Ø„실à (TM) "ëS" |
| Ø„샠ê° (TM) | | | | 숫잠|
| ì´ | | | | 12ì-Â서 |
| ì-Â사가 | | | | ë³´ì´지 |
| 다만 | | | | ì-SëS" () |
| 있다. | | | | Ã"„로그랠|
| 그것ì€ | | | | ì-¸ì-´ ë° |
| ì¸Ä°ë„· | | | | 미ë"¤ì›¨ì-´à |
| ë° ì›"ë"Âœ ì (TM) | | | | «Â¥Â¼ ƵÃ-´ |
| ۓ´ë"Âœ | | | | ì´다. |
| 웹ì„ | | | | 분리ë˜ëS" |
| 위Ã-´ ì´ë | | | | ì»´Ã"¨Ã„°ì |
| ‡ê²Œ ì´다. | | | | |
| ì´ 면담 | | | | 네ÃS¸ì›ŒÃ |
| ë (TM) ì-ˆì-Â, | | | | ¬ÃªÂ°Â€ |
| 우리ëS" | | | | ôë¼ì´ì-¸ |
| 오ëS˜ì¸ | | | | ÃS¸ 서버 |
| 무ì-‡ì„ | | | | ê±´ì¶-ìˆ ì˜ |
| ì¸Ä°ë„·ì | | | | 육체ì Âì¸ |
| „ 만ë" | | | | Ø„실à (TM) |
| 과거 30 ë...„ | | | | "ì- ì˜Ã-˜ì-¬ |
| 내내 | | | | ì´루ì-´ì ¸ |
| ì¼ì-´ë‚œ | | | | 있다; |
| ì-´ë-¤ì˜ | | | | Ã-„ì-°ì |
| ì¤'ìš"Ã-Âœ | | | | Â으로 |
| 발달ì„ | | | | 기간 |
| 첫째로 | | | | ôë¼ì´ì-¸ |
| ë³¼ | | | | ÃS¸ 서버ëS" |
| 것ì´다. | | | | 분산 |
| ì´ | | | | 처리를 |
| ë...„대기ë¥ | | | | 위Ã-Âœ ë (TM) |
| ¼ 검Æ Ã-Âœ | | | | ì˜ì-´ê°€ |
| Û„ì-Â, | | | | ë˜ì-´ |
| 우리ëS" | | | | ê²½Ã-¥ì´ |
| ì¸Ä°ë„·ì | | | | 있다. |
| „ | | | | ôë¼ì´ì-¸ |
| 지ì›ÂÃ-˜ëS" | | | | ÃS¸ 서버 |
| 근본ì Âì¸ | | | | ê±´ì¶-ìˆ ì€ |
| 기ìˆ ì˜ | | | | 기ìˆ ì˜ |
| 2개를 ë³¼ | | | | 다른 ì-´ë-¤ |
| 것ì´다. | | | | ÃS¹ì - |
| 첫번째 | | | | ì¢...류ì˜ PC, |
| 서로ì˜ | | | | ë˜ÂëS" |
| 몇백ëª... | | | | 사용ì- |
| ì-¼ë"Âœ ì-ˆì- | | | | 관Ã-˜ì-¬ì„œ |
| 있ëS" | | | | «Â§ÂŒ 부수ì |
| ì»´Ã"¨Ã„°ë¥ | | | | Â으로 |
| ì-°ê²°Ã-˜ê¸° | | | | ì´다. |
| 위Ã-˜ì-¬ | | | | 그러나, |
| ì´용ëÂÂœ | | | | Ø„재 ìƒÂà |
| 가장 | | | | (TM) ©ì-Â서, |
| ë„Â리 | | | | ôë¼ì´ì-¸ |
| ü진 | | | | ÃS¸ |
| Æµì‹ | | | | 서버가 PC |
| ë§Âì˜ | | | | 기ìˆ |
| ì´ëÂ"네ÃS¸, | | | | ì´용ì˜ ì |
| ì›Â래 | | | | Âì-Â서 |
| 근거리 | | | | 주로 ì |
| 네ÃS¸ì› | | | | 㑤Âëœ다 |
| (근거리 | | | | 보Ƶ ì |
| Æµì‹ ë§Â) | | | | ÂÃ-©Ã-˜ë‹¤ |
| ê¸°ìˆ ë° | | | | (우리가 |
| ì-㓤Âë„ | | | | ì˜ 위ì- |
| Ã-œê°œ | | | | ì-ˆìœ¼ë¡œ |
| ì´다. ì Âœ2ëS" | | | | 1.2ì-Â서 |
| TCP/IP ì˜ | | | | 시ìž'Ã-Âœ) Gartner ì |
| ë©"시지률| | | | -ì˜ì-Â서 |
| ¼ | | | | 것과 ê° (TM) |
| 서로ì-Âê² | | | | ì´. ìžÂ치 |
| 지시Ã-˜ê³ | | | | ôë¼ì´ì-¸ |
| | | | ÃS¸ 서버 |
| 견실Ã-˜ê² | | | | ê±´ì¶-ìˆ ì˜ |
| | | | ì´ ì¼반ì |
| êµÂƵÃ-˜ê¸ | | | | Âì¸ |
| 위Ã-˜ì-¬ ì | | | | 모ì-'ì€ (ì˜ |
| „세계 | | | | ôë¼ì´ì-¸ |
| 있ëS" | | | | ÃS¸ 서버 |
| ì»´Ã"¨Ã„°ë¥ | | | | 관계, |
| 가ëSÂ¥Ã-˜ê²Œ | | | | ôë¼ì´ì-¸ |
| Ã-˜ëS" | | | | ÃS¸ ì-ÂÃ- , |
| 소Ã"„ÃS¸ì›¨ | | | | 서버 ì-ÂÃ- |
| ì-´ | | | | 건물 |
| 기준ì´ë | | | | 막ëS"다) |
| ¤. | | | | 개방Ø- |
| ì¸Ä°ë„·ì | | | | Ã"„ë |
| „ Æ ë¡ Ã-Âœ | | | | ˆìž„워ì |
| Û„ì-Â, | | | | ì‹ ì² |
| 우리ëS" ê·¸ | | | | ê±´ì¶-ìˆ ì˜ |
| ë-ÂŒ ì›"ë"Âœ ì (TM) | | | | 기본ì Âì¸ |
| ۓ´ë"Âœ | | | | 성분ì´ë |
| 웹ì- | | | | ¤. |
| 우리ì˜ | | | | |
| 주ì˜, | | | | Assumptions:- |
| ìžÂ체를 | | | | |
| ëÂÂŒ | | | | 1.One client is connected to at most one |
| 것ì´다. | | | | server at a time. [The customer later refuted |
| 면담ì€ | | | | this assumption.] |
| 1대ì˜ | | | | |
| ì»´Ã"¨Ã„°ì- | | | | 2.Replication is a secondary effect of the |
| 달리ëS" | | | | existing fat-client architecture; we assume |
| ôë¼ì´ì-¸ | | | | that updates to one server are automatically |
| ÃS¸ | | | | propagated in a timely fashion. |
| Ã"„로그랠| | | | |
| ì´ ì-½ê°„ | | | | 3.A single client may have more than one |
| ÃS¹ì -Ã-Âœ ì | | | | session. [Replaced Assumption 1.] |
| -보를 | | | | |
| ìš"구Ã-˜ê¸° | | | | 4.All calculated columns (columns that |
| 위Ã-˜ì-¬ 똠| | | | represent behavior rather than aspects) are |
| 다른 | | | | easily & quickly calculated on the server. |
| Ã-œê°œì- | | | | |
| 달리ëS" | | | | 5.Deletion or insertion of a row forces a |
| 서버 | | | | window update on the client. |
| Ã"„로그랠| | | | |
| ê³¼ | | | | 6.Transmission of client-server traffic is |
| ì-°ë½Ã-˜ëS" | | | | out of scope.chapter-7 |
| 그것ì˜ | | | | |
| 기본ì Âì¸ | | | | Architecture Types:- When |
| ôë¼ì´ì-¸ | | | | considering a move to client/server |
| ÃS¸/서버 | | | | computing, whether it is to replace existing |
| ê±´ì¶-ìˆ ì˜ | | | | systems or introduce entirely new systems, |
| 검Æ 로 | | | | practitioners must determine which type of |
| ë˜ÂëS" ì-½ê°„ | | | | architecture they intend to use. The vast |
| 서비ìS¤ëS" | | | | majority of end user applications consist of |
| ì´Ã-‰ëœ닠| | | | three components: presentation, processing, |
| ¤ | | | | and data. The client/server architectures can |
| 시ìž'ëœ닠| | | | be defined by how these components are split |
| ¤. 웹ì€ ì | | | | up among software entities and distributed on |
| -ë³´ì˜ | | | | a network. There are a variety of ways for |
| ÃŽ˜ìÂ´ì§€ë¥ | | | | dividing these resources and implementing |
| ¼ | | | | client/server architectures. This paper will |
| ìš"구Ã-˜ê¸° | | | | focus on the most popular forms of |
| 위Ã-˜ì-¬ 웹 | | | | implementation of two-tier and three-tier |
| 브ë¼우ì | | | | client/server computing systems. Two-tier |
| € | | | | Architecture:- Although there |
| (ôë¼ì´ì- | | | | are several ways to architect a two-tier |
| ÃS¸)가 | | | | client/server system, we will focus on |
| ê°Âì¢... 웹 | | | | examining what is overwhelmingly the most |
| 서버ì (TM) € | | | | common implementation. In this |
| ì-°ë½Ã-˜ëS" | | | | implementation, the three components of an |
| ôë¼ì´ì-¸ | | | | application (presentation, processing, and |
| ÃS¸/서버 | | | | data) are divided between two software |
| ê±´ì¶-ìˆ ì„ | | | | entities (tiers): client application code and |
| 사용Ã-˜ì-¬ | | | | database server (Figure 2). A robust client |
| ë˜ÂëS" | | | | application development language and a |
| Ã"„로그랠| | | | versatile mechanism for transmitting client |
| ì€ | | | | requests to the server are essential for a |
| 서버ì˜ | | | | two-tier implementation. Presentation is |
| ì¼반 | | | | handled exclusively by the client, processing |
| 출ìž...구 | | | | is split between client and server, and data |
| 공용ì˜Âì- | | | | is stored on and accessed via the server. The |
| (CGI)를 | | | | PC client assumes the bulk of responsibility |
| ƵÃ-´ì„œ | | | | for application (functionality) logic with |
| 실Ã-‰ëÂœë‹ | | | | respect to the processing component, while |
| ¤ | | | | the database engine - with its attendant |
| 건설ë˜ì- | | | | integrity checks, query capabilities and |
| 다. Internet/WWW가 | | | | central repository functions - handles data |
| ì¼반ì Âì¸ | | | | intensive tasks. In a data access topology, a |
| 계산 | | | | data engine would process requests sent from |
| ê·¸ë¦¬ê³ | | | | the clients. Currently, the language used in |
| Æµì‹ | | | | these requests is most typically a form of |
| ì¸Ã"„ë¼갠| | | | SQL. Sending SQL from client to server |
| ë˜ëS" ë-ÂŒ, ì´ | | | | requires a tight linkage between the two |
| 준ì-„Ã-Âœ | | | | layers. To send the SQL the client must know |
| ôë¼ì´ì-¸ | | | | the syntax of the server or have this |
| ÃS¸/서버 | | | | translated via an API (Application Program |
| 관계ëS" à (TM) | | | | Interface). It must also know the location of |
| -장ëÂ˜ê³ | | | | the server, how the data is organized, and |
| 있다. | | | | how the data is named. The request may take |
| 1개ì˜ | | | | advantage of logic stored and processed on |
| 그런 à (TM) | | | | the server, which would centralize global |
| -장ì€ | | | | tasks such as validation, data integrity, and |
| ìžÂë°"를 | | | | security. Data returned to the client can be |
| ìÃ-¨Ã-œë‹¤. | | | | manipulated at the client level for further |
| ê³¼ì -ì-Â서 | | | | sub selection, business modeling, "what if" |
| 나ì¤'ì- ì´ | | | | analysis, reporting, etc. |
| ì‹ ê°œë°œì- | | | | |
| 관Ã-˜ì-¬ ëÂ" | | | | Figure 2 - Data Access Topology for two-tier |
| 많ì€ 것, | | | | architecture. Majority of functional logic |
| 그러나 | | | | exists at the client level |
| 당분간, | | | | The most compelling advantage of a |
| 우리ëS" | | | | two-tier environment is application |
| 웹ì˜ ê³ ì | | | | development speed. In most cases a two-tier |
| „ì Âì¸ | | | | system can be developed in a small fraction |
| ôë¼ì´ì-¸ | | | | of the time it would take to code a |
| ÃS¸/서버 | | | | comparable but less flexible legacy system. |
| ë""ìžÂì¸ì- | | | | Using any one of a growing number of PC-based |
| ì§'ì¤'Ã- | | | | tools, a single developer can model data and |
| 것ì´다. | | | | populate a database on a remote server, paint |
| ì-¸ì-´ 웹 | | | | a user interface, create a client with |
| ôë¼ì´ì-¸ | | | | application logic, and include data access |
| ÃS¸ì (TM) € | | | | routines. Most two-tier tools are also |
| 서버ëS" | | | | extremely robust. These environments support |
| 서로 | | | | a variety of data structures, including a |
| 불린다 HTTP | | | | number of built in procedures and functions, |
| (Ã-˜ì´Ã¼ | | | | and insulate developers from many of the more |
| Ã...ÂìS¤ÃS¸ ì | | | | mundane aspects of programming such as memory |
| „송 | | | | management. Finally these tools also lend |
| Ã"„로Æ | | | | themselves well to iterative prototyping and |
| 콜)ì-Â게 | | | | rapid application development (RAD) |
| ë§ÂÃ-œë‹¤. | | | | techniques, which can be used to ensure that |
| 당ì‹ ì€ | | | | the requirements of the users are accurately |
| HTTP를 | | | | and completely met. |
| ìƒÂ세Þˆ | | | | Tools for developing two-tier client/server |
| 배울 | | | | systems have allowed many IS organizations to |
| Ã-„ìš"ì-†ì„ | | | | attack their applications backlog, satisfying |
| 것ì´다, | | | | pent-up user demand by rapidly developing and |
| 그러나 | | | | deploying what are primarily smaller |
| 당ì‹ ì€ | | | | workgroup-based solutions. Two-tier |
| 기본ì Âì¸ | | | | architectures work well in relatively |
| HTTP | | | | homogeneous environments with fairly static |
| Ã"„로그랠| | | | business rules. This architecture is less |
| Ã-˜ëS" CGI를 | | | | suited for dispersed, heterogeneous |
| Ã-˜ê¸° | | | | environments with rapidly changing rules. As |
| 위Ã-˜ì-¬ | | | | such, relatively few IS organizations are |
| ë©"시지률| | | | using two-tier client/server architectures to |
| ¼ | | | | provide cross-departmental or cross-platform |
| 건설Ã-´ì-¼ | | | | enterprise-wide solutions |
| Ã-˜ê³ | | | | Since the bulk of application |
| 그것ì˜ | | | | logic exists on the PC client, the two-tier |
| 근본ì Âì¸ | | | | architecture faces a number of potential |
| ì² Ã- (TM) ë° | | | | version control and application |
| 그것ì˜ | | | | re-distribution problems. A change in |
| 기본Ø- | | | | business rules would require a change to the |
| 밠기ëS¥ | | | | client logic in each application in a |
| ì´Ã-´Ã-´ì-¼ | | | | corporation's portfolio, which is affected, |
| Ã-œë‹¤. | | | | by the change. Modified clients would have to |
| | | | be re-distributed through the network - a |
| 장 4 | | | | potentially difficult task given the current |
| | | | lack of robust PC version control software |
| ê³¼ì -: - | | | | and problems associated with upgrading PCs |
| | | | that are turned off or not "docked" to the |
| ôë¼ì´ì- | | | | network. System security |
| ÃS¸ ê³¼ì -: - | | | | in the two-tier environment can be |
| ôë¼ì´ì-¸ | | | | complicated since a user may require a |
| ÃS¸ ì´다 | | | | separate password for each SQL server |
| ê³¼ì - | | | | accessed. The proliferation of end-user query |
| (서버가 | | | | tools can also compromise database server |
| ì-...무 | | | | security. The overwhelming majority of client |
| (서비ìS¤)ë¥ | | | | server applications developed today are |
| ¼ | | | | designed without sophisticated middleware |
| ì´Ã-‰Ã-œã„´ | | | | technologies, which offer increased security. |
| «Â‹Â¤Ã«S" 것ì„ | | | | Instead, end-users are provided a password, |
| ìš"구Ã-˜ëS" | | | | which gives them access to a database. In |
| Ã"„로그랠| | | | many cases this same password can be used to |
| ) 서버 | | | | access the database with data-access tools |
| Ã"„로세ìS¤ | | | | available in most commercial PC spreadsheet |
| (Ã"„로그랠| | | | and database packages. Using such a tool, a |
| ¨)ì- | | | | user may be able to access otherwise hidden |
| ë©"시지률| | | | fields or tables and possibly corrupt data. |
| ¼ 보내ëS". | | | | Client tools and the SQL |
| ôë¼ì´ì-¸ | | | | middleware used in two-tier environments are |
| ÃS¸ | | | | also highly proprietary and the PC tools |
| Ã"„로그랠| | | | market is extremely volatile. The client |
| ì€ 보Ƶ | | | | server tools market seems to be changing at |
| ì‹ ì²Âì˜ | | | | an increasingly unstable rate. In 1994, the |
| 사용잠| | | | leading client/server tool developer was |
| 공용ì˜Âì- | | | | purchased by a large database firm, raising |
| 부분ì„ | | | | concern about the manufacturer's ability to |
| 처리Ã-˜ê³ , | | | | continue to work cooperatively with RDBMS |
| 사용ìžÂê° | | | | vendors, which compete with the parent |
| € ìž...ë Â¥Ã-Âœ | | | | company's products. The number two-tool maker |
| ìžÂ료를 ìœ | | | | lost millions and has been labeled as a |
| Ú¨Ã-˜ê²Œ | | | | takeover target. A firm also in the midst of |
| Ã-˜ê³ , | | | | severe financial difficulties and management |
| 서버 | | | | transition supplies the tool, which has |
| Ã"„로그랠| | | | received some of the brightest accolades in |
| ì- ìš"구를 | | | | early 1995. This kind of volatility raises |
| ÃŒŒê²¬Ã-˜ê³ , | | | | questions about the long-term viability of |
| ë-Œë-Œë¡œ | | | | any proprietary tool an organization may |
| 비즈니ìS | | | | commit to. All of this complicates |
| ¤ 로ì§Âì„ | | | | implementation of two-tier systems - |
| 수Ã-‰Ã-œë‹¤. | | | | migration from one proprietary technology to |
| ôë¼ì´ì-¸ | | | | another would require a firm to scrap much of |
| ÃS¸ 근거Ã-Âœ | | | | its investment in application code since none |
| ê³¼ì -ì€ | | | | of this code is portable from one tool to the |
| 사용ìžÂê° | | | | next. |
| € ë³´ê³ | | | | |
| ìƒÂظ | | | | Three tier:- Most |
| ìž'용Ã-˜ëS" | | | | sophisticated Web based applications, which |
| ì‹ ì²Âì˜ ì„ | | | | involve data entry, are based on a 3 tier |
| 불용ìÂ´ë‹ | | | | client server architecture. The 3 tiers are |
| ¤. | | | | |
| ôë¼ì´ì-¸ | | | | • The Client (Web Browser) |
| ÃS¸ ê³¼ì -ì€ | | | | |
| Ã-´ê²°ì±... | | | | • The Web Server/Application |
| ÃS¹ì -Ã-Âœ | | | | Server |
| ë...¼ë¦¬ë¥¼ | | | | |
| ìÃ-¨Ã-˜ê³ | | | | • The Database Server |
| ìÂ'용 | | | | The tree tier architecture |
| 시ìS¤Ã...ϓ˜ | | | | (Figure 3) attempts to overcome some of the |
| 사용ìžÂì | | | | limitations of the two-tier scheme by |
| (TM) € | | | | separating presentation, processing, and data |
| 나머지 | | | | into separate, distinct software entities |
| 사ì´ | | | | (tiers). The same types of tools can be used |
| 공용ì˜Âì- | | | | for presentation as were used in a two-tier |
| ì„ ì | | | | environment, however these tools are now |
| œê³µÃ-œë‹¤. | | | | dedicated to handling just the presentation. |
| ôë¼ì´ì-¸ | | | | When the presentation client requires |
| ÃS¸ ê³¼ì -ì€ | | | | calculations or data access, a call is made |
| ë˜ÂÃ-Âœ | | | | to a middle tier functionality server. This |
| 사용ìžÂê° | | | | tier can perform calculations or can make |
| € | | | | requests as a client to additional servers. |
| ê°Â시ìžÂì | | | | The middle tier servers are typically coded |
| (TM) € ê° (TM) ì´ | | | | in a highly portable, non-proprietary |
| ¤보ë"Âœ, | | | | language such as C. Middle-tier functionality |
| 워ÓS¤Ã...ÂŒ | | | | servers may be multi-threaded and can be |
| ì´ì...˜ CPU ë° | | | | accessed by multiple clients, even those from |
| 주변 | | | | separate applications. |
| 장치ì (TM) € | | | | Although three-tier systems can be |
| ìƒÂظ | | | | implemented using a variety of technologies, |
| ìž'용Ã-œë‹¤ | | | | the calling mechanism from client to server |
| Ø„지 | | | | in such as system is most typically the |
| ìžÂì›Âì„ | | | | remote procedure call or RPC. Since the bulk |
| 처리Ã-œë‹ | | | | of two-tier implementations involve SQL |
| . | | | | messaging and most three-tier systems utilize |
| ôë¼ì´ì-¸ | | | | RPCs, it is reasonable to examine the merits |
| ÃS¸ | | | | of these respective request/response |
| 워ÓS¤Ã...ÂŒ | | | | mechanisms in a discussion of architectures. |
| ì´ì...˜ì˜ | | | | RPC calls from presentation client to |
| ì¤'ìš"Ã-Âœ | | | | middle-tier server provide greater overall |
| 성분ì˜ | | | | system flexibility than the SQL calls made by |
| Ã-œê°œëS" | | | | clients in the two-tier architecture. This is |
| 그래Ã"½ | | | | because in an RPC, the requesting client |
| 사용잠| | | | simply passes parameters needed for the |
| ì¸Ä°ÃŽ˜ì | | | | request and specifies a data structure to |
| ´ìS¤ (GUI)ì´다. | | | | accept returned values (if any). Unlike most |
| ì¼반ì | | | | two-tier implementations, the three-tier |
| Â으로 | | | | presentation client is not required to |
| 운옠| | | | "speak" SQL. As such, the organization, |
| 체계ì˜ | | | | names, or even the overall structure of the |
| 부분ì€ i.e | | | | back-end data can be changed without |
| ì°½ 매니ì | | | | requiring changes to PC-based presentation |
| € 사용잠| | | | clients. Since SQL is no longer required, |
| ì-¡ì...˜ì„ | | | | data can be organized hierarchically, |
| 검출Ã-˜ê³ , | | | | relationally, or in object format. This added |
| ì „ì‹œì- | | | | flexibility can allow a firm to access legacy |
| ì°½ì„ | | | | data and simplifies the introduction of new |
| 처리Ã-˜ê³ | | | | database technologies. |
| ì°½ì- ìžˆëS" | | | | |
| ìžÂ료를 | | | | Figure 3 - Three-Tier Architecture. |
| Ã'œì‹œÃ-œë‹¤. | | | | Functionality servers handle most of the |
| | | | logic processing. Middle-tier code can be |
| 서버 | | | | accessed and utilized by multiple clients |
| Ã"„로세ìS¤: | | | | In addition to the |
| - 서버 | | | | openness stated above, several other |
| Ã"„로세ìS¤ | | | | advantages are presented by this |
| (Ã"„로그랠| | | | architecture. Having separate software |
| ¨)ëS" ìš"구ëÂÂœ | | | | entities can allow for the parallel |
| ì-...무를 | | | | development of individual tiers by |
| ì´Ã-‰Ã-´ì„œ | | | | application specialists. It should be noted |
| ôë¼ì´ì-¸ | | | | that the skill sets required to develop c/s |
| ÃS¸ ìš"ì²Âì„ | | | | applications differ significantly from those |
| 성취Ã-œë‹ | | | | needed to develop mainframe-based character |
| ¤. 서버 | | | | systems. As examples, user interface creation |
| Ã"„로그랠| | | | requires an appreciation for platform and |
| ì€ | | | | corporate UI standards and database design |
| ôë¼ì´ì-¸ | | | | requires a commitment to and understanding of |
| ÃS¸ | | | | the enterprise's data model. Having experts |
| Ã"„로그랠| | | | focus on each of these three layers can |
| ì-Â서 | | | | increase the overall quality of the final |
| ì¼반ì | | | | application. The |
| Â으로 | | | | three-tier architecture also provides for |
| ìš"구를, | | | | more flexible resource allocation. |
| 수Ã-‰Ã-œë‹¤ | | | | Middle-tier functionality servers are highly |
| ë°ì´Ã€ë² | | | | portable and can be dynamically allocated and |
| ì´ìS¤ | | | | shifted as the needs of the organization |
| 복구를 | | | | change. Network traffic can potentially be |
| ë°›ê³ ê°±ì‹ | | | | reduced by having functionality servers strip |
| ì€, | | | | data to the precise structure required before |
| ôë¼ì´ì-¸ | | | | distributing it to individual clients at the |
| ÃS¸ ìš"ì²Âì- | | | | LAN level. Multiple server requests and |
| ë°ì´Ã€ | | | | complex data access can emanate from the |
| ë¬´ê²°ì„±ê³ | | | | middle tier instead of the client, further |
| ¼ ÃŒŒê²¬ | | | | decreasing traffic. Also, since PC clients |
| ìÂ'답ì„ | | | | are now dedicated to just presentation, |
| 처리Ã-œë‹ | | | | memory and disk storage requirements for PCs |
| . ë-Œë-Œë¡œ | | | | will potentially be reduced. |
| 서버 | | | | Modularly designed middle tier code |
| Ã"„로그랠| | | | modules can be re-used by several |
| ì€ ì¼반 ì | | | | applications. Reusable logic can reduce |
| ÂìÂ´ê³ | | | | subsequent development efforts, minimize the |
| 복잡Ã-Âœ | | | | maintenance workload, and decrease migration |
| 비즈니ìS | | | | costs when switching client applications. In |
| ¤ 로ì§Âì„ | | | | addition, implementation platforms for three |
| 수Ã-‰Ã-œë‹¤. | | | | tier systems such as OSF/DCE offer a variety |
| 서버 | | | | of additional features to support distributed |
| 근거Ã-Âœ | | | | application development. These include |
| ê³¼ì -ì€ | | | | integrated security, directory and naming |
| 달릴지ë | | | | services, server monitoring and boot |
| „ | | | | capabilities for supporting dynamic |
| "네ÃS¸ì›ŒÃ | | | | fault-tolerance, and distributed time |
| ¬Ã¬- ë‹¤ë¥¸ | | | | management for synchronizing systems across |
| 기계ì- | | | | networks and separate time zones. |
| 모른다". | | | | There are of course drawbacks |
| ì´ 서버ëS" | | | | associated with a three-tier architecture. |
| 주ì¸ | | | | Current tools are relatively immature and |
| 운옠| | | | require more complex 3GLs for middle tier |
| 체계 ë˜ÂëS" | | | | server generation. Many tools have |
| 네ÃS¸ì›ŒÃ | | | | under-developed facilities for maintaining |
| ¬ ÃŒŒì¼ | | | | server libraries - a potential obstacle for |
| 서버ì¼ | | | | simplifying maintenance and promoting code |
| 수 | | | | re-use throughout an IS organization. More |
| 있ì-ˆë‹¤; | | | | code in more places also increases the |
| 서버ëS" ê·¸ | | | | likelihood that a system failure will effect |
| ë-ÂŒ ì œê³µÃ-Âœ | | | | an application so detailed planning with an |
| ë'˜ 다 | | | | emphasis on the reduction/elimination of |
| ÃŒŒì¼ | | | | critical-paths is essential. Three tiers |
| 시ìS¤Ã...Âœ | | | | brings with it an increased need for network |
| 서비ìS¤ | | | | traffic management, server load balancing, |
| ë° ì‹ ì² | | | | and fault tolerance. |
| 서비ìS¤ì | | | | For technically strong IS organizations |
| ´Ã«Â‹Â¤. ë˜ÂëS" | | | | servicing customers with rapidly changing |
| ì-´ë- Ã-Âœ | | | | environments, three tier architectures can |
| 경우ì-ÂëS", | | | | provide significant long-term gains via |
| 다른 | | | | increased responsiveness to business climate |
| ÃÂìƒÂ용 | | | | changes, code reuse, maintainability, and |
| 기계ëS" ì‹ | | | | ease of migration to new server platforms and |
| ì² | | | | development environments. |
| 서비ìS¤ë¥ | | | | |
| ¼ ì | | | | Comparing two and three tire development |
| œê³µÃ-œë‹¤. | | | | efforts:- The graphs in |
| 서버 | | | | Figures 4-6 illustrate the time to deployment |
| Ã"„로세ìS¤ | | | | for two tiers vs. three tier environments. |
| «S" | | | | Time to deployment is forecast in overall |
| ë°ì´Ã€ë² | | | | systems delivery time, not man-hours. |
| ì´ìS¤ | | | | According to a Deloitte & Touche study, rapid |
| ì¸쇄 | | | | application development time is cited as one |
| 기계, | | | | of the primary reasons firms chose to migrate |
| Æµì‹ | | | | to client/server architecture. As such, |
| ì-°ê²°, ë˜ÂëS" | | | | strategic planning and platform decisions |
| ë†'ì€ ê°-à (TM) | | | | require an understanding how development time |
| "Ã-˜ | | | | relates to architecture and how development |
| 가공ì-...잠| | | | time changes as an IS organization gains |
| ì (TM) € ê° (TM) ì€ | | | | experience in c/s. |
| ê³µìœ | | | | |
| ìžÂì›Âì„ | | | | Figure 4 - Initial Development Effort |
| 처리Ã-˜ëS" | | | | Figure 4 shows the initial |
| 소Ã"„ÃS¸ì›¨ | | | | development effort forecast to create |
| ì-´ | | | | comparable distributed applications using the |
| ì-"진으로 | | | | common two tier and three tier approaches |
| ìž'ë (TM) | | | | discussed above. The three tier application |
| Ã-œë‹¤. | | | | takes much longer to develop - this is due |
| 서버 | | | | primarily to the complexity involved in |
| Ã"„로세ìS¤ | | | | coding the bulk of the application logic in a |
| «S" ìœ 사Ã-Âœ | | | | lower-level 3GL such as C and the |
| ì‹ ì²Âì- | | | | difficulties associated with coordinating |
| ì¼반ì Âì¸ | | | | multiple independent software modules on |
| Û„부 | | | | disparate platforms. In contrast, the |
| ì-...무를 | | | | two-tier scheme allows the bulk of the |
| ì´Ã-‰Ã-œë‹¤. | | | | application logic to be developed in a |
| | | | higher-level language within the same tool |
| 계산Ã-˜ëS" | | | | used to create the user interface. |
| ôë¼ì´ì-¸ | | | | |
| ÃS¸ 서버: - | | | | Figure 5 - Subsequent Development Efforts |
| | | | Subsequent development efforts |
| • 단 | | | | may see three-tier applications deployed with |
| Ã-˜ë‚˜ | | | | greater speed than two tier systems (Figure |
| ôë¼ì´ì-¸ | | | | 5). This is entirely due to the amount of |
| ÃS¸, 단 | | | | middle-tier code, which can be re-used from |
| Ã-˜ë‚˜ | | | | previous applications. The speed advantage |
| 서버 | | | | favoring the three-tier architecture will |
| | | | only result if the three-tier application is |
| • 다수 | | | | able to use a sizable portion of existing |
| ôë¼ì´ì-¸ | | | | logic. Experience indicates that these |
| ÃS¸, 단 | | | | savings can be significant, particularly in |
| Ã-˜ë‚˜ | | | | organizations, which require separate but |
| 서버 | | | | closely related applications for various |
| ôë¼ì´ì-¸ | | | | business units. Re-use is also high for |
| ÃS¸/서버 | | | | organizations with a strong enterprise data |
| ôë¼ì´ì-¸ | | | | model because data-access code can be written |
| ÃS¸/서버 | | | | once and re-used whenever similar access |
| 계산ì´ | | | | needs arise across multiple applications. The |
| 모ë"ˆë³„ | | | | degree of development time reduction on |
| Ã"„로그랠| | | | subsequent efforts will grow as an |
| ì˜ ë...¼ë¦¬ì | | | | organization deploys more c/s applications |
| Âì¸ | | | | and develops a significant library of |
| ì-°ìž¥ì¸ | | | | re-usable, middle-tier application logic. |
| 서버 | | | | |
| Ã"„로세ìS¤ | | | | Figure 6 - Client Tool Migration |
| ¬-Â서 | | | | Figure 6 makes the important case |
| 서비ìS¤ë¥ | | | | for code savings when migrating from one |
| ¼ ìš"구Ã-˜ëS" | | | | client development tool to another. It was |
| ôë¼ì´ì-¸ | | | | stated earlier that client tools are highly |
| ÃS¸ ê³¼ì -ì„ | | | | proprietary and code is not portable between |
| ìÃ-¨Ã-˜ëS" | | | | the major vendor packages. The point was also |
| ì»´Ã"¨Ã„° | | | | made that the PC tools market is highly |
| ê±´ì¶-ìˆ ì€ | | | | volatile with vendor shakeouts and technical |
| ì´다. | | | | "leapfrogging" commonplace. In a two-tier |
| 모ë"ˆë³„ | | | | environment, IS organizations wishing to move |
| Ã"„로그랠| | | | from one PC-based client development platform |
| ì€ | | | | to another will have to scrap their previous |
| 그것ì˜ | | | | investment in application logic since most of |
| 구성 | | | | this logic is written in the language of the |
| 부분 | | | | proprietary tool. In the three-tier |
| ("단위")로 | | | | environment this logic is written in a |
| 소Ã"„ÃS¸ì›¨ | | | | re-usable middle tier, thus when migrating to |
| ì-´ì˜ ð | | | | the new tool, the developer simply has to |
| ì¡°ê°Âì˜ | | | | create the presentation and add RPC calls to |
| 별거가 | | | | the functionality layer. |
| ëÂ" 쉬운 | | | | Flexibility in re-using existing middle-tier |
| 발달 밠| | | | code can also assist organizations developing |
| ëÂ" 나ì€ ìœ | | | | applications for various PC client operating |
| 지가ëS¥ì„ | | | | system platforms. Until recently there were |
| ±Ã¬Â„ 위Ã-Âœ | | | | very few cross-platform client tool |
| 가ëS¥ì„±ì | | | | development environments and most of today's |
| „ | | | | cross-platform solutions are not considered |
| 창조Ã-œã„ | | | | "best-of-breed". In a three-tier environment |
| 다ëS" | | | | separate client tools on separate platforms |
| 것ì„ | | | | can access the middle tier functionality |
| 그것ì˜ | | | | layer. Coding application logic once in an |
| 기본ì Âì¸ | | | | accessible middle tier decreases the overall |
| 가ì -으로 | | | | development time on the cross-platform |
| 있다. | | | | solution and it provides the organization |
| ôë¼ì´ì-¸ | | | | greater flexibility in choosing the best tool |
| ÃS¸/서버 | | | | on any given platform. |
| 계산ì€ | | | | |
| ê·¸ | | | | The characteristics of client/server |
| 단위가 | | | | architecture:- |
| ë (TM) ì¼Ã-Âœ | | | | |
| 기ì-µ | | | | The basic characteristics of client/server |
| 장소 | | | | architectures are: |
| 공간 ì-ˆì- | | | | |
| 모ë'Â를 | | | | 1) Combination of a client or front-end |
| 수Ã-‰ëœㄠ| | | | portion that interacts with the user, and a |
| ´Ã«Â‹Â¤Ã«S" | | | | server or back-end portion that interacts |
| 것ì„ | | | | with the shared resource. The client process |
| Ã-„ìš"로 | | | | contains solution-specific logic and provides |
| Ã-˜ì§€ | | | | the interface between the user and the rest |
| ì-SëS"다ëS" | | | | of the application system. The server process |
| 것ì„ | | | | acts as a software engine that manages shared |
| ì¸ì‹ÂÃ-´ì„ | | | | resources such as databases, printers, |
| œ | | | | modems, or high-powered processors. |
| ì´것ì-Â게 | | | | |
| 조치를 | | | | 2) The front-end task and back-end task have |
| 멀리 | | | | fundamentally different requirements for |
| ì·¨Ã-œë‹¤. | | | | computing resources such as processor speeds, |
| ì´ ê±´ì¶-ìˆ | | | | memory, disk speeds and capacities, and input |
| 로, 부르ëS" | | | | output devices. |
| 단위ëS" | | | | |
| "ôë¼ì´ì- | | | | 3) The environment is typically heterogeneous |
| ÃS¸"ì- | | | | and multiFinder. The hardware platform and |
| (서비ìS¤ë¥ | | | | operating system of client and server are not |
| ¼ ìš"구Ã-˜ëS" ì | | | | usually the same. Client and server processes |
| €ê²ƒ) | | | | communicate through a well-defined set of |
| ì-´ìš¸ë¦¬ê³ , | | | | standard application program interfaces |
| 불린 | | | | (API's) and RPC's. |
| 단위ëS" | | | | |
| "서버"가 | | | | 4) An important characteristic of |
| ëœ다 | | | | client-server systems is scalability. They |
| (서비ìS¤ë¥ | | | | can be scaled horizontally or vertically. |
| ¼ ì œê³µÃ-˜ëS") | | | | Horizontal scaling means adding or removing |
| ì €ê²ƒ. | | | | client workstations with only a slight |
| ì´것ì˜ | | | | performance impact. Vertical scaling means |
| ë...¼ë¦¬ì Âì¸ | | | | migrating to a larger and faster server |
| ì-°ìž¥ì€ | | | | machine or multiservers. |
| ê·¸ë"¤ì˜ | | | | |
| 기ëS¥ì„ | | | | Client-server applications:- |
| 위Ã-Âœ ì | | | | |
| ÂÃ-©Ã-Âœ | | | | We define a client-server application as: |
| Ã-˜ë"œì›¨ì-´ì | | | | |
| (TM) € | | | | An application system in which logically |
| 소Ã"„ÃS¸ì›¨ | | | | separate software components are |
| ì-´ Ã"Œëž˜ÃS¸à | | | | integrated together via client-server |
| (TM) ˆì- ë‹¬ë ¤ | | | | relationships. In a |
| ôë¼ì´ì-¸ | | | | client-server relationship, one part of an |
| ÃS¸ì (TM) € | | | | application (the client end) uses a service |
| 서버를 | | | | provided by the other part (the server end). |
| 비치Ã-˜ëS"ì | | | | The latter is often a shared resource, used |
| ´ë‹¤. | | | | by many clients. Although integrated together |
| 예를 | | | | via the client-server relationship, the parts |
| ë"¤ë©´, | | | | remain separate. We refer to them as being |
| 처리 | | | | logically separate because they need not be |
| ÃŒŒì¼ì„ | | | | physically remote from one another (they |
| 위Ã-Âœ | | | | might be in the same computer). |
| ÃS¹ë³„Ã-Âœ | | | | We describe client-server application |
| 성분으ë | | | | software here in three steps: splitting an |
| œ 질문, | | | | application, joining separate applications |
| ë˜ÂëS" | | | | together, and distributed application |
| Ã"Œëž˜ÃS¸à (TM) | | | | structure |
| ˆì- ë‹¬ë¦¬ëS" | | | | |
| ÃŒŒì¼ | | | | Splitting an application:- |
| 서버를 | | | | Figure 5 Application software modularity |
| 실Ã-‰Ã-˜ê¸° | | | | There are many ways of |
| 위Ã-˜ì-¬ | | | | partitioning application software into |
| ÃS¹ë³„Ã-˜ê²Œ | | | | separate components. However, the content of |
| ë""ìžÂì¸ë˜à | | | | most applications can usually be classified |
| ³ | | | | under three different technical headings: |
| Ø-성ë˜ëS" | | | | data management, application logic and |
| Ã"Œëž˜ÃS¸à (TM) | | | | presentation. This is illustrated in figure |
| ˆì- ë‹¬ë¦¬ëS" | | | | 5. If the application is to be |
| ë°ì´Ã€ë² | | | | split into two parts (one part on a client |
| ì´ìS¤ | | | | platform, the other on a server platform), |
| 관리 | | | | the split can be made at either of the two |
| 체계 | | | | boundaries between functions, or inside one |
| 서버. | | | | of the three functions. Consequently there |
| | | | are five main ways of splitting a centralized |
| 네ÃS¸ì›ŒÃ | | | | or personal application into two parts |
| ¬ 계산 | | | | between which there is a client-server |
| ê±´ì¶-ìˆ : - | | | | relationship. This is the basis of the |
| | | | popular classification into five |
| Oracleì˜ | | | | client-server styles, which is promoted by |
| 네ÃS¸ì›ŒÃ | | | | the Gartner Group. It is illustrated in |
| ¬ 계산 | | | | figure 6. |
| ê±´ì¶-ìˆ (NCA)ëS" | | | | |
| 3개ì˜ | | | | Figure 6 Five generic styles of basic |
| 개ë...Âì- | | | | client-server structure |
| ì˜Ã-´ ë¶ (TM) | | | | |
| 잡ì„ 수 | | | | The details need not concern us here. The |
| 있다: | | | | important point is that different styles suit |
| | | | different needs and circumstances: |
| 1.The ì›"ë"œ ì (TM) | | | | |
| ۓ´ë"Âœ | | | | • The two styles on the left |
| 웹ì€ ì -맠| | | | of the diagram are typical of centralized |
| ÃŽ¸ìž¬Ã-˜ëS" | | | | interactive applications that have been |
| 서비ìS¤ì | | | | adapted to client-server by means of |
| ´Ã«Â‹Â¤. | | | | graphical interface technology, terminal |
| | | | emulation, etc. |
| 2.The Java 가샠| | | | |
| 머ì‹ ì€ | | | | • The style in the middle of |
| (ë˜ÂëS" 곧 ë | | | | the diagram is typical of object-oriented |
| 것ì´다) | | | | distributed applications and distributed TP |
| 웹 | | | | applications in which data and function are |
| 브ë¼우ì | | | | encapsulated together behind application |
| € ì-ˆì-Â서 | | | | interfaces |
| 묻ÞŒ ì -맠| | | | |
| ÃŽ¸ìž¬Ã-˜ëS" | | | | • The two styles on the right |
| 서비ìS¤ì | | | | of the diagram are typical of data-centered |
| ´Ã«Â‹Â¤. | | | | applications using client-server 4GL |
| | | | development tools and relational database |
| Oracle | | | | products Some applications |
| ë°ì´Ã€ë² | | | | combine all three areas of function |
| ì´ìS¤ | | | | (presentation, application logic and data |
| ì-"진ì„ | | | | management) at the personal platform. Also, |
| 가진 ì‹ | | | | different styles may occur in combination at |
| 철납Ã'ˆ (ìœ | | | | the same platform. |
| 닉ìS¤ ð | | | | |
| 서버ì-Â), | | | | Joining applications together:- |
| ôë¼ì´ì-¸ | | | | One of the great strengths of client-server |
| ÃS¸ì- ê²½ëŸ‰ | | | | is the ability to join separate applications |
| Java ì- | | | | together. This can be done in many ways; but |
| Ã"Œë¦¬ì¼€ì | | | | upon the principles used in 2.4.1, there are |
| ì...˜, ë° ì¤'ì- | | | | essentially three levels at which |
| (TM) 층ì„ | | | | applications can interface with one another. |
| 위Ã-Âœ 3.A 3 | | | | This is illustrated in figure 7. |
| 층층 | | | | |
| 모Ø-ì€ 2 | | | | Figure 7 Three levels at which applications |
| 사ì´ | | | | can be joined together |
| 출ìž...구률| | | | |
| ¼ ì œê³µÃ-˜ê¸° | | | | The main characteristics and advantages and |
| 위Ã-˜ì-¬ | | | | disadvantages of these three approaches are: |
| 서버를 | | | | |
| "Ø-성Ã-œë‹¤ | | | | • At presentation level: |
| ". | | | | Interaction at this level is achieved via |
| | | | direct data exchange (DDE) within a window |
| OracleëS" 1998ë...„ì€ | | | | management system, or via scripting; see |
| 1ì›"ì-Â서 | | | | [Duxbury, 1994], in which software uses an |
| 릴리ìS¤ 10.7 NCA | | | | application's user interface by simulating a |
| (웹 | | | | human user. This kind of technique is often |
| 배치ëÂÂœ | | | | referred to as screen scraping. It is very |
| ì‹ ì²Â)를 | | | | useful for accessing legacy applications, but |
| 발송Ã-˜ëS" | | | | leads to software maintenance problems if the |
| 시ìž'ë˜ì-ˆà | | | | user interfaces need to change. |
| «Â‹Â¤Ã¢Â€Â¦. 2000ëS" | | | | |
| ìš"구Ã-œë‹¤ | | | | • At application function |
| | | | level: Interaction at this level is in terms |
| 방출 10.7 | | | | of business functions. Therefore, the |
| NCA로, OracleëS" | | | | inter-application requests are about the |
| ë˜'ë˜'Ã-Âœ | | | | business meanings of the application (and not |
| ôë¼ì´ì-¸ | | | | its presentation or database encoding). This |
| ÃS¸ì-Â서 | | | | has the advantage of keeping their internal |
| ê¹Â기ì˜ | | | | designs separate from their external |
| ì-´ë ¤ì›€ì- | | | | interactions. There are fewer software |
| ê³ ê° | | | | maintenance problems. |
| Ã"¼ë"œë°±ì- | | | | |
| 반ìÂ'Ã-ˆë‹¤. | | | | • At data management level: |
| 기ëS¥ì´ 10 SCì | | | | Interaction at this level is by direct access |
| (TM) € 10 NCA | | | | to the other application's database. This is |
| 사ì´ì-Â선| | | | common practice, but leads to software |
| œ ë (TM) ì¼ | | | | maintenance problems when application data |
| 있ëÂ"ë¼ë | | | | structures change. |
| , OracleëS" | | | | |
| 과립샠| | | | The first and third approaches inhibit |
| ê¹ÂëS" ì | | | | potential for change, the second does not. |
| „ëžµì- ì›¹ | | | | Further distinctions can be made between |
| 배치Ã-Âœ | | | | direct and indirect interaction between |
| 릴리ìS¤ì-Âà | | | | applications, synchronous and asynchronous |
| „œ ëÂΑ | | | | interaction, and externally programmed |
| ¤ë³´ëƒˆë‹¤. | | | | interaction and internally programmed |
| ì´ ì | | | | interaction. |
| „ëžµì€ | | | | |
| ë˜ÂÃ-Âœ | | | | Distributed application structure:- |
| ë³´ì¡´ | | | | Distributed applications are |
| ì‹ÂÃ'ˆ | | | | evolving towards richly connected network |
| 주문à (TM) | | | | structures of the kind illustrated in figure |
| "를 | | | | 8. The circles represent separate software |
| 나ì-„ì§„ë‹ | | | | components, and the lines represent |
| ¤. Ã-Âê²S | | | | client-server relationships between them. |
| ì¡°ê°Âì„ ì | | | | This is typical of the kind of structure that |
| Â용Ã-˜ê¸° | | | | results from use of object-oriented design |
| Û„ì- | | | | and distributed object management. |
| ÚŒìƒÂì´ | | | | |
| 지금 ëÂ" | | | | Figure 8 Complex distributed application |
| 쉽기 모ì-' | | | | There is also large-scale |
| 기ìˆ ì´ | | | | structure of distributed application systems |
| ì-ˆê°Âì„ | | | | (within which the individual client-server |
| 갈ì-„대긠| | | | relationships occur). Typically, three tiers |
| ° 웹 | | | | of application software can be discerned in |
| 배치Ã-˜ê¸° | | | | the large-scale structure: |
| 릴리ìS¤ì- | | | | |
| 있ëS" | | | | • Front tier: Application |
| 서버ì- | | | | software (and databases) at personal |
| ë‹¬ë¦¬ê³ | | | | platforms, providing all kinds of application |
| 기 ë-Œë¬¸ì-Â. | | | | services, using local resources and remote |
| ê¹ÂëS" ì | | | | resources. Typically, the platforms are PCs. |
| „ëžµì- ìžˆëS" | | | | This tier is where the greatest amount of |
| 다름 | | | | computer power and of new application |
| ë-Œë¬¸ì-Â, OracleëS" | | | | software is now being deployed. |
| ê³ ê° | | | | |
| 사용 | | | | • Middle tier: Application |
| ë˜'ë˜'Ã-Âœ | | | | software (and databases) at server platforms, |
| ôë¼ì´ì-¸ | | | | providing the back-end of personal |
| ÃS¸ë¥¼ ì-„ë‹ | | | | applications, shared workgroup services and |
| (TM) 니다 | | | | task-oriented services. Typically, the |
| ì¶"천Ã-˜ê³ | | | | platforms are UNIX or PC. This tier provides |
| ë (TM) ì¼Ã-Âœ | | | | rapid adaptation to business process change, |
| 경우ì- | | | | without needing changes to the back tier. It |
| 있ëS" 10.7 NCA를 | | | | puts boundaries around the turbulence and |
| Ã'ۓ-´ | | | | uncertainty generated in the volatile world |
| ë†"ëS"다. OracleëS" | | | | at the first tier, where all the users are. |
| 그런 | | | | It also provides lateral linkage across the |
| 윤곽ì„ | | | | enterprise (e.g. electronic mail services). |
| 지ì›ÂÃ-˜ì§ | | | | |
| € ì-Sì„ | | | | • Back tier: Application |
| 것ì´다. | | | | software and databases at server platforms |
| Customerncharactermode | | | | providing corporate information services. |
| 임ëª...ì€ | | | | These are usually functionally partitioned |
| 웹 | | | | (e.g. accounts, manufacturing, personnel). |
| 배치Ã-Âœ | | | | Typically, the platforms are mainframes. This |
| 릴리ìS¤ì- | | | | tier provides the core of shared and |
| ì§Âì 'ì | | | | long-lived information assets that everything |
| Â으로 | | | | else depends on. There are strong guarantees |
| ì´ë (TM) Ã-´ì-¼ | | | | of data integrity, and the applications and |
| Ã-œë‹¤ | | | | databases are stable, and their design |
| | | | changes rather slowly. |
| 장 5 | | | | |
| | | | This structure separates different kinds of |
| ôë¼ì´ì- | | | | concerns, which used to be bundled together |
| ÃS¸ 서버 | | | | in centralized computingchapter-8 |
| ê¸°ìˆ : - | | | | |
| ôë¼ì´ì-¸ | | | | Important of client server:- |
| ÃS¸ 서버 | | | | |
| 기ìˆ ì€ | | | | Advantages of Client-Server:- |
| 잘 | | | | |
| 우리가 | | | | ØPotential of reduced cost |
| 4개ì˜ | | | | |
| 지ì-Âì-Â서 | | | | ØImproved performance |
| 그것ì„ | | | | |
| Æ ë¡ Ã-˜ëS" | | | | ØIncreased security |
| 경우ì- | | | | |
| ì´Ã-´ëœ닠| | | | ØMore GUI application |
| : | | | | |
| | | | ØGives people the opportunity to make |
| 1.Personal Ã"Œëž˜ÃS¸à | | | | change for better |
| (TM) ˆ | | | | |
| | | | ØBetter SW development tools once |
| 2.Server Ã"Œëž˜ÃS¸à | | | | established |
| (TM) ˆ | | | | |
| | | | ØExploits existing H/W, S/W |
| 3.Client 서버 | | | | configurations |
| 미ë"¤ì›¨ì-´ | | | | |
| | | | ØMatches distributed business models |
| 4.Client 서버 | | | | |
| 공구ì (TM) € | | | | ØScalable |
| 서비ìS¤ | | | | |
| | | | ØFlexibility and cost saving |
| ì´ | | | | |
| 지ì-Âì˜ | | | | ØFlexibility business modeling |
| ê°Âê°Âì€ | | | | |
| ê·¸ë"¤ | | | | ØMaximum technology component choice |
| 사ì´ | | | | |
| 오버랩ì | | | | ØEfficient use of computing resources |
| ´ 있ì„ 수 | | | | |
| 있ëÂ"ë¼ë | | | | ØData interchangeability and |
| , ÃS¹ìœ Ã-˜ë‹¤. | | | | interoperatability |
| | | | |
| 기간 | | | | ØEnhanced data sharing |
| Ã"Œëž˜ÃS¸à (TM) | | | | |
| ˆì€ | | | | ØIntegrated services |
| Ã-˜ë"œì›¨ì-´ì | | | | |
| (TM) € 운옠| | | | ØSharing resources among devices |
| 체계 | | | | platforms |
| 소Ã"„ÃS¸ì›¨ | | | | |
| ì-´ì˜ ì (TM) „ì | | | | ØLocation independence data and |
| „Ã-Âœ | | | | process |
| ì¡°Ã-©ì¸ | | | | |
| ì»´Ã"¨Ã„° | | | | ØTechnology revolution |
| Ã"Œëž˜ÃS¸à (TM) | | | | |
| ˆì„ | | | | ØFuture technology |
| ì-¸ê¸‰Ã-˜ëS" | | | | |
| ì-¬ê¸°ì-Â서 | | | | ØRelational databases |
| 사용ëÂœë | | | | |
| ¤. | | | | ØDisadvantages of Client-Server:- |
| | | | |
| 개ì¸ | | | | ØHeavy up-front cost |
| Ã"Œëž˜ÃS¸à (TM) ˆ: | | | | |
| - 개ì¸ | | | | ØInitial performance decline |
| Ã"Œëž˜ÃS¸à (TM) | | | | |
| ˆì€ ì-„마 | | | | ØLack of skilled professionals |
| ôë¼ì´ì-¸ | | | | |
| ÃS¸ 서버 | | | | ØNeed of rewrite a lot of software |
| 기ìˆ ì˜ | | | | |
| 가장 ÃS¹ìœ | | | | ØNeed for retraining user |
| Ã-Âœ | | | | |
| 지ì-Âì´닠| | | | ØDependability- when the server goes |
| ¤. 우리ëS" | | | | down, operational cases |
| 개ì¸ | | | | |
| Ã"Œëž˜ÃS¸à (TM) | | | | ØLack of mature tools |
| ˆì„ | | | | |
| 다ìŒ과 | | | | ØLack of the scalability-network |
| ê° (TM) ìÂÂŒ ì | | | | operating system (e.g. novel NetWare, window |
| -ì˜Ã-œë‹¤: | | | | NT server) are not very scalable |
| | | | |
| 네ÃS¸ì›ŒÃ | | | | ØHigher then anticipated costs |
| ¬Ã¬- | | | | |
| ì-°ê²°ë˜ëS", | | | | ØHarder to build |
| ì»´Ã"¨Ã„° | | | | |
| Ã"Œëž˜ÃS¸à (TM) | | | | ØLess stable |
| ˆì€ | | | | |
| ì¼관ëÂÂœ | | | | ØSusceptible to network load |
| ì§Â관ì | | | | |
| Âì¸ | | | | ØLacking in the specialists |
| 사용잠| | | | |
| ì¸Ä°ÃŽ˜ì | | | | ØDifficult to debug |
| ´ìS¤ ë° | | | | |
| 기ì-...ì˜ | | | | ØDifficult to test |
| ëŒ€ì‹ | | | | |
| 으로 | | | | Client/Server Business Application |
| ì-...무를 | | | | Architectures: Traditional |
| 달성Ã-˜ê¸ | | | | applications architectures have been based on |
| ° 위Ã-˜ì-¬ | | | | function today, to meet the needs of the |
| 개ì¸ | | | | business an application architecture should |
| 사용잠| | | | reflect the complete range of business |
| ì›Âì¡°Ã-˜ê¸ | | | | requirements. |
| ì | | | | |
| œê³µÃ-œë‹¤. | | | | Therefore, client/server computing demands a |
| ì´ | | | | three layer view of theorganization. |
| ÃS¹ì„±ì€ | | | | |
| 숫잠| | | | 1 The user interface layer, which implements |
| 2ì-Â서 | | | | the functional model |
| 설ëª...ëÂœë‹ | | | | |
| ¤. 개ì¸ | | | | 2 The business function layer, which |
| Ã"Œëž˜ÃS¸à (TM) | | | | implements the process model |
| ˆì€ | | | | |
| 관계ë˜ | | | | 3 The data layer, which implements the |
| ì‹¸ê³ | | | | information model It |
| 굉대Ã-˜ê² | | | | should be noted that this application |
| Œ ê°-ë Â¥Ã-˜, | | | | architecture does not demand multiple |
| 공급ìžÂì | | | | hardware platforms, although such technology |
| ˜ ë„"ì€ ì„ | | | | can be utilised,if the environment is robust |
| ÃÂì´ | | | | and reliable enough and the business is |
| 있다. | | | | prepared to pay the additional costs |
| ì»´Ã"¨Ã„°ì | | | | associated with workstation and LAN |
| 많ì€ | | | | technology. |
| 다른 | | | | |
| ì¢...류ëS" | | | | Business Benefits: - There is a perceived |
| 개ì¸ | | | | need for vendor independence. This includes |
| Ã"Œëž˜ÃS¸à (TM) ˆ | | | | application development methodologies, |
| (예를ë"¤ë© | | | | programming paradigms, products and |
| MS/DOS PC, ì°½ PC, OS/2 PC, | | | | architectures. - Organization have changed |
| ìœ ë‹‰ìS¤ | | | | from steep hierarchies to flattened |
| 워ÓS¤Ã...ÂŒ | | | | hierarchies - Network management is replacing |
| ì´ì...˜, Apple | | | | vertical management - There is a change to |
| 매¨Æ | | | | team based management - The customer should |
| 시, 밠| | | | have a single point of contact for all |
| ê°Âì¢... | | | | business with the organization - |
| 소Ø- | | | | The customer should deal with the same person |
| 장치)ì¼ | | | | over multiple contacts. - The user will |
| 수 있다; | | | | perform as much processing as possible during |
| 그러나 | | | | customer contact time - The time required to |
| ì¼반ì Âì¸ | | | | complete the work will be minimized - There |
| 케ì´ìS¤ëS" | | | | is a need for empowerment of staff and audit |
| 오ëS˜ Microsoft Windows | | | | trail of actions - Multi-skilled and |
| 운옠| | | | multi-function teams need access to multiple |
| 체계를 | | | | applications |
| 가진 IBM | | | | |
| ظà (TM) ˜ìš© | | | | Different types of servers:- |
| PCì´다. | | | | The simplest form of servers are disk servers |
| 그런 | | | | and file servers. With a file server, the |
| Ã"Œëž˜ÃS¸à (TM) | | | | client passes requests for files or file |
| ˆì€ 지금 | | | | records over a network to the file server. |
| Ã-„ìš"Ã-˜ë‹¤ | | | | This form of data service requires large |
| ì-´ë""ë" 지 | | | | bandwidth and can slow a network with many |
| ë³´ÃŽ¸ì | | | | users down considerably. Traditional LAN |
| Â으로 ì | | | | computing allows users to share resources, |
| Â당Ã-˜ë‹¤. | | | | such as data files and peripheral devices, by |
| ì´것ì€ | | | | moving them from standalone PCUs onto a |
| ì»´Ã"¨Ã„° | | | | Networked File Server (NFS). |
| 시ìS¤Ã...Âœ | | | | The more advanced form of servers are |
| ì-ˆì˜ | | | | database servers, transaction server and |
| ê±´ì¶-ìˆ ì„ | | | | application servers (Orfali and Harkey 1992). |
| ë°-으로 | | | | In database servers, clients pass SQL |
| ëÂΓ-˜ë‹¤: | | | | (Structured Query Language) requests as |
| 오래ëÂÂœ | | | | messages to the server and the results of the |
| 초ì Âì€ | | | | query are returned over the network. The code |
| 그것 | | | | that processes the SQL request and the data |
| 사용ìžÂì- | | | | resides on the server allowing it to use its |
| 게서 | | | | own processing power to find the requested |
| 멀ì-ˆë˜ | | | | data, rather than pass all the records back |
| ì¤'ì- (TM) | | | | to a client and let it find its own |
| 기계ì- | | | | |
| 있ëS" | | | | Data as was the case for the file server. In |
| 부족Ã-Âœ | | | | transaction servers, clients invoke remote |
| ìžÂ웠| | | | procedures that reside on servers, which also |
| ì´ì-ˆë‹¤; | | | | contain an SQL database engine. There are |
| 새로운 | | | | procedural statements on the server to |
| 초ì Âì€ | | | | execute a group of SQL statements |
| 갠단ëÂ... | | | | (transactions), which either all succeed or |
| 사용ì˜ | | | | fail as a unit. The applications based on |
| ì†Â가ë½ | | | | transaction servers are called On-line |
| ëÂÂì- | | | | Transaction Processing (OLTP) and tend to be |
| 지금 | | | | mission-critical applications, which require |
| Ã'Â부Ã-Âœ | | | | 1-3 second response time, 100% of the time |
| 개ì¸ | | | | and require tight controls over the security |
| ìžÂì›Âì´ë | | | | and integrity of the database. The |
| ¤. PC 가격 | | | | communication overhead in this approach is |
| 성ëS¥ | | | | kept to a minimum as the exchange typically |
| 비율ì´ì | | | | consists of a single request/reply (as |
| ˜ ë˜ÂëS" ì´ë | | | | opposed to multiple SQL statements in |
| ‡ê²Œ ìš"ì¸ | | | | database servers). Application servers are |
| 2개ì˜ 매 18 | | | | not necessarily database centered but are |
| 달ì- | | | | used to server user needs, such as. |
| ì˜Ã-˜ì-¬ | | | | |
| Ã-¥ìƒÂÃ-˜ê¸° | | | | Download capabilities from Dow Jones or |
| 것ì„ | | | | regulating a electronic mail process. Basing |
| 계ì†ÂÃ-˜ê¸ | | | | resources on a server allows users to share |
| ° ë-Œë¬¸ì-Â, | | | | data, while security and management services, |
| ì´ ë (TM) | | | | which are also based in the server, ensure |
| Ã-¥ì-ÂëS" | | | | data integrity and security. |
| 계솠| | | | |
| ì¦Â가Ã-˜ëS" | | | | Special types of Architecture: IBM's System |
| Þ˜ì´ | | | | Application Architecture: |
| 있다. 초ì | | | | SAA is a collection of selected software |
| Âì˜ ì´ | | | | interfaces, conventions, and protocols that |
| 변à (TM) "ëS" | | | | are used as a framework for developing |
| 사ì-... | | | | consistent, integrated applications across |
| 구조ì- | | | | the major IBM computing environments. |
| 있ëS" 변à (TM) | | | | |
| "를 | | | | Four major components of this architecture |
| 맞춘다: | | | | are: - Common User Access (CUA) defines |
| 조짠| | | | conventions for GUI look and feel. - Common |
| 서ì-´ì€ | | | | Programming Interface (CPI) provides |
| ÉÉÃ-˜ê² | | | | languages, tools, and APIs that give |
| Œ Ã-˜ê³ | | | | |
| 있다, ì -ì±... | | | | applications |
| ìž...ì-ˆ | | | | greater portability and more consistent user |
| 권위ëS" | | | | interfaces across multiple platforms. - |
| ì-'ë„ëÂ˜ê³ | | | | Common Communication Support (CCS) supports |
| 있다, | | | | existing communications standards, such as LU |
| ê·¸ë¦¬ê³ | | | | 6.2. - Common Applications, written by IBM, |
| 그것 | | | | will serve as demonstrations of SAA concepts |
| 가ëSÂ¥Ã-˜ê²Œ | | | | and make it easy for users to migrate between |
| ëÂÂœ ê³¼ì -ì€ | | | | systems. |
| 지금 | | | | |