Getters and setters are often criticized as being not proper OO. On the other hand, most OO code I've seen has extensive getters and setters.

When are getters and setters justified? Do you try to avoid using them? Are they overused in general?

If your favorite language has properties (mine does) then such things are also considered getters and setters for this question. They are the same thing from an OO methodology perspective. They just have nicer syntax.

Sources for Getter/Setter Criticism (some taken from comments to give them better visibility):

To state the criticism simply: Getters and Setters allow you to manipulate the internal state of objects from outside of the object. This violates encapsulation. Only the object itself should care about its internal state.

And an example
Procedural version of code:

struct Fridge
    int cheese;

void go_shopping(Fridge fridge)
     fridge.cheese += 5;

Mutator version of code:

class Fridge
     int cheese;
     void set_cheese(int _cheese) { cheese = _cheese; }
     int get_cheese() { return cheese; }

void go_shopping(Fridge fridge)
     fridge.set_cheese(fridge.get_cheese() + 5);        

The getters and setters made the code much more complicated without affording proper encapsulation. Because the internal state is accessible to other objects we don't gain a whole lot by adding these getters and setters.

The question has been previously discussed on Stack Overflow:

  • 24
    Getters and setters are often criticized as being not proper OO - Citation, please. Nov 26, 2010 at 22:43
  • 37
  • 46
    @Job, why because it has code? It's a good question and reeks of holy war if taken seriously. Nov 26, 2010 at 23:55
  • 4
    @Winston Ewert: "... the question is if you should be accessing the data inside the class at all.": well, noone forces you to implement getters and setters for all member variables, you only implement those you need. That's why you use getters and setters instead of public member variables.
    – Giorgio
    Nov 19, 2011 at 14:07
  • 3
    @Winston Ewert: I do not see how the absence of getters / setters would solve this problem: there must be a way to access every piece of data otherwise it is useless; it is the task of a good design to decide which part of the data is accessible to which part of the code. If one is a bad designer he or she will be such with or without getters and setters. Just my 2 cents.
    – Giorgio
    Nov 19, 2011 at 16:55

13 Answers 13


Having getters and setters does not in itself break encapsulation. What does break encapsulation is automatically adding a getter and a setter for every data member (every field, in java lingo), without giving it any thought. While this is better than making all data members public, it is only a small step away.

The point of encapsulation is not that you should not be able to know or to change the object's state from outside the object, but that you should have a reasonable policy for doing it.

  • Some data members may be entirely internal to the object, and should have neither getters nor setters.

  • Some data members should be read-only, so they may need getters but not setters.

  • Some data members may need to be kept consistent with each other. In such a case you would not provide a setter for each one, but a single method for setting them at the same time, so that you can check the values for consistency.

  • Some data members may only need to be changed in a certain way, such as incremented or decremented by a fixed amount. In this case, you would provide an increment() and/or decrement() method, rather than a setter.

  • Yet others may actually need to be read-write, and would have both a getter and a setter.

Consider an example of a class Person. Let's say a person has a name, a social security number, and an age. Let's say that we do not allow people to ever change their names or social security numbers. However, the person's age should be incremented by 1 every year. In this case, you would provide a constructor that would initialize the name and the SSN to the given values, and which would initialize the age to 0. You would also provide a method incrementAge(), which would increase the age by 1. You would also provide getters for all three. No setters are required in this case.

In this design you allow the state of the object to be inspected from outside the class, and you allow it to be changed from outside the class. However, you do not allow the state to be changed arbitrarily. There is a policy, which effectively states that the name and the SSN cannot be changed at all, and that the age can be incremented by 1 year at a time.

Now let's say a person also has a salary. And people can change jobs at will, which means their salary will also change. To model this situation we have no other way but to provide a setSalary() method! Allowing the salary to be changed at will is a perfectly reasonable policy in this case.

