|
|
You're in the
dotnet distributed apps
group:Distributed Application Design using .NET
dotnet distributed apps:
fat-client project into a more acceptable multiple layered application. We're looking at using the 3 typical layers: data, business, client. The requirements of my application (that I can think of) are: - Transaction oriented. On the current system this equated to a peak of < 1000 transactions per minute over an hour's time, and on average < 500 transactions per hour. The # of transactions, however, is not as important as the SPEED of the transaction. - Client can start long-running processes on business layer, such as batch operations and generating reports. Client must continue to operate while these processes occur, but needs some form of notification event when these processes finish on the business layer. - Business layer may need to maintain state of client (this is not a definite, I'd like to get away from it if possible) - Client will be in a Windows form and may EVENTUALLY (6+ months) be converted to a web-based interface. I should mention that I've programmed with C# as a hobbyist for about a year, but it's always been pretty generic fat-client type applications. I really don't have a ton of experience with .NET, yet on my team, I definitely have the most experience with newer platfroms & technologies. I've heard of Web Services and .NET Remoting, and have read a little on them, but no practical experience. I'm basically trying to determine what tool or type of project I need to be using for each layer. Is what I'm looking at something as simple as a C# Windows Form for my client and a Web Service with data access components for my business side? Are Web Services efficient enough to use in mission critical appslications? Is there any .NET technology I can make use of to make transfer of data between client and business layers fairly transparent (more transparent than manually converting data to a type supported by the underlying network, sending & verifying the data, and re-integrating it on the receiving end)? Any and all advice would be welcome. Thanks,
Hi,
Unfortunately Visual Studio.Net doesn't offer a prebuilt infrastructure for a distributed application. You have to investigate all the possibilities, then build and decide for your infrastructure (no light matters), and then start to build your application. One would expect at least a proposal for a three-tier infrastructure (more or less generated). Regards Roger. [quoted text, click to view] "John M. Langley" <jjlangley2@comcast.net> wrote in message news:<O8QtrYyDFHA.4020@TK2MSFTNGP14.phx.gbl>...
> I'm on a part of a team looking at converting a rather large scale > fat-client project into a more acceptable multiple layered application. > We're looking at using the 3 typical layers: data, business, client. > The requirements of my application (that I can think of) are: > > - Transaction oriented. On the current system this equated to a peak of > < 1000 transactions per minute over an hour's time, and on average < > 500 transactions per hour. The # of transactions, however, is not as > important as the SPEED of the transaction. > - Client can start long-running processes on business layer, such as > batch operations and generating reports. Client must continue to > operate while these processes occur, but needs some form of notification > event when these processes finish on the business layer. > - Business layer may need to maintain state of client (this is not a > definite, I'd like to get away from it if possible) > - Client will be in a Windows form and may EVENTUALLY (6+ months) be > converted to a web-based interface. > > I should mention that I've programmed with C# as a hobbyist for about a > year, but it's always been pretty generic fat-client type applications. > I really don't have a ton of experience with .NET, yet on my team, I > definitely have the most experience with newer platfroms & technologies. > I've heard of Web Services and .NET Remoting, and have read a little > on them, but no practical experience. > > I'm basically trying to determine what tool or type of project I need to > be using for each layer. Is what I'm looking at something as simple as > a C# Windows Form for my client and a Web Service with data access > components for my business side? Are Web Services efficient enough to > use in mission critical appslications? Is there any .NET technology I > can make use of to make transfer of data between client and business > layers fairly transparent (more transparent than manually converting > data to a type supported by the underlying network, sending & verifying > the data, and re-integrating it on the receiving end)? > > Any and all advice would be welcome. > > Thanks,
Thanks for the reply. This is about the same conclusion we came up
with, but with none of us really having any true large applications built with the .NET framework, it's nice to have a confirmation. It seems that the closest thing to built-in infrastructure is designing/building an ASP.NET application -- which is not something we will presently be doing. Several members of the team have picked up some literature that will be helpful for us in our final decision. I suppose in some ways it's nice that Microsoft allows the freedom for developers to create distributed apps 100% the way we want to, but it would be nice to see some form of standard model to emerge (and if there is one, please, someone point me to it! =>). Perhaps in the design of our product we'll look @ how simple it would be to generate a generic distrbuted app, and if it's something that can be done in a fashion that could be highly reusable, publish an article on it. Thanks again for your time & advice! -John Langley [quoted text, click to view] Roger wrote:
> Hi, > > Unfortunately Visual Studio.Net doesn't offer a prebuilt > infrastructure for a distributed application. You have to investigate > all the possibilities, then build and decide for your infrastructure > (no light matters), and then start to build your application. > One would expect at least a proposal for a three-tier infrastructure > (more or less generated). > > Regards Roger. > > > "John M. Langley" <jjlangley2@comcast.net> wrote in message news:<O8QtrYyDFHA.4020@TK2MSFTNGP14.phx.gbl>... > >>I'm on a part of a team looking at converting a rather large scale >>fat-client project into a more acceptable multiple layered application. >> We're looking at using the 3 typical layers: data, business, client. >>The requirements of my application (that I can think of) are: >> >>- Transaction oriented. On the current system this equated to a peak of >> < 1000 transactions per minute over an hour's time, and on average < >>500 transactions per hour. The # of transactions, however, is not as >>important as the SPEED of the transaction. >>- Client can start long-running processes on business layer, such as >>batch operations and generating reports. Client must continue to >>operate while these processes occur, but needs some form of notification >>event when these processes finish on the business layer. >>- Business layer may need to maintain state of client (this is not a >>definite, I'd like to get away from it if possible) >>- Client will be in a Windows form and may EVENTUALLY (6+ months) be >>converted to a web-based interface. >> >>I should mention that I've programmed with C# as a hobbyist for about a >>year, but it's always been pretty generic fat-client type applications. >> I really don't have a ton of experience with .NET, yet on my team, I >>definitely have the most experience with newer platfroms & technologies. >> I've heard of Web Services and .NET Remoting, and have read a little >>on them, but no practical experience. >> >>I'm basically trying to determine what tool or type of project I need to >>be using for each layer. Is what I'm looking at something as simple as >>a C# Windows Form for my client and a Web Service with data access >>components for my business side? Are Web Services efficient enough to >>use in mission critical appslications? Is there any .NET technology I >>can make use of to make transfer of data between client and business >>layers fairly transparent (more transparent than manually converting >>data to a type supported by the underlying network, sending & verifying >>the data, and re-integrating it on the receiving end)? >> >>Any and all advice would be welcome. >> >>Thanks,
John,
this (http://www.asplications.com.au/GenieWhitePaper.pdf) whitepaper has an overview of a wholistic methodology for building systems that deploy purely as WebServices (so consumed by WinForms app, javascript dhtml, Flash, Java clients etc). Plenty of diagrams included. Scalable and secure server topology, extreme use of OO. Enjoy, Radek [quoted text, click to view] "John M. Langley" <jjlangley2@comcast.net> wrote in message news:#JxFI9CFFHA.2296@TK2MSFTNGP15.phx.gbl... > Thanks for the reply. This is about the same conclusion we came up > with, but with none of us really having any true large applications > built with the .NET framework, it's nice to have a confirmation. It > seems that the closest thing to built-in infrastructure is > designing/building an ASP.NET application -- which is not something we > will presently be doing. Several members of the team have picked up > some literature that will be helpful for us in our final decision. > > I suppose in some ways it's nice that Microsoft allows the freedom for > developers to create distributed apps 100% the way we want to, but it > would be nice to see some form of standard model to emerge (and if there > is one, please, someone point me to it! =>). Perhaps in the design of > our product we'll look @ how simple it would be to generate a generic > distrbuted app, and if it's something that can be done in a fashion that > could be highly reusable, publish an article on it. > > Thanks again for your time & advice! > -John Langley > > Roger wrote: > > Hi, > > > > Unfortunately Visual Studio.Net doesn't offer a prebuilt > > infrastructure for a distributed application. You have to investigate > > all the possibilities, then build and decide for your infrastructure > > (no light matters), and then start to build your application. > > One would expect at least a proposal for a three-tier infrastructure > > (more or less generated). > > > > Regards Roger. > > > > > > "John M. Langley" <jjlangley2@comcast.net> wrote in message news:<O8QtrYyDFHA.4020@TK2MSFTNGP14.phx.gbl>... > > > >>I'm on a part of a team looking at converting a rather large scale > >>fat-client project into a more acceptable multiple layered application. > >> We're looking at using the 3 typical layers: data, business, client. > >>The requirements of my application (that I can think of) are: > >> > >>- Transaction oriented. On the current system this equated to a peak of > >> < 1000 transactions per minute over an hour's time, and on average < > >>500 transactions per hour. The # of transactions, however, is not as > >>important as the SPEED of the transaction. > >>- Client can start long-running processes on business layer, such as > >>batch operations and generating reports. Client must continue to > >>operate while these processes occur, but needs some form of notification > >>event when these processes finish on the business layer. > >>- Business layer may need to maintain state of client (this is not a > >>definite, I'd like to get away from it if possible) > >>- Client will be in a Windows form and may EVENTUALLY (6+ months) be > >>converted to a web-based interface. > >> > >>I should mention that I've programmed with C# as a hobbyist for about a > >>year, but it's always been pretty generic fat-client type applications. > >> I really don't have a ton of experience with .NET, yet on my team, I > >>definitely have the most experience with newer platfroms & technologies. > >> I've heard of Web Services and .NET Remoting, and have read a little > >>on them, but no practical experience. > >> > >>I'm basically trying to determine what tool or type of project I need to > >>be using for each layer. Is what I'm looking at something as simple as > >>a C# Windows Form for my client and a Web Service with data access > >>components for my business side? Are Web Services efficient enough to > >>use in mission critical appslications? Is there any .NET technology I > >>can make use of to make transfer of data between client and business > >>layers fairly transparent (more transparent than manually converting > >>data to a type supported by the underlying network, sending & verifying > >>the data, and re-integrating it on the receiving end)? > >> > >>Any and all advice would be welcome. > >> > >>Thanks, > >>John Langley
Thank you, I most certainly will look into that. Any information on
this topic is very useful. -John [quoted text, click to view] Radek Cerny wrote:
> John, > > this (http://www.asplications.com.au/GenieWhitePaper.pdf) whitepaper has an > overview of a wholistic methodology for building systems that deploy purely > as WebServices (so consumed by WinForms app, javascript dhtml, Flash, Java > clients etc). Plenty of diagrams included. Scalable and secure server > topology, extreme use of OO. > > Enjoy, > > Radek > > "John M. Langley" <jjlangley2@comcast.net> wrote in message > news:#JxFI9CFFHA.2296@TK2MSFTNGP15.phx.gbl... > >>Thanks for the reply. This is about the same conclusion we came up >>with, but with none of us really having any true large applications >>built with the .NET framework, it's nice to have a confirmation. It >>seems that the closest thing to built-in infrastructure is >>designing/building an ASP.NET application -- which is not something we >>will presently be doing. Several members of the team have picked up >>some literature that will be helpful for us in our final decision. >> >>I suppose in some ways it's nice that Microsoft allows the freedom for >>developers to create distributed apps 100% the way we want to, but it >>would be nice to see some form of standard model to emerge (and if there >>is one, please, someone point me to it! =>). Perhaps in the design of >>our product we'll look @ how simple it would be to generate a generic >>distrbuted app, and if it's something that can be done in a fashion that >>could be highly reusable, publish an article on it. >> >>Thanks again for your time & advice! >>-John Langley >> >>Roger wrote: >> >>>Hi, >>> >>>Unfortunately Visual Studio.Net doesn't offer a prebuilt >>>infrastructure for a distributed application. You have to investigate >>>all the possibilities, then build and decide for your infrastructure >>>(no light matters), and then start to build your application. >>>One would expect at least a proposal for a three-tier infrastructure >>>(more or less generated). >>> >>> Regards Roger. >>> >>> >>>"John M. Langley" <jjlangley2@comcast.net> wrote in message > > news:<O8QtrYyDFHA.4020@TK2MSFTNGP14.phx.gbl>... > >>>>I'm on a part of a team looking at converting a rather large scale >>>>fat-client project into a more acceptable multiple layered application. >>>> We're looking at using the 3 typical layers: data, business, client. >>>>The requirements of my application (that I can think of) are: >>>> >>>>- Transaction oriented. On the current system this equated to a peak of >>>> < 1000 transactions per minute over an hour's time, and on average < >>>>500 transactions per hour. The # of transactions, however, is not as >>>>important as the SPEED of the transaction. >>>>- Client can start long-running processes on business layer, such as >>>>batch operations and generating reports. Client must continue to >>>>operate while these processes occur, but needs some form of notification >>>>event when these processes finish on the business layer. >>>>- Business layer may need to maintain state of client (this is not a >>>>definite, I'd like to get away from it if possible) >>>>- Client will be in a Windows form and may EVENTUALLY (6+ months) be >>>>converted to a web-based interface. >>>> >>>>I should mention that I've programmed with C# as a hobbyist for about a >>>>year, but it's always been pretty generic fat-client type applications. >>>> I really don't have a ton of experience with .NET, yet on my team, I >>>>definitely have the most experience with newer platfroms & technologies. >>>> I've heard of Web Services and .NET Remoting, and have read a little >>>>on them, but no practical experience. >>>> >>>>I'm basically trying to determine what tool or type of project I need to >>>>be using for each layer. Is what I'm looking at something as simple as >>>>a C# Windows Form for my client and a Web Service with data access >>>>components for my business side? Are Web Services efficient enough to >>>>use in mission critical appslications? Is there any .NET technology I >>>>can make use of to make transfer of data between client and business >>>>layers fairly transparent (more transparent than manually converting >>>>data to a type supported by the underlying network, sending & verifying >>>>the data, and re-integrating it on the receiving end)? >>>> >>>>Any and all advice would be welcome. >>>> >>>>Thanks, >>>>John Langley > >
Hi John,
I'm in no way an expert in .Net. I too am looking to do something similar as you are. I've looked hard in several places on the .Net platform. For whatever is worth, Microsoft has tons of information on how to develop client/server, multi-tiered applications. I'm sure you've probably looked at this information, but in the case you did not, I thought maybe you might want to try MS. Also you might want to find out if there is any INETA users group in your area. These people are user group in .Net can probably give you some information. In our organization, we use strictly web services and they seem pretty secured. But. . . if you have good developers who knows the technology, they can best tap into the technology to its max. In ADO.Net the DB is dis-connected while the user(s) are editing the data. You might want to consider this as an option in view of your transactional design needs. Oh yes, one more thing. . . get ready to read, read and read. This technology is so vast, and large in contents and depth that it is sometimes overwhelming. But I guess this is what we developers do best: read and write code. Good luck Al [quoted text, click to view] "John M. Langley" wrote:
> I'm on a part of a team looking at converting a rather large scale > fat-client project into a more acceptable multiple layered application. > We're looking at using the 3 typical layers: data, business, client. > The requirements of my application (that I can think of) are: > > - Transaction oriented. On the current system this equated to a peak of > < 1000 transactions per minute over an hour's time, and on average < > 500 transactions per hour. The # of transactions, however, is not as > important as the SPEED of the transaction. > - Client can start long-running processes on business layer, such as > batch operations and generating reports. Client must continue to > operate while these processes occur, but needs some form of notification > event when these processes finish on the business layer. > - Business layer may need to maintain state of client (this is not a > definite, I'd like to get away from it if possible) > - Client will be in a Windows form and may EVENTUALLY (6+ months) be > converted to a web-based interface. > > I should mention that I've programmed with C# as a hobbyist for about a > year, but it's always been pretty generic fat-client type applications. > I really don't have a ton of experience with .NET, yet on my team, I > definitely have the most experience with newer platfroms & technologies. > I've heard of Web Services and .NET Remoting, and have read a little > on them, but no practical experience. > > I'm basically trying to determine what tool or type of project I need to > be using for each layer. Is what I'm looking at something as simple as > a C# Windows Form for my client and a Web Service with data access > components for my business side? Are Web Services efficient enough to > use in mission critical appslications? Is there any .NET technology I > can make use of to make transfer of data between client and business > layers fairly transparent (more transparent than manually converting > data to a type supported by the underlying network, sending & verifying > the data, and re-integrating it on the receiving end)? > > Any and all advice would be welcome. > > Thanks, > John Langley
Hi John,
I think you should look into something like DevExpress XPO (an Object-Relational Mapper) for your data layer on which you can build your business layer. I have no relation to DevExpress, but I am using this product and it is great... /Thomas "John M. Langley" <jjlangley2@comcast.net> skrev i en meddelelse news:O8QtrYyDFHA.4020@TK2MSFTNGP14.phx.gbl... [quoted text, click to view] > I'm on a part of a team looking at converting a rather large scale > fat-client project into a more acceptable multiple layered application. > We're looking at using the 3 typical layers: data, business, client. The > requirements of my application (that I can think of) are: > > - Transaction oriented. On the current system this equated to a peak of < > 1000 transactions per minute over an hour's time, and on average < 500 > transactions per hour. The # of transactions, however, is not as > important as the SPEED of the transaction. > - Client can start long-running processes on business layer, such as batch > operations and generating reports. Client must continue to operate while > these processes occur, but needs some form of notification event when > these processes finish on the business layer. > - Business layer may need to maintain state of client (this is not a > definite, I'd like to get away from it if possible) > - Client will be in a Windows form and may EVENTUALLY (6+ months) be > converted to a web-based interface. > > I should mention that I've programmed with C# as a hobbyist for about a > year, but it's always been pretty generic fat-client type applications. I > really don't have a ton of experience with .NET, yet on my team, I > definitely have the most experience with newer platfroms & technologies. > I've heard of Web Services and .NET Remoting, and have read a little on > them, but no practical experience. > > I'm basically trying to determine what tool or type of project I need to > be using for each layer. Is what I'm looking at something as simple as a > C# Windows Form for my client and a Web Service with data access > components for my business side? Are Web Services efficient enough to use > in mission critical appslications? Is there any .NET technology I can > make use of to make transfer of data between client and business layers > fairly transparent (more transparent than manually converting data to a > type supported by the underlying network, sending & verifying the data, > and re-integrating it on the receiving end)? > > Any and all advice would be welcome. > > Thanks, > John Langley
Don't see what you're looking for? Try a search.
|
June 2003
July 2003
August 2003
September 2003
October 2003
November 2003
December 2003
January 2004
February 2004
March 2004
April 2004
May 2004
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
November 2007
December 2007
January 2008
February 2008
March 2008
April 2008
May 2008
June 2008
| home · blog · groups | Questions? Comments? Contact the dn |