mitocgroup

Fair point :) Will learn based on this experience and try to simplify the documentation. Thanks for your feedback!

Thank you, Neytan! We'd be happy to notify you when we are open for public beta, but again feel free to email at beta@deep.mg to get an early access ;)

I guess we have tried to show the value to both developers and businesses. Would you like to read in README more technical details or more none technical examples on how this is already used by other people? To be honest, we have tried to explain it similar to AngularJS, that we are using on frontend, but I guess we failed you here.

We have met with guys from JAWS at AWS re:Invent last week and they are doing great job with it! We don't look at them as competition, but rather brothers in arms who aim the same goals of building serverless platforms on AWS. We are pretty sure that we will partner in the near future, mainly because from our humble experience, customers who need help with Serverless AWS are overwhelmingly a lot, but developers and partners who can meaningfully help them - very few.

Think of enterprise applications as puzzles, and think of us as puzzle manufacturers who will help puzzle builders (developers, devops, admins, etc) get the best puzzle for customer needs :)

Again, very much appreciate your feedback. This is the main reason why we've posted it here, to get some discussions and learn together what is relevant nowadays to developers and what is not, so we don't have to reinvent the wheel.

To touch base on your example with authentication, we are working on deep-security library that everybody will be able to reuse without any effort. We are approaching security in every layer similar Amazon IAM, and since we are using microservices architecture, developers don't need to write any security specific code, because it is automatically generated at deploy. Everything is collected at deployment time from every layer and applied on AWS for backend and database, while on frontend is exposed in UI as role-based access. Does it make sense?

Thanks for your feedback! Just to make sure we can act on your feedback: Do you mean the first diagram is distracting or which logo are you referring to? If you would make the change, what would you improve?