Today, I implemented the ability to compress our return Json.
After trying a number of options, this was the one that seemed to give me the flexibility and consistency:
Microsoft.AspNet.WebApi.MessageHandlers.Compression
And although I've not found a lot of documentation to this fact, best practice seems to dictate that you do not want to compress every single response. For objects less than ~4kb the time, and server resources, it takes to compress is more than the time save for sending the smaller package over the wire. I would love to see more on this subject, though.
Saturday, February 28, 2015
Tuesday, February 24, 2015
Sunday, February 22, 2015
Project Assemblies and Tools
Architecture, third party assemblies, and tools for current work project:
Web API, returning JSON
Ninject for dependency and interception/AOP
Hand-rolled usage and error logging
Service/Business Layer
Entity Framework (without any repository pattern or datalayer)
Using Command Query pattern as much as possible
MS Unit for unit testing
MS Unit for performance testing/benchmarks
Looking into using CacheCow. Additional assemblies and strategies are being considered and will be documented as they come up.
Visual Studio 2013, .Net 4.51
SQL Server 2008
SOAP UI
Textpad++
Resharper 8
NCrunch
Ghost Doc Pro
Web Essentials
Nuget
Git/Bitbucket
Chrome App: Postman
Write everything so that it is testable, no set meteric for code coverage. Currently have 180 unit tests. Performance will be tested. If a performance issue is caused by a code change, we want to know, ASAP.
So Here Goes..
Like everyone, I should have started this blog twelve years ago when I first began programming professionally.
To be able to market your skills, work on your writing, create connections, get feedback on your difficulties, and have a resource for your problems and solutions to look back on, there is little that can compete. To my team, to those who I will work with and hire in the future, to those who are just starting out, and to those who have been in the field for decades, start a blog, you won't regret it!
I am a journeyman, a generalist, and someone who takes great pride in what I do. I love solving problems for businesses, and for those I work with. Over the years I have built the smallest of brochure sites, for the smallest of small businesses to work on the largest of applications for major corporations. I have worked on over fifty project at more than a dozen companies.
I'm currently working for a mid-size, international company (in the data research and reporting space) and loving every bit of it. Agile team of four developers, and a scrum master. No project managers! In total, the shop has thirty developers, with additional BA, QA, and managerial support. The current project is a Web API, using C# and Entity Framework. Given the multiple purposes, long term goals, and level of usage, maintainability and performance are the primary architectural concerns of the project. Probably, the first time I have had to be cognizant of both of these features at the same time and to this degree.
I have a number of thoughts of how I would like to see this blog developed, but 1) I just hope I keep at it 2) It will serve me well over the next six months while I finish up the first phase or so of our Web API project.
To be able to market your skills, work on your writing, create connections, get feedback on your difficulties, and have a resource for your problems and solutions to look back on, there is little that can compete. To my team, to those who I will work with and hire in the future, to those who are just starting out, and to those who have been in the field for decades, start a blog, you won't regret it!
I am a journeyman, a generalist, and someone who takes great pride in what I do. I love solving problems for businesses, and for those I work with. Over the years I have built the smallest of brochure sites, for the smallest of small businesses to work on the largest of applications for major corporations. I have worked on over fifty project at more than a dozen companies.
I'm currently working for a mid-size, international company (in the data research and reporting space) and loving every bit of it. Agile team of four developers, and a scrum master. No project managers! In total, the shop has thirty developers, with additional BA, QA, and managerial support. The current project is a Web API, using C# and Entity Framework. Given the multiple purposes, long term goals, and level of usage, maintainability and performance are the primary architectural concerns of the project. Probably, the first time I have had to be cognizant of both of these features at the same time and to this degree.
I have a number of thoughts of how I would like to see this blog developed, but 1) I just hope I keep at it 2) It will serve me well over the next six months while I finish up the first phase or so of our Web API project.
Subscribe to:
Posts (Atom)