This makes perfect sense as the primary purpose of the DataContractJsonSerializer is to be used with WCF, and just as its name suggests, it’s a JSON serializer for DataContract types.
One interesting side effect of the above is that you can’t use DataContractJsonSerializer with anonymous types.
Unfortunately you won’t be able to deserialize the JSON string back into an anonymous type as all the available deserialize methods requires a type which has a parameterless constructor.
Another main functional difference between these two serializers is how they deal with dictionaries.
Take this simple dictionary for instance:
The DataContractJsonSerializer serializes dictionaries as an array of KeyValuePair objects:
This subtle different might seem trivial at first, but it can make a huge difference when you’re dealing with data that are originated from a non-.Net language. A perfect example came couple of days ago when we were testing out the Facebook graph API and one of the JSON responses we came across was a dictionary whose keys were numeric IDs like this:
In cases like this, you simply won’t be able to deserialize this JSON using the DataContractJsonSerializer!
Enjoy what you’re reading? Subscribe to my newsletter and get more content on AWS and serverless technologies delivered straight to your inbox.
I’m an AWS Serverless Hero and the author of Production-Ready Serverless. I have run production workload at scale in AWS for nearly 10 years and I have been an architect or principal engineer with a variety of industries ranging from banking, e-commerce, sports streaming to mobile gaming. I currently work as an independent consultant focused on AWS and serverless.
In this course, we’ll cover everything you need to know to use AWS Step Functions service effectively. Including basic concepts, HTTP and event triggers, activities, design patterns and best practices.
Here is a complete list of all my posts on serverless and AWS Lambda. In the meantime, here are a few of my most popular blog posts.
- Lambda optimization tip – enable HTTP keep-alive
- You are thinking about serverless costs all wrong
- Many faced threats to Serverless security
- We can do better than percentile latencies
- I’m afraid you’re thinking about AWS Lambda cold starts all wrong
- Yubl’s road to Serverless
- AWS Lambda – should you have few monolithic functions or many single-purposed functions?
- AWS Lambda – compare coldstart time with different languages, memory and code sizes
- Guys, we’re doing pagination wrong