DeepfakeHTTP – Your 100% static dynamic back end

github.com

27 points·tommybox··12 comments

I think the name prefix of "Deep" is out of pocket for the project, call it fakeHTTP, call it Netcat -listen.

And in classic HN retort, the time it would take just hand crafting all these responses you could spin up some SQLite to REST, or whatever database floats your boat.

You are right, but there are lot of project names like "Linux Mint" (how it related to mint?) or Telegram (not related to real telegram)

This could be great for mocks.

At one point I was trying to automate against an internal tool that had a (useless, for my purposes) dependency on AWS. Rather than give my pipeline access to AWS, I strapped VCR (https://github.com/vcr/vcr) onto it, ran it on my laptop with my own AWS permissions, and then just ran the automation with VCR in front of it from there on out.

The difference is that with DeepfakeHTTP you don't need to code and setup responses, just provide dumps. vcr is platform that you must setup programatically.

This reminds me of mockserver, but I like that you can statically setup your responses beforehand. I'm not sure that's possible in mockserver.

I was hoping / expecting that this used few shot or one shot learning to construct realistic mock data

Yeah I was expecting GPT-3 (or github copilot) but for HTTP responses.

I was here for it until I realized it's Java.

Java is great. Performant. Great libraries and data types. Huge community. Can use Kotlin if you want concise syntax and the interop is pretty seamless

Java is as bad as the developer using it. I say this as a person who used, GO, Nodejs, python professionally for 5 years and Java+scala since 2 years.

this sounds amazing for hackathons!

thanks))

Reply on news.ycombinator.com