I am writing Portfolio module for my web site and it has 3 components. Gallery Category, Gallery, & Gallery Images.I am doing all the request handling, (creating, reading, updating, other), for the above 3 components in 1 class, Portfolio.DB handling jobs for Portfolio module is done in another file.My question is, even just for request handling purpose, can you do all the operations in 1 class?-Reddy
Design Anti-Patterns - C# - Do you call this a God object?
design patterns;anti patterns
You have to go back to the basics - coupling and cohesion.  Coupling is how much a class depends on other classes, and cohesion is how well it does the job it is intended to do.  Ideally, you want to lower coupling and raise cohesion.  In other words - decoupled objects that do its one job well - without a whole bunch of other responsibilities.  It sounds like when you create your Portfolio class you are trying to make it do a lot of different jobs.  Not only will this create coupling with the other objects, but will lower cohesion in that it must do things that it really is not intended for.  I wouldn't go down that path - it is only inviting maintenence issues in the long run.