Skip to content
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.

Sign up for GitHub

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

Update preparation-for-going-live.md #2330

Merged
merged 2 commits into from
Dec 8, 2023
Merged

Update preparation-for-going-live.md #2330

Changes from 1 commit
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
f36faba
Update preparation-for-going-live.md
ThomasLehnerSpryker Nov 16, 2023
c97aba4
Merge branch 'master' into ThomasLehnerSpryker-patch-8
lenadoc Dec 8, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions docs/ca/dev/preparation-for-going-live.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -56,7 +56,7 @@ Double check that you do not have any clear text passwords stored in config file

## Four weeks before go-live

- *Make sure you are familiar with NewRelic APM*. If you have not requested NewRelic APM to be set up for you, do so. For more details about requesting changes, see [Platform change requests](https://docs.spryker.com/docs/scos/user/intro-to-spryker/support/how-to-use-the-support-portal.html#platform-change-requests).
- *Make sure you have an APM set up*. Application Performance Monitoring tools help you identify performance bottlenecks in your application. You can request NewRelic APM from Spryker (subject to additional fees).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@ThomasLehnerSpryker how do I request NewRelic?

Copy link
Collaborator Author

@ThomasLehnerSpryker ThomasLehnerSpryker Nov 30, 2023 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Will add preliminary instructions

- *Performance Tips implemented and verified*. Double-check that you implemented all the provided [performance tips](/docs/scos/dev/guidelines/performance-guidelines/general-performance-guidelines.html).
- *Conduct Load Tests*. Conduct load tests for your application. The sample data used for testing should be comparable to the size and complexity of the production data.
- *Performance testing and environment scale dial-in*. Testing your production environment before officially going live and assessing its performance are critical steps for a successful launch. Because production environments typically employ horizontal auto-scaling, it's essential to conduct stress and performance tests under expected average and peak loads. These tests enable our team to optimize the environment's vertical scaling in advance, ensuring that it can seamlessly handle the expected loads from the get-go, without any potential delays caused by auto-scaling mechanisms. This proactive approach eliminates the need for post-launch adjustments, providing your team with a significant advantage and peace of mind, while delivering a fast and responsive experience to your users right from the first request to the application.
Expand Down Expand Up @@ -142,4 +142,4 @@ If your go-live date is close and you feel like you need help with any of the de

- *Validate that the rollback strategy is still valid*. Check that you have everything you need to recover from an unforeseen issue with the newest version of the project you are deploying.
- *Organize a go-live support team*. Prepare a team that can monitor your go-live, react quickly to any issues, and work with the Spryker Support or Operations teams.
- *Validate BI and Analytics Integrations*. They should not be connected to your production database, but should be connected to the provided read replica. Make sure that no external system is working with your production database.
- *Validate BI and Analytics Integrations*. They should not be connected to your production database, but should be connected to the provided read replica. Make sure that no external system is working with your production database.
Loading