What are the Slack Archives?
Itβs a history of our time together in the Slack Community! Thereβs a ton of knowledge in here, so feel free to search through the archives for a possible answer to your question.
Because this space is not active, you wonβt be able to create a new post or comment here. If you have a question or want to start a discussion about something, head over to our categories and pick one to post in! You can always refer back to a post from Slack Archives if needed; just copy the link to use it as a reference..
Hello everyone. Is there a best practice or some workflow for doing rollbacks in AWS/Spryker Cloud e
Hello everyone. Is there a best practice or some workflow for doing rollbacks in AWS/Spryker Cloud environment? Rolling back the code base to a previous version is just a matter of creating containers from some older images, but what is the right (or the best) way to roll back database, redis and elasticsearch?
Comments
-
Hi Neven. Great question. Let me that that to our experts. I will keep you posted
0 -
@USZ0XG6SK can i have a couple of days to compile a good answer for you?
0 -
or is this an urgent matter?
0 -
Hi @tom.lehner, it is not so urgent. I would be happy if i get an answer until the end of next week.
0 -
should be doable, i will keep you posted
0 -
thanks π
0 -
@tom.lehner any news here?
0 -
Still in the works, sorry
0 -
any update? This is a very interesting question
0 -
Let me check the status on it
0 -
We are currently just finishing up the documentation. Should be ready for release shortly
0 -
Here is a preliminary version I can share with you. The final version will be published in our documentation sometime next week.
0 -
thx,
this is just a documentation how to restore a database backup.
I'm more interested in rolling back a deployment without deleting data. When restoring the backup, things like e.g. orders or new customer accounts that happened in the meantime will be deleted0 -
Hi Philipp,
There are 2 different options, what is possible to rollback, actually 3 when needed:
1. DB: using a previously created snapshot you can restore the whole DB (structure + data)
2. Application: using a deploy function with a dedicated version (GitHub commit)
3. Do steps 1 and 2 simultaneously
It sounds to me you are asking about the 2nd step and it is covered in the documentation here: https://cloud.spryker.com/docs/deploying-in-a-production-environment#roll-back-an-applicationCould you please check it and let us know if that is what you are looking for?
Thank you.P.S. there is no backup and this restore solutions for redis, ES at the moment.
0 -
We treat the DB as a single source of truth. Thus, there are solutions to backup and restore:
1. data in database (backup and restore RDS)
2. application or code (deploy a specific version).
Everything else should be updated from these 2 places: DB or code of application.
With backups of many interconnected pieces a new problem would need to be solved: keep all moving part in a consistency, when backed up and when restored.0 -
So basically suggested way to go is to
β’ deploy older docker image
β’ restore a db from a snapshot and then run data sync to sync the data with ES and redis
Is there a reason why arenβt you suggesting the Propel Migrations? This seems to me a better way to revert the database structure without loosing the data.
If we restore the DB from a snapshot, it would mean that we lose potential data saved since last snapshot (max 1 hour in this case), which, in a high traffic shop, would mean a large potential loss.0 -
Propel Migrations are also possible, but requires code changes.
With RDS backup/restore no code changes are needed, as only AWS services need to be triggered.
It is just a different approach.0 -
RDS Backup & Restore is of cause the "easier" way, but as Neven wrote, there will be a loss of data, which doesn't sound too cool
0
Categories
- All Categories
- 42 Getting Started & Guidelines
- 7 Getting Started in the Community
- 8 Additional Resources
- 7 Community Ideas and Feedback
- 69 Spryker News
- 894 Developer Corner
- 757 Spryker Development
- 83 Spryker Dev Environment
- 361 Spryker Releases
- 3 Oryx frontend framework
- 34 Propel ORM
- 68 Community Projects
- 3 Community Ideation Board
- 30 Hackathon
- 3 PHP Bridge
- 6 Gacela Project
- 22 Job Opportunities
- 3.2K π Slack Archives
- 116 Academy
- 5 Business Users
- 370 Docker
- 551 Slack General
- 2K Help
- 75 Knowledge Sharing
- 6 Random Stuff
- 4 Code Testing
- 32 Product & Business Questions
- 68 Spryker Safari Questions
- 50 Random