Featured post
c# - Should I compress the data being exposed via wcf service? -
i'm creating wcf service exposes object graph expected grow in size while service , running. in playing test data (85k), smaller expected when live, hit default 65k message size limit. quick on net showed simple enough extend in config.
as i'm creating service , client consumes it, wondered if there added value in compressing data before sent it. having run brief test, test data shrunk around 7k, looks aid in time message sent on wire , increase amount of data send.
the service pre-prepares data before first call made , there no initial overhead on every call due compression.
is idea sake of scalability, , trying optimise performance, or adding complexity not needed?
by reading post, seems able implement compression quite easily.
if control both sides, adding layer of compression/decompression not increase complexity general scenarios when gain lot of bandwidth benefit out of it.
what minimize complexity implementing patterns interceptor
or decorator
.
- Get link
- X
- Other Apps
Comments
Post a Comment