I have several applications where I perform constant insertions of data in the local database, but the number of concurrent applications has gotten too large and the data is behind schedule. Now, I need to split these applications into separate servers to keep the data current in real time.
What are the most common ways to enter data remotely and concurrently with high performance (Client XML, JSON, API, WebService, etc.)?
It is the service-oriented architecture of Microsoft. You can start with this tutorial if you want to learn right 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 settings and tends to be more granularized. While WCF works best on atomic requests (a call to accomplish the entire task), the Web API works best by passing the job on multiple (more resource-oriented) requests.
The default data transfer format is JSON, but the Web API also works with XML , OData and YAML .
This is more out of curiosity because it escapes the .NET scope, but it might be interesting for you to know. SQL Server Integration Services (SSIS) seamlessly integrates databases into SQL Server. It may be an option if the desire is good synchronicity and performance.
