4 ms·

Well we do currently use .net but I asked a question the other week on here about different languages etc and one good piece of advice I got was to create a RES

Well we do currently use .net but I asked a question the other week on here about different languages etc and one good piece of advice I got was to create a REST service and interact with that. We have put a lot of thought into it and we were going to give it a go with WCF and REST but I don't see any issue why we cannot buy a UNIX box and put Postgresql on it and put a layer on it with some other language serving the REST? I will be benchmarking this with a current customer who has over 1 million products and a lot of visitors a day to see how it stands up against MSSQL, we are quite sensible into not jumping into decisions so I appreciate your comment and it shall definitely be part of the benchmark.

dos1 15y ago
Having spent the better part of 3 years creating REST services with .NET, I strongly recommend you do NOT use traditional WCF. The WCF Web API stuff looks interesting but still seems immature. I've found ASP.NET MVC to be the best tool for creating REST apis.
- chrislomax 15y ago
  Thanks for the advice I have found the routing in MVC and their returns types (JSON etc) working really well to be honest, I will take a look at that Thanks
- hkarthik 15y ago
  Even MVC is a little heavy and you don't get a lot of things for free with it. Compare it to some of the Java OSS projects like Enunciate and it still requires a lot of extra work. On the .NET side, I would suggest looking at Demis Ballot's excellent Service Stack library. http://www.servicestack.net/ http://www.servicestack.net/