-
Notifications
You must be signed in to change notification settings - Fork 2.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
serverless.adoc #1192
serverless.adoc #1192
Conversation
Co-Authored-By: evanchooly <[email protected]>
Co-Authored-By: evanchooly <[email protected]>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Added a couple of comments.
|
||
Quarkus solves of much of this for us. Quarkus offers blindingly fast start up times memory optimized applications well-suited to | ||
serverless environments. With Quarkus, developers can continue to use Java and many of the libraries familiar to them. Quarkus takes on | ||
the work of packaging everything up for deployment. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't know where we will include that but I'm missing a bit the "how do we do that`. Maybe mentioning natives images and GraalVM in this paragraph would make sense.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good, I've made a few comments.
|
||
=== FaaS API | ||
All this begs the question: why doesn't Quarkus simply provide its own opinionated API? | ||
While this may happen eventually, the current philosophy is to integrate with what choices make sense so developers don't need to learn a whole new API set to make use of Quarkus. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should this document include your AWS lambda example?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I was debating it but i was holding off until the meeting with Burr to get a feel with how we want to present that aspect.
JVM startup time and memory overhead are prohibitive costs for many organizations. | ||
However, it would be a shame to leave behind the wealth of experience and vast ecosystem of Java. | ||
|
||
Quarkus solves of much of this for us. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Should be Quarkus changed to {project-name} ? Or it doesn't matter now (after rename)?
clean up some bits based on PR feedback
This is the first draft of this document. I'm reasonably sure we'll want to tweak this and expand one area or another but hopefully this will serve as the framework solidifying our messaging on quarkus/serverless applications.