Last post Jul 17, 2015 06:01 AM by XIII
Jul 15, 2015 10:39 AM|nid15|LINK
We are building an in-house application which will be used by various employees in multiple countries. Our goal is that if it works out well, we can commercialize it to companies that do similar work as ours. My experience has always been with client server
applications and we do have some modules already working in client server using winforms and it works well. Installations across employees is not a problem since we use Remote Desktop.
Now, we want to use the latest the frameworks which will be supported for a long time to come. Many whom I have consulted have told me to use WebApi, odata. I am not very familiar with web application technologies and will appreciate if someone can give
us pointers. Does webapi, odata only handle the middleware? Do we need to decide on the front end?
Our application contains various modules like calender, task assignment and data grids. The grid is going to be a major part of the application since we are in insurance claims industry and it is not uncommon for us to have 2000+ lines populating the database
on a daily basis. The client server application works find because it is running on the terminal server so the data grid populates very fast, scrolling is also very fast with thousands of records, the users can double click on the rows and screens open up
where they can enter notes etc. Can we expect the same kind of performance with webapi and odata? We cannot afford to have lag (the spinning wheels) on the user interface.
I have seen applications in our industry where they are web based, but when we login to the sites, they download the software however the data still resides on the cloud. They seem to have good response with data grids. Are these possible in .net?
Is it better to stick to client server applications hosted on a remote desktop/citrix if grid performance, multiple windows is of importance?
Jul 17, 2015 06:01 AM|XIII|LINK
Web API is the new cool kid on the block hence most people will advice it to you. It's powerful for sure and I'm making use of it as part of a solution in the banking industry.
If you can continue, also with your clients, with the citrix/winforms approach then why put budget into creating a new approach? Don't just start creating things for the sake of technology but for a business purpose. If you want to also expose the data to
a browser based solution then we're talking something different. Both Web API as WCF are good candidates, the first one is usually easier to set up and use.