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