❓
물음표살인마 블로그
  • README
  • ALGORITHM
    • Sieve of Eratosthenes
    • Round Up
    • Binary Search
    • Union Find
    • Sorting Array
    • Lcm, Gcd
  • TechTalk Review
    • Template
  • Books
    • CS Note for Interview
      • Ch1. Design Pattern & Programming paradigm
        • 1.1.1 Singleton Pattern
        • 1.1.2 Factory Pattern
        • 1.1.4 Observer Pattern
        • 1.1.5 Proxty Pattern & Proxy Server
        • 1.1.8 Model-View-Controller Pattern
        • 1.2.1 Declarative and Functional Programming
        • 1.2.2 Object Oriented Programming
      • Ch2. Network
        • 2.2.1 TCP/IP Four-Layer Model
        • 2.2.1-1 TCP 3, 4 way handshake
        • 2.3 Network Devices L4, L7
        • 2.4.1 ARP, RARP
        • 2.4.2 Hop By Hop Communication
        • 2.4.3 IP Addressing Scheme
      • Ch3. Operating System
        • 3.1.1 Roles and Structure of Operating Systems
        • 3.2.1 Memory Hierarchy
        • 3.2.2 Memory Management
        • 3.3.1 Processes and Compilation Process
        • 3.3.3 Memory Structure of a Process
        • 3.3.4 Process Control Block (PCB)
        • 3.3.5 Multiprocessing
        • 3.3.6 Threads and Multithreading
        • 3.3.7 Shared Resources and Critical Sections
        • 3.3.8 Deadlock
        • 3.4 CPU Scheduling Algorithm
      • Ch4. Database
        • 4.1 Database Basic
        • 4.2 Normalization
        • 4.3 Transaction and Integrity
        • 4.4 Types of Databases
        • 4.5 Indexes
        • 4.6 Types of Joins
        • 4.7 Principles of Joins
      • Ch5. Data Structure
    • Learning the Basics of Large-Scale System Design through Virtual Interview Cases
      • 1. Scalability based on user counts(1/2)
      • 1. Scalability based on user counts(2/2)
      • 2.Back-of-the-envelope estimation
      • 3. Strategies for System Design Interviews
      • 4. Rate Limiter
      • 5. Consistent Hashing
      • 6. Key-Value System Design
      • 7. Designing a Unique ID Generator for Distributed Systems
      • 8. Designing a URL Shortener
      • 9. Designing a Web Crawler
      • 10. Notification System Design
      • 11. Designing a News Feed System
      • 12. Chat System Design
      • 13. AutoComplete
      • 14. Design YouTube
      • 15. Design Google Drive
      • Loadbalancer Algorithms
      • Cache tier
      • CDN, Content Delivery Network
      • Stateless Web tier
    • Computer System A programmer's perspective
    • Effective Java
      • Item 1. Consider Static Factory Methods Instead of Constructors
      • Item 2. Consider a Builder When Faced with Many Constructor Parameters
      • Item 3. Ensure Singleton with Private Constructor or Enum Type
      • Item 4. Enforce Noninstantiability with a Private Constructor
      • Item 5. Prefer Dependency Injection to Hardwiring Resources
      • Item 6. Avoid Creating Unnecessary Objects
      • Item 7. Eliminate Obsolete Object References
      • Item 8. Avoid Finalizers and Cleaners
      • Item 9.Prefer try-with-resources to try-finally
      • Item10. Adhering to General Rules When Overriding equals
        • Handling Transitivity Issues
        • Ensuring Consistency
      • Item11. Override hashCode When You Override equals
      • Item12. Always Override toString
        • Always Override toString
      • Item13. Override Clone Judiciously
      • Item14. Consider Implementing Comparable
      • Item15. Minimize the Accessibility of Classes and Members
      • Item16. Accessor Methods Over Public Fields
      • Item17. Minimize Mutability
      • Item18. Composition over inherentance
      • Item19. Design and Document for Inheritance, or Else Prohibit It
      • Item20. Prefer Interfaces to Abstract Classes
      • Item21. Design Interfaces with Implementations in Mind
      • Item22. Use Interfaces Only to define Types
      • Item23. Prefer Class Hierarchies to Tagged Classes
      • Item24. Favor Static Member Classes Over Non-Static
      • Item28. Use Lists Instead of Arrays
      • Item29. Prefer Generic Types
      • Item30. Favor Generic Methods
    • Head First Design Patterns
      • Ch1. Strategy Pattern
      • Ch2. Observer Pattern
        • Ver1. Ch2. Observer Pattern
      • Ch3. Decorator Pattern
        • Ch3. Decorator Pattern
      • Ch4. Factory Pattern
      • Ch5. Singleton Pattern
      • Ch6. Command Pattern
      • Ch7. Adapter and Facade Pattern
      • Ch8. Template Method Pattern
    • Digging Deep into JVM
      • Chapter 2. Java Memory Area & Memory Overflow
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (1/2)
      • Chapter 3. Garbage Collector & Memory Allocation Strategy (2/2)
      • Chapter 5. Optimization Practice
      • Chapter 6. Class file structure
      • Chapter 8. Bytecode Executor Engine (1/2)
  • Interview Practices
    • Restful API Practices
      • Url Shortener API
      • Event Ticket Reservation API
      • Course Management API
      • Search posts by tags API
      • Online Code platform API
      • Simple Task Management API
      • Event Participation API
      • Review System API
      • Car management API
      • Online Library
    • Tech Review
      • if(kakao)
        • Kakao Account Cache Migration / if(kakao)2022
        • Improving the Anomaly Detection System for KakaoTalk Messaging Metrics / if(kakao) 2022
        • Standardizing API Case Handling Without Redeployment / if(kakaoAI)2024
        • JVM warm up / if(kakao)2022
    • Naver Computer Science
      • Process & Thread
      • TCP & UDP
      • Spring & Servlet
      • Filter & Interceptor & AOP
      • Equals() & ==
      • Dependency Injection
      • Object Oriented Programming
  • F-Lab
    • Week1
      • Client & Server
      • HTTP
      • TCP/UDP
      • REST API
      • Questions
        • Object Oriented Programming
        • HTTP
        • Process & Thread
        • Data Structure
    • Week2
      • OSI 7 layer
      • Web vs WAS
    • Week3
      • RDB vs NoSQL
      • RDB Index
      • Cache
      • Redis
      • Messaging Queue
    • Week4
      • Project - Ecommerce
    • Week5
      • ERD - 1
    • Week6
      • Ecommerce - 2
      • Role
      • pw hashing && Salt
      • CreatedAt, ModifiedAt
      • JWT
      • Copy of ERD - 1
    • Week7
      • Vault (HashiCorp Vault)
    • Week 8
      • Api Endpoints
    • Week10
      • Product Create Workflow
  • TOY Project
    • CodeMentor
      • Implementation of Kafka
      • Project Improvement (Architectural Enhancements)
      • Communication between servers in msa
  • JAVA
    • MESI protocol in CAS
    • CAS (Compare and Set)
    • BlockingQueue
    • Producer & Consumer
    • Synchronized && ReentrantLock
    • Memory Visibility
    • Checked vs Unchecked Exception
    • Thread
    • Batch delete instead of Cascade
    • Java Questions
      • Week 1(1/2) - Basic Java
      • Week 1(2/2) - OOP
      • Week 2(1/2) - String, Exception, Generic
      • Week2(2/2) Lambda, Stream, Annotation, Reflection
      • Week3(1/2) Collections
      • Week3(2/2) Threads
      • Week4 Java Concurrency Programming
      • Week5 JVM & GC
    • Java 101
      • JVM Structure
      • Java Compiles and Execution Method
      • Override, Overload
      • Interface vs Abstract Class
      • Primitive vs Object Type
      • Identity and equality
      • String, StringBuilder, StringBuffer
      • Checked Exceptions and Unchecked Exceptions
      • Java 8 methods
      • Try-with-reources
      • Strong Coupling and Loose Coupling
      • Serialization and Deserialization
      • Concurrency Programming in Java
      • Mutable vs Immutable
      • JDK vs JRE
  • SPRING
    • DIP. Dependency Inversion Principal
    • Ioc container, di practice
    • @Transactional
    • Proxy Pattern
    • Strategy Pattern
    • Template Method Pattern
    • using profile name as variable
    • Spring Questions
      • Spring Framework
      • Spring MVC & Web Request
      • AOP (Aspect-Oriented Programming)
      • Spring Boot
      • ORM & Data Access
      • Security
      • ETC
  • DATABASE
    • Enhancing Query Performance & Stability - User list
    • Ensuring Data Consistency, Atomicity and UX Optimization (feat.Firebase)
    • Redis: Remote Dictionary Server
    • Database Questions
      • Week1 DBMS, RDBMS basics
      • Week2 SQL
      • Week3 Index
      • Week4 Anomaly, Functional Dependency, Normalization
      • Week5 DB Transaction, Recovery
    • Normalization
      • 1st Normal Form
      • 2nd Normal Form
      • 3rd Normal Form
  • NETWORK
    • HTTP & TCP head of line blocking
    • HTTP 0.9-3.0
    • Blocking, NonBlocking and Sync, Async
    • Network Questions
      • Week1 Computer Network Basic
      • Week2(1/3) Application Layer Protocol - HTTP
      • Week2(2/3) Application Layer Protocol - HTTPS
      • Week2(3/3) Application Layer Protocol - DNS
      • Week3 Application Layer
      • Week4 Transport Layer - UDP, TCP
      • Week5 Network Layer - IP Protocol
    • Network 101
      • https://www.google.com
      • TCP vs UDP
      • Http vs Https
      • TLS Handshake 1.2
      • HTTP Method
      • CORS & SOP
      • Web Server Software
  • OS
    • Operating System Questions
      • Week1 OS & How Computer Systems Work
      • Week2(1/2) Process
      • Week2(2/2) Thread
      • Week3 CPU Scheduling
      • Week4 Process Synchronize
      • Week5 Virtual Memory
    • Operating System 101
      • Operating system
        • The role of the operating system
        • The composition of the operating system.
      • Process
        • In Linux, are all processes except the initial process child processes?
        • Zombie process, orphan process
        • (Linux) Daemon process
        • Process address space
        • Where are uninitialized variables stored?
        • Determination of the size of the Stack and Heap
        • Access speed of Stack vs Heap
        • Reason for memory space partitioning
        • Process of compiling a process
        • sudo kill -9 $CURRENT_PID
      • Thread
        • Composition of a thread's address space
      • Process vs Thread
        • Creation of processes and threads in Linux
      • Multiprocessing
        • Web Browser
        • Implementation of multiprocessing
        • Application areas of multiprocessing
      • Multithreading
        • Application areas of multithreading
      • Interrupt
        • HW / SW Interrupt
        • Method of handling interrupts
        • Occurrence of two or more interrupts simultaneously
      • Polling
      • Dual Mode
        • Reason for distinguishing between user mode and kernel mode
      • System call
        • Differentiation between system calls
        • Types of system calls
        • Execution process of a system call
      • Process Control Block (PCB)
        • PCB의 구조
        • 쓰레드는 PCB를 갖고 있을까?
        • 프로세스 메모리 구조
      • Context switching
        • Timing of context switching
        • Registers saved during context switching
        • Context switching in processes
        • Context switching in threads
        • Difference between context switching in processes and threads
        • Information of the current process during context switching
      • Interprocess Communication (IPC)
        • Cases where IPC is used
        • Process address space in IPC Shared Memory technique
        • Types of IPC
  • COMPUTER SCIENCE
    • Computer Architecture 101
      • 3 components of a computer
      • RAM vs ROM
      • CPU vs GPU
      • SIMD
      • Two's complement
      • Harvard Architecture vs. von Neumann Architecture
      • The structure of a CPU.
      • Instruction cycle (CPU operation method)
      • Instruction pipelining
      • Bus
      • Memory area
      • Memory hierarchy structure
        • Reason for using memory hierarchy structure
      • Cache memory
      • L1, L2, L3 Cache
      • Locality of reference (cache)
      • Fixed-point vs Floating-point
        • epresentation of infinity and NaN (Not a Number) in floating-point
      • RISC vs CISC
      • Hamming code
      • Compiler
      • Linking
      • Compiler vs Interpreter
      • Mutex vs Semaphore
      • 32bit CPU and 64bit CPU
      • Local vs Static Variable
      • Page
  • Programming Paradigm
    • Declarative vs Imperative
  • JPA, QueryDsl
    • why fetchResults() is deprecated
  • PYTHON
    • Icecream
  • FASTAPI
    • Template Page
  • LINUX
    • Template Page
  • DATA STRUCTURE
    • Counting Sort
    • Array vs Linked List
  • GIT, Github
    • git clone, invalid path error
  • INFRA
    • Template Page
  • AWS
    • Server Log Archive Pipeline
    • Image Processing using Lambda
  • DOCKER
    • Docker and VM
    • Python Executable Environment
    • Docker commands
  • docker-compose
    • Kafka, Multi Broker
  • KUBERNATES
    • !Encountered Errors
      • my-sql restarts
      • kafka producer: disconnected
    • Kubernetes Components
    • Helm
      • Helm commands
    • Pod network
    • Service network
      • deployment.yaml
      • services.yaml
    • Service type
      • Cluster IP
      • NodePort
    • service-name-headless?
    • kube-proxy
  • GraphQL
    • Template Page
  • WEB
    • Template Page
  • Reviews
    • Graphic Intern Review
    • Kakao Brain Pathfinder Review
    • JSCODE 자바 1기 Review
  • 😁Dev Jokes
    • Image
      • Plot twist
      • Priorities
      • SQL join guide
      • Google is generous
      • Genie dislikes cloud
      • buggy bugs
      • last day of unpaid internship
      • what if clients know how to inspect
      • its just game
      • how i wrote my achievement on resume
      • self explanatory
      • chr(sum(range(ord(min(str(not))))))
