DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports Events Over 2 million developers have joined DZone. Join Today! Thanks for visiting DZone today,
Edit Profile Manage Email Subscriptions Moderation Admin Console How to Post to DZone Article Submission Guidelines
View Profile
Sign Out
Refcards
Trend Reports
Events
Zones
Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
  1. DZone
  2. Software Design and Architecture
  3. Performance
  4. Why TCP is Evil and HTTP is King

Why TCP is Evil and HTTP is King

Oren Eini user avatar by
Oren Eini
·
Aug. 02, 12 · Interview
Like (0)
Save
Tweet
Share
8.74K Views

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:

image

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 .

compare this:

image_thumb2

to this:

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.

Transmission Control Protocol

Opinions expressed by DZone contributors are their own.

Popular on DZone

  • How Do the Docker Client and Docker Servers Work?
  • 9 Ways You Can Improve Security Posture
  • RabbitMQ vs. Memphis.dev
  • What Was the Question Again, ChatGPT?

Comments

Partner Resources

X

ABOUT US

  • About DZone
  • Send feedback
  • Careers
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 600 Park Offices Drive
  • Suite 300
  • Durham, NC 27709
  • support@dzone.com
  • +1 (919) 678-0300

Let's be friends: