G
Guest
I am working on porting our existing intranet from classic ASP to ASP.NET.
Currently the code is in a single application. After I complete the
conversion there could be up to 6 developers maintaining the application. I
feel that for scalability purposes it would be better to break it up into 5
or 6 functional areas. However my manager feels that we will gain nothing by
doing this and that it will actually be more of a hassle. I cannot come up
with a solid argument for my side.
Am I correct to think that we should break everything up? I would
appreciate some advice from either side of the discussion.
Thanks.
Currently the code is in a single application. After I complete the
conversion there could be up to 6 developers maintaining the application. I
feel that for scalability purposes it would be better to break it up into 5
or 6 functional areas. However my manager feels that we will gain nothing by
doing this and that it will actually be more of a hassle. I cannot come up
with a solid argument for my side.
Am I correct to think that we should break everything up? I would
appreciate some advice from either side of the discussion.
Thanks.