Powered by GitBook
On this page
  • String: 불변(Immutable) 객체
  • String의 장점
  • String의 단점
  • StringBuilder: 가변(Mutable) 객체
  • StringBuilder의 장점
  • StringBuilder의 단점
  • StringBuffer: 가변(Mutable) 객체 + Thread-safe
  • StringBuffer의 장점
  • StringBuffer의 단점
  • 성능 비교
  • 단일 스레드 환경
  • 멀티스레드 환경
  • String Pool
  • String Pool의 장점
  • String Pool의 한계
  • intern() 메서드
  1. JAVA
  2. Java 101

String, StringBuilder, StringBuffer

String, StringBuilder, StringBuffer

String: 불변(Immutable) 객체

String은 Java에서 가장 많이 사용되는 클래스 중 하나로, 문자열을 표현하기 위해 사용됩니다. String 객체는 불변(immutable) 객체로, 생성된 후에는 그 값을 변경할 수 없습니다.

String str = "Hello";
str = str.concat(" World");

위 코드에서 str은 처음에 "Hello"를 가리키고, concat 메서드를 호출한 후에는 "Hello World"라는 새로운 문자열을 가리키게 됩니다. 원래의 "Hello" 문자열은 변경되지 않으며, 새로운 문자열 객체가 생성됩니다.

String의 장점

  • 간결함: 문자열을 다루는 기본적인 클래스이며, 간단한 문자열 조작에 적합합니다.

  • Thread-safe: String 객체는 불변이기 때문에 멀티스레드 환경에서 안전합니다.

String의 단점

  • 비효율성: 문자열 조작이 빈번한 경우, 새로운 객체가 계속 생성되어 메모리와 성능에 영향을 줄 수 있습니다.

StringBuilder: 가변(Mutable) 객체

StringBuilder는 가변(mutable) 객체로, String과 달리 동일 객체 내에서 문자열을 변경할 수 있습니다. 즉, 문자열을 추가하거나 수정할 때 새로운 객체를 생성하지 않고 기존 객체를 변경합니다.

StringBuilder sb = new StringBuilder("Hello");
sb.append(" World"); // "Hello World"
sb.insert(5, ","); // "Hello, World"
sb.delete(5, 6); // "Hello World"
sb.reverse(); // "dlroW olleH"

위 코드에서는 StringBuilder 객체가 생성되고, append 메서드를 통해 " World"가 추가됩니다. 이 과정에서 새로운 객체가 생성되지 않고, 기존 StringBuilder 객체의 값이 변경됩니다.

StringBuilder의 장점

  • 성능: 문자열을 자주 변경해야 하는 경우, StringBuilder는 새로운 객체를 생성하지 않으므로 메모리 사용과 성능 면에서 유리합니다.

  • 간결성: String처럼 여러 메서드를 체인으로 연결할 수 있어, 코드가 간결해집니다.

StringBuilder의 단점

  • Thread-unsafe: StringBuilder는 동기화를 제공하지 않으므로, 멀티스레드 환경에서는 안전하지 않습니다.

StringBuffer: 가변(Mutable) 객체 + Thread-safe

tringBuffer는 StringBuilder와 매우 유사하지만, 멀티스레드 환경에서 안전한(Thread-safe) 가변 객체입니다. StringBuilder와 동일하게 문자열을 변경할 수 있지만, 동기화가 추가되어 여러 스레드가 동시에 접근할 경우에도 안전합니다.

StringBuffer sbf = new StringBuffer("Hello");
sbf.append(" World");

위 코드에서 StringBuffer는 StringBuilder와 유사한 방식으로 동작하지만, 멀티스레드 환경에서 안전하게 사용할 수 있습니다.

StringBuffer의 장점

  • Thread-safe: 동기화가 적용되어 멀티스레드 환경에서 안전하게 사용할 수 있습니다.

  • 가변성: StringBuilder처럼 동일 객체 내에서 문자열을 변경할 수 있어, 성능이 우수합니다.

StringBuffer의 단점

  • 성능 저하: 동기화로 인해 StringBuilder보다 성능이 약간 떨어질 수 있습니다. 그러나 멀티스레드 환경에서의 안전성을 보장해야 할 때는 이 성능 저하를 감수할 가치가 있습니다.

