Yeah you certainly refer to AWS ElasticBeanStalk, in fact it is like AppEgine. I even use it now.
But the thing is actually i wanted to put the frontend app in the same folder than the backend app and put maybe everything in a Docker. Or divide it in two service each in separated docker images.
I didn't think of deploying on ELB because it seemed to be too huge for a such small app.... but it seem like no that huge.
i wanted to put the frontend app in the same folder than the backend app and put maybe everything in a Docker
Honestly, that is (IMHO) the thing which we'd prefer to avoid. All frontend stuff should live at least on some static serving proxy (like nginx) or better some CDN (or something alike, like github pages).
In your application the traffic for logic (sending urls and short handles between backend and frontend) is going to be much smaller than size of all JS/CSS/PNG etc, right?
Yeah you certainly refer to AWS ElasticBeanStalk, in fact it is like AppEgine. I even use it now.
But the thing is actually i wanted to put the frontend app in the same folder than the backend app and put maybe everything in a Docker. Or divide it in two service each in separated docker images.
I didn't think of deploying on ELB because it seemed to be too huge for a such small app.... but it seem like no that huge.
Honestly, that is (IMHO) the thing which we'd prefer to avoid. All frontend stuff should live at least on some static serving proxy (like nginx) or better some CDN (or something alike, like github pages).
In your application the traffic for logic (sending urls and short handles between backend and frontend) is going to be much smaller than size of all JS/CSS/PNG etc, right?
yes