1
I have several applications where I perform constant data insertions in the local database, however, the number of simultaneous applications has become very large and the data is delayed. Now, I need to split these applications into separate servers to be able to keep data up to date in real time.
What are the most common ways to enter data remotely and concurrently with high performance (Client XML, JSON, API, Webservice, etc.)?
1
It is the service-oriented architecture of Microsoft. You can start with this tutorial if you want to learn now.
WCF can work, in theory, with any data model, such as XML (default), JSON, Odata, or an unusual format, such as YAML.
This architecture is simpler than WCF in terms of configurations and tends to be more granularized. While WCF works best on atomic requests (one call to perform the entire task), the Web API works best due to the task in multiple requests (more resource-oriented).
The standard data transfer format is JSON, but the Web API also works with XML, Odata and YAML.
This is mostly out of curiosity because it’s outside the scope . NET, but it might be interesting for you to know. SQL Server Integration Services (SSIS) integrates databases into SQL Server transparently. It may be an option if desire is good timing and performance.
What would you use? (Considering the scenario I presented). About SSIS, I use SQL Server, is a viable alternative.
Web API, for being more eclectic. WCF is an older and more cast alternative, therefore.
Browser other questions tagged .net
You are not signed in. Login or sign up in order to post.
Rest ?
– DontVoteMeDown