성능 비교

단일 스레드 환경

단일 스레드 환경에서는 StringBuilder가 StringBuffer보다 성능이 뛰어납니다. 동기화가 필요 없기 때문에 불필요한 오버헤드가 발생하지 않기 때문입니다.

StringBuilder sb = new StringBuilder();
for (int i = 0; i < 10000; i++) {
    sb.append("a");
}

위와 같은 반복문에서 StringBuilder를 사용하면 String을 사용할 때보다 훨씬 빠른 성능을 얻을 수 있습니다.

멀티스레드 환경

멀티스레드 환경에서는 StringBuffer를 사용하는 것이 안전합니다. 여러 스레드가 동시에 문자열을 수정할 수 있는 상황에서는 동기화가 되어 있는 StringBuffer를 사용해야 합니다.

StringBuffer sbf = new StringBuffer();
Runnable task = () -> {
    for (int i = 0; i < 1000; i++) {
        sbf.append("a");
    }
};

Thread thread1 = new Thread(task);
Thread thread2 = new Thread(task);

thread1.start();
thread2.start();

이 경우, StringBuffer는 동기화를 통해 안전하게 문자열을 수정할 수 있습니다.

String Pool

ava에서 String은 불변(immutable) 객체이기 때문에, 동일한 문자열을 여러 번 사용하더라도 메모리 낭비를 줄이기 위해 String Pool이라는 메커니즘을 사용합니다. String Pool은 JVM의 Heap 영역에 있는 특별한 공간으로, 동일한 문자열 리터럴을 관리합니다.

String str1 = "Hello";
String str2 = "Hello";

위 코드에서 str1과 str2는 동일한 "Hello" 문자열을 참조합니다. 이 문자열은 String Pool에 한 번만 생성되고, 이후 같은 리터럴을 사용할 때는 동일한 참조를 반환합니다.

String Pool의 장점

  • 메모리 절약: 동일한 문자열 리터럴이 여러 번 생성되는 것을 방지하여 메모리 사용을 최적화합니다.

  • 성능 향상: 이미 생성된 문자열을 재사용함으로써 성능이 향상됩니다.

String Pool의 한계

  • 동적 문자열 생성: new 키워드를 사용해 String 객체를 생성하면 String Pool에 저장되지 않습니다.

String str3 = new String("Hello");

위 코드에서 str3은 new를 사용해 생성되었기 때문에, String Pool과는 별도로 Heap에 새로운 String 객체가 생성됩니다.

intern() 메서드

intern() 메서드를 사용하면 동적으로 생성된 String을 String Pool에 추가할 수 있습니다. 만약 String Pool에 이미 동일한 문자열이 존재한다면, 해당 문자열의 참조를 반환합니다.

String str4 = new String("World").intern();
String str5 = "World";
System.out.println(str4 == str5); // true

위 코드에서 str4는 intern()을 사용하여 String Pool에 저장된 "World" 문자열을 참조하게 됩니다.

PreviousIdentity and equalityNextChecked Exceptions and Unchecked Exceptions

Last updated 9 months ago