Why TCP is Evil and HTTP is King
Join the DZone community and get the full member experience.Join For Free
nitpicker corner: if you tell me that http is built on tcp i’ll agree, then point out that this is completely irrelevant to the discussion.
i got asked why ravendb uses http for transport, instead of tcp. surely binary tcp would be more efficient to work with, right?
well, the answer it complex, but it boils down to this:
huh? what does fiddler has to do with ravendb transport mechanism?
quite a lot, actually. using http enable us to do a lot of amazing things, but the most important thing it allows us to do?
it is freaking easy to debug and work with.
- it has awesome tools like fiddler that are easy to use and understand.
- we can piggyback on things like iis for hosting easily.
- we can test out scaling with ease using off the shelf tools.
- we can use hackable urls to demo how things work at the wire level.
in short, http it human readable.
for that matter, i just remapped the changes api solely for the purpose of making it fiddler friendly.
coming back again to building pro software, making sure that your clients and your support team can diagnose things easily .
there is an entire world of difference between the quality that you can give between the two.
and that is why ravendb is using http, because going with tcp would mean writing a lot of our own tools and making things harder all around.
Opinions expressed by DZone contributors are their own.
Essential Architecture Framework: In the World of Overengineering, Being Essential Is the Answer
How to LINQ Between Java and SQL With JPAStreamer
Security Challenges for Microservice Applications in Multi-Cloud Environments
Application Architecture Design Principles