built my new project using AWS Lambda. Serverless. It&#x27;s fucking awesome.<p>- html and js files hosted on s3<p>- api gateway talking to dynamodb<p>- no servers and worries about scaling.<p>The only downside thing is that it&#x27;s truly tough to figure out how to point your domain to s3. I followed everything and DNS is okay too yet the domain never resolves. Tested with route53 and after 1 month of trying gave up and using digitalocean&#x27;s DNS manager.<p>I implemented a token based HTTP Api, a fully functional Angular.js app that talks to it. Allow user to register, change passwords, login, create a blog.<p>It definitely requires new type of thinking: throwing shit out. Seriously, I&#x27;ve built apps with Flask, Node.js, variety of PHP frameworks on Apache, Nginx, Java Web applications and I think that a serverless architecture blows everything out of the water.<p>It&#x27;s nice to know there&#x27;s not a server anywhere. All of the HTTP requests are sent to AWS, and AWS runs a script that modifies or does things to the dynamodb. It feels me with so much excitement. I&#x27;ve yet to stress test it but I expect it to be highly scalable as AWS ramps things up.<p>However, I don&#x27;t think I will be using AppEngine because I&#x27;m so used to AWS now it feels like a lot of cost to switch over to Google....I&#x27;m afraid AppEngine is another Google+ moment.<p>Guys, I really think serverless architecture is the way to go, and is the future!