-
Notifications
You must be signed in to change notification settings - Fork 43
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
Content Contribution: Pathway to Serverless Development page #36
Comments
@shortjared It was a good overall conversation with you about the content for this section. If you have any questions, feel free to ping me or add it here. For next steps, let's get a draft outline for the content that we can review together. |
Hey @shortjared, just checking if you are good on getting a draft outline out soon. If you have any questions, please let me know. |
Pathway to Serverless DevelopmentIntroducing Serverless to your Projects
Migrating from the Monolith
All in On Serverless
Serverless is Serviceful, Relying on Third Parties
Setting up your Teams for Success
Scaling and Performance Considerations
Should we Multi-cloud?
The Rough Edges of Serverless
Operationalizing
|
@rupakg took a first stab at this, let me know your thoughts. |
@shortjared This is sweet and I love that you thought through it. I like all the sub-sections. Some of it may belong under different sections. So I will think about it and maybe suggest something. I would say you can start on the Introducing Serverless to your Projects sub-section. |
Description
Add content to the Development/Pathway to Serverless Development section of the guide.
Filename:
/guide/source/dev/pathway_to_sls.md
Page/Section: Development/Pathway to Serverless Development
Contributing Author/Company: Jared Short (Trek10)
Details:
Some suggested ideas and guidance for content in this section:
Pathway to Serverless Development
Tell the story around how to get involved and get thinking on introducing serverless technologies into the organizations. Cutting through the hype and misconceptions, use personal experiences to contrast advantages and challenges.
The text was updated successfully, but these errors were encountered: