Skip to main content

String & StringBuffer & StringBuilder


**** String ****

-> String is immutable  ( once created can not be changed )object.
   The object created as a String is stored in the  Constant String Pool  .
   Every immutable object in Java is thread safe ,that implies String is also thread safe .
   String can not be used by two threads simultaneously.
   String  once assigned can not be changed.


**** StringBuffer  ***

-> StringBuffer is mutable means one can change the value of the object .
   The object created through StringBuffer is stored in the heap .
   StringBuffer  has the same methods as the StringBuilder ,
   but each method in StringBuffer is synchronized that is StringBuffer is thread safe .

****** StringBuilder ****

-> StringBuilder  is same as the StringBuffer ,
   that is it stores the object in heap and it can also be modified .
   The main difference between the StringBuffer and StringBuilder is that StringBuilder is also not thread safe.
   StringBuilder is fast as it is not thread safe . 

Comments

Post a Comment

Popular posts from this blog

Mockito interview Questions

1.       Question 1. What Is Mockito? Answer : Mockito allows creation of mock object for the purpose of Test Driven Development and Behavior Driven development. Unlike creating actual object, Mockito allows creation of fake object (external dependencies) which allows it to give consistent results to a given invocation. 2.       Question 2. Why Do We Need Mockito? What Are The Advantages? Answer : Mockito differentiates itself from the other testing framework by removing the expectation beforehand. So, by doing this, it reduces the coupling. Most of the testing framework works on the "expect-run-verify". Mockito allows it to make it "run-verify" framework. Mockito also provides annotation which allows to reduce the boilerplate code. 3.       Question 3. Can You Explain A Mockito Framework? Answer : In Mockito, you always check a particular class. The dependency in that class is injected using m...
2 comments
Read more

REST Methods

GET ============================================= HTTP GET method is used to **read** (or retrieve) a representation of a resource. According to the design of the HTTP specification, GET requests are used only to read data and not change it. Therefore, when used this way, they are considered safe. That is, they can be called without risk of data modification or corruption. Means calling it once has the same effect as calling it 10 times. Additionally, GET is idempotent which means that making multiple identical requests ends up having the same result as a single request. Donot expose unsafe operations via GET. It should never modify any resources on the server. Example: ------------    GET http://www.example.com/customers/12345/orders POST =================================== -> The POST verb is most-often utilized to **create** new resources. In particular, it's used to create subordinate resources. -> That is, subordinate to some other (e.g. parent) reso...
Post a Comment
Read more