Live data from Hacker News

Hoodie: very fast web app development

hood.ie

71–80 of 155 posts

Re: Hoodie: very fast web app development

#71

I have a question for experts in Hoodie and/or other similar projects (like Meteor): How are database connections managed? If every client (browser) basically talks nearly directly to the database, don't you end up with of thousands of database connections? Large number of connections is not a problem by itself, and servers like nginx handle them well, but I am not aware of a database which will feel comfortable bein…

As long as the underlying OS can provide file descriptors, CouchDB can handle the concurrent connections through the magic of Erlang, both persistent and shorter lived.

There are obvious limits to this, but the Hoodie architecture allows easy scale out (more DB servers and manual sharding, or a dynamo-like BigCouch, more workers etc.) that we’ll get to making use of once Hoodie apps become that big.

Re: Hoodie: very fast web app development

#72
post #42

Earlier quoted context omitted.

Which sounds kind of bad, if that is the case. 1. Even if the users are idiots you shouldn't let them ruin their own application experience. 2. I would never put anything remotely connected to security and user privileges in the same storage accessible by users, so I would have to set up a separate service.

1. what if that idiot messes with gmail’s web console? 2. Security handling is purely server-side. You can’t fake your way without using a proper auth-channel.

The distinction here is that Hoodie is supposed to free you from dealing with servers, but that is currently limited to scenarios where you have users with uniform access privileges and no concerns about users messing around with their database information. So until they add modules most projects will have to get down and dirty in the end if they want to attach any kind of privileges to users. In both points 1 and 2 you need to have some server side logic beyond Hoodie.

Re: Hoodie: very fast web app development

#73
post #42

Earlier quoted context omitted.

1. what if that idiot messes with gmail’s web console? 2. Security handling is purely server-side. You can’t fake your way without using a proper auth-channel.

The distinction here is that Hoodie is supposed to free you from dealing with servers, but that is currently limited to scenarios where you have users with uniform access privileges and no concerns about users messing around with their database information. So until they add modules most projects will have to get down and dirty in the end if they want to attach any kind of privileges to users. In both points 1 and 2…

Hoodie can only promise to free you from worrying about the backend by providing one that you can just use.

The sharing module e.g. makes heavy use of server side logic and database security and access control features. The Hoodie frontend just makes it accessible to frontend devs.

Re: Hoodie: very fast web app development

#74
post #60

Earlier quoted context omitted.

hi I am trying very hard not to be dumb, but this is beating me seemingly Kanso? and Hoodie both have JS stubs at the client and server end, these synch with each other, then synch with whatever you are using at client (say backbone) and server (node? CouchDB? My Postgres server behind my python app?) If thats roughly right, why do I do this? I control my server apps no? Why wrap them in another layer? Json->backbone…

Okay, first off, let's discuss a standard three tier webapp architecture: Browser Server DB You get some HTML/CSS/JS from the server, you display stuff to the user. As the user interacts with your app, HTTP requests hit your server which processes them. As needed, the server will make requests to the DB, which will reply with data, which then gets passed back to the browser. Everyone knows how this stack works, I hop…

thats a fantastic explanation, thanks

Re: Hoodie: very fast web app development

#75
post #41

Earlier quoted context omitted.

Ugh, the word 'hipster' should be banished, along with the word 'fanboy'.

I stopped using the word 'hipster' when it became mainstream.

I was doing that like a year ago. Now I have moved on to using "hipster" ironically.

Re: Hoodie: very fast web app development

#76
Apologies for an off-topic question - how did you go about registering a .ie domain name? I've been wanting to register one for a while, but the last time I looked there was a requirement to show proof of residency (or a business address) in Ireland.

Edit: The reason I ask is that it seems like the developers are living in Zurich and Berlin, not Ireland. I live in SF, so can't fulfil the residency requirement.

Re: Hoodie: very fast web app development

#78
post #8

Hey there, other @hoodiehq dev here. Here is a bit longer intro to Hoodie: http://hood.ie/intro.html And a presentation from earlier at @berlinjs including a live demo: https://www.youtube.com/watch?v=X3Ttb0BD8pg

Nice presentation. In the description of back end modules, you mention payments as a future capability. What kind of payment service would you be able to work with? (I don't see how you could handle card details in the Hoodie architecture). Thanks.

Re: Hoodie: very fast web app development

#80
post #12

Neat, I really like the idea of being able to sync local storage with a Couch backend. > Hoodie currently only runs on OS X Oh, a hipster framework.

are you on Windows or Linux? Would be great if you could help us to migrate it. hoodie is basically CouchDB + node.js, nothing fancy. We just do local DNS magic, creating *.dev domains like http://pow.cx/ , that is only compatible with Mac atm

I'm on windows 8 primarily, but I also run osx and mint. I'm going to check this out on osx first, if all is good, I can help ensure windows compatibility.
Post reply on HN