Questions regarding the magento one hosting from aws to digital ocean deployment ?

Hi Team,

I want to deploy my magento project on digitalocean, so i thought to clear some doubts to move ahead.

As of now , it deployed on AWS with a particular architecture. So following are some of the questions need to be asked.

  1. What will be the architecture for our magento store.
  2. What is the pricing for a particular architecture /what will be the monthly cost ??
  3. Do you use varnish cache ?
  4. Which server is used for serving php(apache/nginx)?
  5. How much time it will take to deploy our store from aws hosting to digital ocean hosting ?
  6. How many domain we can make in a one installation(as we will also need the test environment for the same store) ?
  7. How frequently we can scale the architecture ?
  8. Do you use redis server and memcache cache ?
  9. Is the cron jobs handled by your system ?
  10. How about FTP/SSH logins ??
  11. Does the database backup taken daily by you?
  12. is the Email setup daily ?
  13. Is Load Balancer used ?
  14. Is Git software available ?


Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

At DigitalOcean, self-managed hosting is provided. This means you setup the installation, from the Web Server to the Magento store you wish to run. You are provided with a droplet (ie virtualized machine) and credentials for the root user (unless an SSH key is provided). Because of this, a lot of your questions depend on how you setup the droplet and make it work for you.

You can always resize to a bigger droplet if your store grows and needs more resources at its disposal. You can find guides on resizing and downsizing via this article on resizing and this article on downsizing.

While DigitalOcean provides a backup service you can utilize (for an additional cost), it would be run on a weekly basis, so you might wish to make a custom script or cron job to handle making daily backups of your database.

None of the services you make on the droplet would be behind a load balancer unless you set one up. You could make one using one of the many DigitalOcean articles covering load balancing if you wished, or utilize our floating IPs feature to help in the process.

You can certainly use Git if you so wish. It all depends on your setup. You can find many articles on using Git via these articles.

You can view the full list of packages and prices here.

Hope it helps, and happy coding!