News for hackers. Stuff that matters.
Re:I bet you over-engineered your startup by btilly on Tuesday July 10, 2012 @01:01PM (#4224819)
Here is my simpler version: function calls are the fastest RPCs. They are faster to run, faster to write, and faster to debug if something goes wrong.

By all means conceive of your application as a bunch of well-engineered little pieces. But for now, write them all as modules that you're making method calls to. Should you some day want to, you're free to replace one by a facade around a remote service. But for now it works and you can move on.

Re:I bet you over-engineered your startup by nix on Tuesday July 10, 2012 @01:35PM (#4225032)
you're free to replace one by a facade around a remote service.

RPC rarely lives up to this promise. Starting simple is certainly a good approach, but don't fool yourself about how hard it's going to be when you need to deal with latency and partial failure later.

Re:I bet you over-engineered your startup by btilly on Tuesday July 10, 2012 @01:40PM (#4225056)
Trust me, I'm fully aware of all of the trouble with getting RPCs to work properly. I still think that it is easier to do that work after you have the original non-rpc version as a reference.
Re:I bet you over-engineered your startup by aaronblohowiak on Tuesday July 10, 2012 @02:54PM (#4225455)
Yes, but making those module boundaries loosely coupled and sharing information only through their interfaces will go a LONG way towards enabling you to remote the call at a later date. The biggest mistakes that prevent remoting a module have to do with requiring context that is not part of the interface of the method call (or having a very chatty back-and-forth, but that is less common.)