title: Static layers in a java web application
body: <p>I am building a small website for fun/learning using a fairly standard Web/Service/Data Access layered design.</p>
  
  <p>To save me from constantly having to create instances of my service layer/data access layer classes, I have made the methods in them all static. I shouldn't get concurrency issues as they use local variables etc and do not share any resources (things are simple enough for this at the moment).</p>
  
  <p>As far as I can see the only trade-off for this is that I am not really following a true OO approach, but then again it keeps the code much cleaner.</p>
  
  <p>Is there any reason this would not be a viable approach? What sort of problems might arise later on? Would it be better to have a "factory" class that can return me instances of the service and data layer classes as needed?</p>