This is sort of a just rant but I want some feedback of
other issues
and concerns that you might think of so I can create a good
argument
to change this.. Or if you think it's a good plan let me
know also.
Where I work they decided to create a new infustructure for
our web
applications based on the idea that SQL servers are a lot
more
expensive then web servers.
Now rather then doing queries and returning the data we need
for
filling in tables we're loading collection object with data
on
application load which get stored in session, throwing the
data into a
dataview and filtering on the dataview. I can see where
somecases
that'd be a good idea, like things that don't hardly ever
change, but
this is for everything.
This to me just seems like a ton of overhead, we just
started doing it
so we don't have more then a couple tiny applications that
are
currently doing it, but I'm tasked with writing a large one
and I'm
dreading on writing all that code to do this when I can
write a quick
SQL query to get the data I need and bind it to the dataview
also I'm
very worried about keeping the collection objects and
database in
sync.
I've told my boss my concerns all he ever comes back with is
'SQL
servers are a lot more expensive then web servers, we can
add another
webserver to the farm if its too slow'. The kicker is we're
using a
SQL server for SessionState, so we're going to be storing
and
retrieving the objects from a SQL server anyways
Jamie
--~--~---------~--~----~------------~-------~--~----~
You received this message because you are subscribed to the
Google Groups "ASP.Net Community" group.
To post to this group, send email to aspnet googlegroups.com
To unsubscribe from this group, send email to
aspnet-unsubscribegooglegroups.com
For more options, visit this group at http://gr
oups.google.com/group/aspnet?hl=en
-~----------~----~----~----~------~----~------~--~---
|