By the way, in your example, I would give the class Fridge the putCheese() and takeCheese() methods, instead of get_cheese() and set_cheese(). Then you would still have encapsulation.

public class Fridge {
  private List objects;
  private Date warranty;

  /** How the warranty is stored internally is a detail. */
  public Fridge( Date warranty ) {
    // The Fridge can set its internal warranty, but it is not re-exposed.
    setWarranty( warranty );

  /** Doesn't expose how the fridge knows it is empty. */
  public boolean isEmpty() {
    return getObjects().isEmpty();

  /** When the fridge has no more room... */
  public boolean isFull() {

  /** Answers whether the given object will fit. */
  public boolean canStore( Object o ) {
    boolean result = false;

    // Clients may not ask how much room remains in the fridge.
    if( o instanceof PhysicalObject ) {
      PhysicalObject po = (PhysicalObject)o;

      // How the fridge determines its remaining usable volume is a detail.
      // How a physical object determines whether it fits within a specified
      // volume is also a detail.
      result = po.isEnclosedBy( getUsableVolume() );

     return result;

  /** Doesn't expose how the fridge knows its warranty has expired. */
  public boolean isPastWarranty() {
    return getWarranty().before( new Date() );

  /** Doesn't expose how objects are stored in the fridge. */
  public synchronized void store( Object o ) {
    validateExpiration( o );

    // Can the object fit?
    if( canStore( o ) ) {
      getObjects().add( o );
    else {
      throw FridgeFullException( o );

  /** Doesn't expose how objects are removed from the fridge. */
  public synchronized void remove( Object o ) {
    if( !getObjects().contains( o ) ) {
      throw new ObjectNotFoundException( o );

    getObjects().remove( o );

    validateExpiration( o );

  /** Lazily initialized list, an implementation detail. */
  private synchronized List getObjects() {
    if( this.list == null ) { this.list = new List(); }
    return this.list;

  /** How object expiration is determined is also a detail. */
  private void validateExpiration( Object o ) {
    // Objects can answer whether they have gone past a given
    // expiration date. How each object "knows" it has expired
    // is a detail. The Fridge might use a scanner and
    // items might have embedded RFID chips. It's a detail hidden
    // by proper encapsulation.
    if( o implements Expires && ((Expires)o).expiresBefore( today ) ) {
      throw new ExpiredObjectException( o );

  /** This creates a copy of the warranty for immutability purposes. */
  private void setWarranty( Date warranty ) {
    assert warranty != null;
    this.warranty = new Date( warranty.getTime() )
  • 4
    Please don't take my Fridge example too seriously. :) A real fridge ought to be a container object, I'd expect it to know how to hold objects without worrying about what exactly they were. I.E. it would be like an ArrayList. As for what makes it a Fridge, let's say it serializes objects to disk when stored so that they will survive system failure. Ok. Enough taking my fridge example over seriously. Nov 26, 2010 at 23:40
  • 6
    But shouldn't the fridge know the expiration dates, so that it can tell you that the cheese has gone bad and should be thrown out? :) Ok, we have to stop this! :)
    – Dima
    Nov 27, 2010 at 0:10
  • 10
    Quite an interesting discussion of Fridge Logic you've got going on here... Nov 27, 2010 at 6:27
  • 35
    Haha, I'd like to see the ad for that: "It's a brand new kind of fridge: It throws things at you when trying to grab something that isn't there! This way you will only try that once! You worry about stuffing the fridge, and let the fridge worry about illegal behaviour!"
    – gablin
    Nov 27, 2010 at 9:13
  • 47
    The example has it all wrong. There should not be an Age field nor a setAge() method. Age is a function of the Person birthDate as compared to some point in time. While seemingly trivial, this is exactly what is wrong with the modern practice of full mutability of objects and other bad designs, as seen by get/set methods for private fields versus carefully considering what is really mutable, what is a field, what the object should know about its behaviors and what state changes are actually valid (which setX methods completely destroy). Jul 21, 2014 at 18:49

The basic reason for getters and setters in Java is very simple:

  • You can only specify methods, not fields, in an interface.

Hence, if you want to allow a field to pass across the interface, you will need a reader and a writer method. These are traditionally called getX and setX for the field x.

  • 49
    That is a language limitation. The real question is whether we should be allowing other objects to manipulate that state. Nov 26, 2010 at 23:05
  • 3
    @Peter Turner, clearly nothing prevents a language from having interfaces that include properties. Under the covers that may well be implemented as getter/setter but it would be easy enough to add support to interface definitions for properties. Nov 26, 2010 at 23:54
  • 2
    @Winston, you will eventually need to allow classes to pass information back and forth between each other to actually get work done. What would you suggest instead?
    – user1249
    Nov 27, 2010 at 6:38
  • 6
    An object is supposed to provide a higher level interface to it innards. Getters and Setters tend to be a low level interface. For example, suppose you have a class that implements a binary tree. You could have functions like GetLeft(), GetRight(), GetValue(), and GetKey() in order to navigate the tree. But that is the completely wrong approach. Your binary tree class should provide operations like Find, Insert, Delete. Nov 27, 2010 at 14:51
  • 6
    To take another example, consider a tetris piece. The tetris piece has some internal state like block_type, rotation, position. You could have getters like GetBlockType(), GetRotation(), GetPosition(). But you really shouldn't. What you should have is a GetSquares() method which returns a list of all of the squares occupied by this piece. You also shouldn't have stuff like SetPosition() or SetRotation(). Instead, you should have operations like MoveLeft(), MoveRight(), Rotate(), Fall(). Nov 27, 2010 at 14:55

From http://www.adam-bien.com/roller/abien/entry/encapsulation_violation_with_getters_and

JavaBean style:




Well, clearly I prefer the latter approach; it doesn't bleed implementation details, it's simpler and more concise, and all of the needed information is included with the method call, so it's easier to get it right. I also prefer setting private members using parameters in the constructor, whenever possible.

Your question is, when is a getter/setter justified? Perhaps when a mode change is needed, or you need to interrogate an object for some information.

myObject.SomeCapabilitySwitch = true;

In thinking about it, when I first started coding in C#, I wrote a lot of code in the Javabeans style illustrated above. But as I gained experience in the language, I began doing more setting of members in the constructor, and using methods that looked more like the above OO style.

  • 6
    Why is the "give all arguments as parameters" OO-style?
    – user1249
    Nov 27, 2010 at 6:39
  • 6
    While your "OO-style" is fine for 2 or 3 options, I would prefer JavaBean style once you get above that. Having 20 overloaded methods for every possible combination of parameters just looks terrible
    – TheLQ
    Nov 27, 2010 at 19:38
  • 3
    @TheLQ: C# 4.0 makes this easier by allowing optional and named parameters in constructor and method calls. Nov 27, 2010 at 22:40
  • 9
    @TheLQ That's what Builder with fluent syntax is for, see e.g. Guava's MapMaker.
    – maaartinus
    Aug 6, 2011 at 16:35
  • 7
    @Thorbjørn Ravn Andersen, I'd say "give all arguments as parameters" is better OO-style than "call JavaBean setters" because a setter implies there is an underlying attribute being set, which by definition exposes internal details. Using the connect(..) method in the example makes no such assumption; maybe you set a user and password attributes, maybe you don't. What's important is that you focus on the right OO concept: the "connect" message.
    – Andres F.
    Nov 21, 2011 at 16:03

When are getters and setters justified?

When the behavior "get" and "set" actually match up to behavior in your model, which is practically never.

Every other use is just a cheat because the behavior of the business domain is not clear.


That answer might have come across as flippant, so let me expand. The answers above are mostly correct but focus on the programming paradigms of OO design and some what miss the big picture. In my experience this leads people to think that avoiding gettings and setters is some academic rule for OO programming languages (e.g people think replacing getters with properties is grand)

In fact it is a consequence of the design process. You don't have to get into interfaces and encapsulation and patterns, arguing over whether it does or doesn't break these paradigms and what is or isn't good OO programming. The only point that ultimately matters is that if there is nothing in your domain that works like this by putting them in you are not modeling your domain.

The reality is that it is highly unlikely that any system in your domain space has getters and setters. You cannot walk up to the man or woman who is responsible for payroll and simply say "Set this salary to X" or "Get me this salary". Such behavior simply doesn't exist

If you are putting this into your code you are not designing your system to match the model of your domain. Yes that breaks interfaces and encapsulation, but that isn't the point. The point is that you are modelling something that doesn't exist.

More over you are probably missing an important step or process, because there is probably a reason I can't just walk up to pay roll and say set this salary to X.

When people use getters and setters they tend to push the rules for this process into the wrong place. This is moving away from your domain even more. Using the real world example, it is like salary assuming that the random person who walked in has the permission to get these values otherwise he wouldn't be asking for them. Not only is that not how the domain is, it is in fact lying about how the domain is.

  • this doesn't seem to offer anything substantial over points made and explained in prior 17 answers
    – gnat
    Sep 8, 2014 at 10:12
  • 2
    The other answers talk about objects, interfaces and other languages paradigms. Which is fine, but it is not the central issue. Getters and setters are not just bad because they break some coding conventions, but primarily because you hardly ever encounter this behaviour in the actual model you are representing. This point tends to get lost in the discussion about the best coding practices. Sep 8, 2014 at 10:42
  • Just what do you think the interface to payroll is if it isn't set/get salary? Sep 8, 2014 at 17:50
  • 3
    If they are wrapped around authorization layers and restricted to certain external entities they are not getters and setters. I'm not saying don't have any method on the payroll department that changes the salary, but that method should align with the internal processes in place in the company itself. For example most companies set salary based on the employees contract, which is authorized by a manager. If the employee's salary changes a new contract is drawn up and a manager has to sign it. Therefore payroll should expect a contract object and some authorisation object to change pay roll Sep 9, 2014 at 14:17
  • 4
    Or to put it another way, there is quite a difference between set_salary(new_salary, employee_id) and authorized_salary_update(employee_contract, authorising_manager). The process should model the internal business process Sep 9, 2014 at 14:23

As a general rule, getters and setters are a bad idea. If a field isn't logically part of the interface and you make it private, that's fine. If it is logically part of the interface and you make it public, that's fine. But if you make it private and then turn around and make it effectively public again by providing a getter and setter, you're back to where you started except your code is now more verbose and obfuscated.

Obviously, there are exceptions. In Java, you might need to use interfaces. The Java standard library has backward compatibility requirements so extreme as to outweigh normal measures of code quality. It's even possible that you may actually be dealing with the legendary but rare case where there's a good chance you may later replace a stored field with on the fly calculation without otherwise breaking the interface. But these are exceptions. Getters and setters are an anti-pattern that needs special justification.

  • 6
    A getter and setter mean that the attribute, not the field, is part of the interface. Suppose getBirthDate() and SetBirthDate() take "yyyy/mm/dd" but the field stored is the number of days since 01/01/1000. You can change that to 01/01/0001 and the getter and setter will keep the interface the same. Especially because 'public' means publically trashable, variables should never be public; always use a setter to validate the incoming value, update any related fields, convert as needed, etc. Try to use a getter in case the internal storage changes. Oct 4, 2011 at 7:35
  • @AndyCanfield that's a bit strong to say public means publicly trashable..That's only so if u program it badly. If you have a setter and the wrong value is sent to it then u could throw an exception which u could call trashing the program but it's quitting with an errorAlso if the user of the object can give a variable a value and cud give it the wrong value then u can bear that in mind and test it.u may say "ah but I only have to do 1 test if I use a setter",but maybe ur own code gives the variable a bad value..so the setter might not reduce your tests.n with tests,ur prog isn't "trashed"
    – barlop
    Feb 1, 2015 at 5:31

whether field is accesible directly or via method is not realy important.

Class invariants (usefull ones) is important. And to preserve them, we sometimes need to not be able to change something from outside. Eg. if we have class Square with separete width and height, changing one of them makes it become something else than square. So we need method changeSide If it was Rectangle, we could have setters/public field. But setter than would test whether its greater than zero would be better.

And in concrete languages (eg. java) are reasons why we need those methods (interfaces). And another reason for method is compatibility (source and binary). So its easier to add them then think whether public field would suffice.

btw. I like to use simple immutable value holding classes with public final fields.

  • This is pretty much the only thing that should be avoided. Going from field to property/getter/setter is a breaking change in most languages.
    – MrDosu
    Sep 16, 2014 at 11:13

You may want to change your internals to whatever while keeping the interfaces the same. If your interfaces don't vary, them you code won't break. You still can change your internals as you wish.

  • 1
    I'm surprised this answer is so far down. Getters and setters allow you to do more in the future (e.g. fire an event, do more input validation, do internal bookkeeping) without breaking your existing API. Even with non-public code, the fewer APIs you have to change, the fewer dependencies to update, and the fewer bugs introduced making those updates. Apr 27, 2016 at 6:00

My approach is this -

When I expect to diddle with the data later on, a getter/setter is justified. Also, if change is happening, I often push the data into a getter/setter.

If it's a POD structure, I leave the slots available.

On a more abstract level, the question is "who manages the data", and that depends on the project.


Firstly there are broadly two types of objects which i will comment on, value and service types.

Service types should never have setters, whatever dependencies they require should not be gettable. THe best way to pass dependencies is via a constructor or factory that way all instances are fully formed from the beginning, plain and simple.

Value types should also be immutable, on the oher hand there are times when this is not practical such as an ORM, or some other mapping such as from a widget to an object. All other value types that get passed around the system from one layer or part to another should be immutable and should not have setters.

  • I'd suggest a third type: a mutable container, whose purpose is to hold one or more values; in many cases, a container should not be expected to have much in the way of logic or validation. Code which needs a method to compute six positive integers may pass a container for six integers to the method which will store the results therein. Responsibility for ensuring the numbers are positive should generally lie with either the caller or the called method, not with the container.
    – supercat
    Jan 13, 2016 at 22:37

If using getters and setters feels complicated, the problem might be the language, not the concept itself.

Here's the code from the second example written in Ruby:

class Fridge
  attr_accessor :cheese

def go_shopping fridge
  fridge.cheese += 5

Notice it looks a lot like the first example in Java? When getters and setters are treated as first class citizens, they're not a chore to use, and the added flexibility can sometimes be a real boon - for example, we could decide to return a default value for cheese on a new fridge:

class Fridge
  attr_accessor :cheese

  def cheese
    @cheese || 0

Of course there will be many variables that shouldn't be exposed publicly at all. Needlessly exposing internal variables will make your code worse, but you can hardly blame that on getters and setters.

  • That is beautifully stated. Builder functions were added because we want to create immutable objects while gradually building up the recipe: maybe if you add artificial sweetener, you don't need to add sugar. Using named parameters, and even with overloading, it is very hard building one method doing all. And then of course java doesn't have named parameters, hence one more reason people are using the Builder pattern.
    – YoYo
    Jan 13, 2016 at 0:38

Consider a Size class which encapsulates width and height. I can eliminate setters by using the constructor but how does that help me draw a rectangle with Size? Width and height are not internal data to the class; they're shared data that must be available to the consumers of Size.

Objects consist of behaviors and state - or attributes. If there is no exposed state then only behaviors are public.

Without state, how would you sort a collection of objects? How would you search for a specific instance of an object? If you only use constructors, what happens when your object has a long list of attributes?

No method parameter should ever be consumed without validation. Therefore it is laziness to write:

setMyField(int myField){
    this.myField = myField;

If you do write it that way then you have at least prepared for using the setter for validation; it's better than a public field - but just barely. But at least you have a consistent public interface that you can come back and put in validation rules without breaking the code of your customers.

Getters, setters, properties, mutators, call them what you will, but they're necessary.

  • But at least you have a consistent public interface that you can come back and put in validation rules without breaking the code of your customers. That's not true. Adding validation rules further down the road could very well "break the code of your customers". Take an int instance variable, for example, and imagine that you decide to add a validation rule to only accepts nonnegative values. The problem is that your customer's code may already rely on the possibility to set it to a negative value...
    – jub0bs
    Nov 1, 2015 at 14:19

If getters and setters violate encapsulation and true OO, then I'm seriously in trouble.

I always felt an object represents whatever best comes to mind that you need it to do.

I have just finished writing a program that generates Mazes in Java, and I have class that represents "Maze Squares". I have data in this class that represents coordinates, walls and booleans etc.

I have to have some way to change/manipulate/access this data! What do I do without getters and setters? Java doesn't use properties and setting all my data that is local to this class to public is DEFINITELY a violation of encapsulation and OO.

  • 6
    Here is the question: If you made all those fields public, and stopped using the getters and setters how would your code be different? Nov 27, 2010 at 15:10
  • In theory, its not. Why even make a class at that point? Same argument could be made with anything. But the post below mine seems to have said it more elegantly. (Getters and setters are a way to safely hand a value to an object, or retrieve a value from that object.) The post goes on.. Nov 27, 2010 at 15:14
  • 3
    I'd point out: that poster eventually agreed with me and posted another answer to that effect. Essentially, using getters and setters is the same as manipulating the data directly. You don't really gain OOness by doing that. In order to be OO you ought to provide a higher level interface to the data. Nov 27, 2010 at 15:29
  • 5
    I think the best way of describing it would be to say that you should design your interfaces from the outside in, not the inside out. The interface your object provides should be dictated by how the object is used not how it is implemented. So don't write getters and allow external object to interpret the data. Find out what question they need answered, and write a method that answers that question. Don't allow external objects to modify state by a setter, find out what kind of manipulations they need to perform and write methods that do that. Nov 27, 2010 at 15:31
  • 2
    In some cases, Getters and Setters are the best method. Sometimes they are the best interface you can provide. However, in many cases they are not. In many cases, you are just leaking implementation details into other classes. Nov 27, 2010 at 15:32

In Swift, there are variables (class, instance, and static variables) which are quite the same as properties. And for every variable, you can add a getter and a setter if you wish to do so, plus code to be called before the setter is called (with a parameter "newValue") and code to be called after the setter is called (with a parameter "newValue).

The variable itself can be private or public (or fileprivate, or internal, or open; these are Swift specific), and the setter can be private.

If it's private it doesn't expose anything (and fileprivate only exposes within one source file). If you have a private setter, it can't be modified without control so you are always safe. And if you have a getter, then it doesn't expose any internal state. It only exposes what the interface says it exposes.

Perfectly object oriented. What you see may be the internal state, maybe it's not. I might have four temperate classes Kelvin, Celsius, Fahrenheit and Reamur which all store temperature in degree Kelvin internally - but only one exposes this directly as a property. And you don't know which one (since the could all four store the temperature in Celsius), and it doesn't matter. Only the interface matters.

The only difference between a variable and a function is mostly that functions have () appended :-) And you don't have a "get" or "set" prefix. And variables should be used for things that are reasonably fast.

BTW. Swift allows fridge.cheese += 5 (no semicolon), calling a "getter" and a "setter".

Not the answer you're looking for? Browse other questions tagged or ask your own question.