77 karma · joined October 25, 2011
But to be politically correct, it should be ca-east-1 ;)
Will help as much as I can, but a piece of advice to Ritlab team - Consider moving your company outside of Moldova and afterwards write a "Thank You" letter ;)
1. We write everything in ES6, following code styling from Airbnb - https://github.com/MitocGroup/javascript
2. Every Lambda is separate npm package, therefore npm is managing all the dependencies; We include node_modules folder into the .zip file and upload it to AWS
3. Using Babel, transpile ES6 to ES5 - https://github.com/MitocGroup/deep-microservices-todo-app/bl...
4. To support 0.10.x, we're requiring Babel Polyfill - https://github.com/MitocGroup/deep-microservices-todo-app/bl...
As anticipated, the performance is not the best one, but functional for some of our use cases where time is not a constrain. That's why the combination with Amazon ECS is perfect complimentary match when AWS Lambda doesn't perform well, as required by the application.
Quote - Serverless doesn’t mean servers are no longer involved. It simply means that developers no longer have to think "that much" about them. Computing resources get used as services without having to manage around physical capacities or limits.
And here is an example: https://github.com/MitocGroup/deep-microservices-todo-app
Based on our experience, currently AWS Lambda is amazing for data / content / asset management use cases. Cold start is a known issue, which I hope AWS will solve sooner rather than later, because a lot of customers are complaining about it ;)
1. DEEP is designed to be Platform-as-a-Service for serverless environments that developers and businesses could use in their own accounts. AWS Lambda is one of those services. The fact that right now only AWS provides the full spectrum of services made us build it on AWS first.
2. "Sandstorm makes it easy to run your own server" and "OpenShift gives you all the tools you need to develop, host and scale your apps in the public or private cloud" - so I would say neither, because the goal as you further described is to be able to support cross-cloud providers, while above ones are service-specific (am I wrong?)
3. You are correct. Right now it's an abstracted layer on AWS, and we are planning to add in near future more providers like Azure, Google Cloud and more. For now, it makes the developer job easy by abstracting everything except application layer, and have it scaled at AWS size, which is virtually infinite.
Does it make sense? And to go even further, what would you improve in our documentation? :)