Common serialization mistakes to avoid

Omar Al Zabir

Rate me:

4.75/5 (4 votes)

17 May 2011CPOL1 min read

27.7K

Caching frequently used objects, that are expensive to fetch from the source, makes application perform faster under high load. It helps scale an application under concurrent requests. But some hard to notice mistakes can lead the application to suffer under high load, let alone making it perform be

Alternatives

Members may post updates or alternatives to this current article in order to show different approaches or add new features.

No alternatives have been posted.

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Written By

Omar Al Zabir

Architect BT, UK (ex British Telecom)

United Kingdom

I am: Head of Engineering Consumer CRM & Billing, BT (ex British Telecom).
I got: 11 Microsoft MVP Awards, 4 CodeProject MVP awards.
I like: Performance and Scalability Challenges.
My Book: Building a Web 2.0 portal using ASP.NET 3.5. Also on Amazon
My Blog: http://omaralzabir.com
My Specialization: Web 2.0, SaaS, Performance and Scalability of Web Apps.
My Email: OmarALZabir at gmail dot com

Follow Me: twitter.com/omaralzabir

My Projects:
Droptiles: Open Source Web 2.0 AJAX Portal
SQL Server real-time monitor
Oracle real-time monitor
Codeuml - UML diagrams as fast as you can type
Fastest Streaming AJAX Proxy
CPU Alerter - Save power, work faster

My Articles:
Top 10 caching mistakes
99.99% Available Production Architecture
10 ASP.NET Performance and Scalability Secrets
UFrame: UpdatePanel and IFRAME combined
Fast ASP.NET web page loading
Fast Streaming AJAX Proxy
Using COM safely inside "using" block without requiring interop assembly
Implementing Word Like Automation Model
Distributed Command Pattern

Common serialization mistakes to avoid

Alternatives

License

Comments and Discussions