DigitalOcean is an infrastructure-as-a-service (IaaS) platform from the company of the same name headquartered in New York. It is known for its support of managed Kubernetes clusters and “droplets” feature.
$5
Starting Price Per Month
Git
Score 10.0 out of 10
N/A
N/A
N/A
WP Engine
Score 7.3 out of 10
N/A
WP Engine is a website hosting service built to host WordPress for companies of any size, with features such as daily backups, firewall,SSL, and proprietary caching technology.
$35
per month
Pricing
DigitalOcean
Git
WP Engine
Editions & Modules
1GB-16GB
$5.00
Starting Price Per Month
8GB-160GB
$60.00
Starting Price Per Month
No answers on this topic
Startup
$35
per month
Core
$400
per month (annual contract)
Enterprise
Custom
*Per Month
Offerings
Pricing Offerings
DigitalOcean
Git
WP Engine
Free Trial
No
No
Yes
Free/Freemium Version
No
No
No
Premium Consulting/Integration Services
No
No
No
Entry-level Setup Fee
No setup fee
No setup fee
No setup fee
Additional Details
—
—
Discount available for annual billing on the Startup plan.
DigitalOcean is fast, easy to use, reliable, with few features, and at a great price. WP Engine is clunky, tricky to use, reliable, feature rich, and at a very high price. GoDaddy is clunky, difficult to use, too complex to be reliable, rife with garbage feature 'add-ons', and …
By usability, DigitalOcean wins. I love DigitalOcean for a lot of reasons, but their setup process is clunky and their feature set is fairly limited. Their setup requires technical competence but after that they are a breeze to work with. For what they do, DigitalOcean is …
DigitalOcean is perfect for hosting client websites, running marketing tools, and managing media storage with Spaces and CDN. The use of Droplets to quickly launch landing pages or WordPress sites for campaigns is a Godsend. It’s great for fast, cheap, and scalable solutions. But for complex microservices or projects needing strict compliance (like HIPAA), DigitalOcean may not always be the best fit, but that depends heavily on your project.
GIT is good to be used for faster and high availability operations during code release cycle. Git provides a complete replica of the repository on the developer's local system which is why every developer will have complete repository available for quick access on his system and they can merge the specific branches that they have worked on back to the centralized repository. The limitations with GIT are seen when checking in large files.
I am an enterprise user of WordPress and host over 7000 sites with WPEngine. Areas that I think they are well suited for include customers that need enterprise-level support and uptime and have more complex needs than a simple blog. They also manage scale well with a variety of isolated install options that you can scale up or down depending on your contract needs. They also provide premier support for enterprises and have highly knowledgable Technical Account Managers that provide a significant value add. If I were to look at where it isn't as appropriate for usage I would focus on the low-end needs and say while they do support small sites, there are options out there for cheaper hosting that lack the support a WPEngine gives you.
I love the database backups and how quickly & easy it is to restore from an old backup point. This gives me & my clients confidence that any change can be rolled back.
The built in caching & CDN mean that I have to spend less time worrying about the speed of the server & site. The caching has some side-effects that take getting used to (on-page dynamic PHP code sometimes needs to be moved to API endpoints), but this is true for most caching systems.
They have really good support for multiple environments. It's very easy to have separate production & staging environments. It's also very simple to deploy from staging to production, making product launches and large scale website copy changes much easier to coordinate.
Some products/services available on other Cloud providers aren't available, but they seem to be catching up as they add new products like Managed SQL DBs.
While they have FreeBSD droplets (VMs), support for *BSD OSs is limited. I.e. the new monitoring agent only works on Linux.
There are no regions available on South America.
They don't seem to offer enterprise-level products, even basic ones as Windows Server, MS SQL Server, Oracle products, etc.
I'd like to see WP Engine offer their own monitoring solution. When I say monitoring, I mean specific use cases that may end up being something you could script. This would keep customers from having to pay for additional services like Pingdom, New Relic, etc.
I would like to see some proactive analysis done by WP Engine on their customer sites - at least on their home pages, and offer up suggestions. This kind of goes along with the other example.
Finally, it would be nice to see a "lighter" offering, perhaps a plan that costs $49 for those who want to host only a few sites, or even 1 site.
Git has met all standards for a source control tool and even exceeded those standards. Git is so integrated with our work that I can't imagine a day without it.
I was in a situation where I had to bolt Wordpress on to an existing infrastructure that could not support it. If I ever end up in that situation again, please kill me. Other than that reasonably common use case, I don't think it offers a lot of value over robust shared hosting, virtual private server (VPS) or dedicated servers.
I honestly can't think of an easier way to set up and maintain your own server. Being able to set up a server in minutes and have fully control is awesome. The UX is incredibly intuitive for first-time users as well so there's no reason to be intimidated when it comes to giving DigitalOcean a shot.
From the onboarding and in the days afterward, it was very easy to get into the platform and begin creating important websites and configuring user options. The interface is easy to navigate, and the platform pages load quickly. Since the platform is built for Word plus press, it has features including backup, staging, maintenance mode, and direct WP-Admin login to make configuration and site management faster. We have never had any issues on the billing side of the account.
They have always been fast, and the process has been straight-forward. I haven't had to use it enough to be frustrated with it, to be honest, and when I have an issue they fix it. As with all support, I wish it felt more human, but they are doing aces.
I am not sure what the official Git support channels are like as I have never needed to use any official support. Because Git is so popular among all developers now, it is pretty easy to find the answer to almost any Git question with a quick Google search. I've never had trouble finding what I'm looking for.
Support is generally great. Enterprise support is fantastic, with little to no wait times. I find that chat support can almost always take care of the problem without escalating to a ticket for a higher level of troubleshooting. The chat support for many other hosting providers can only handle basic issues. This is a big bonus for us to get quick and helpful answers.
DigitalOcean is an inexpensive product as compared to other products available in the market. The UI is easy and the beginner can also understand the UI with the step by step guide. It provides a lot of custom features and the user needs to pay only for what they are using. Amazon has a complex UI and is on the expensive side. DigitalOcean is simple to use and is easily manageable and the servers can easily be set up without additional cost and such.
I've used both Apache Subversion & Git over the years and have maintained my allegiance to Git. Git is not objectively better than Subversion. It's different. The key difference is that it is decentralized. With Subversion, you have a problem here: The SVN Repository may be in a location you can't reach (behind a VPN, intranet - etc), you cannot commit. If you want to make a copy of your code, you have to literally copy/paste it. With Git, you do not have this problem. Your local copy is a repository, and you can commit to it and get all benefits of source control. When you regain connectivity to the main repository, you can commit against it. Another thing for consideration is that Git tracks content rather than files. Branches are lightweight and merging is easy, and I mean really easy. It's distributed, basically every repository is a branch. It's much easier to develop concurrently and collaboratively than with Subversion, in my opinion. It also makes offline development possible. It doesn't impose any workflow, as seen on the above linked website, there are many workflows possible with Git. A Subversion-style workflow is easily mimicked.
While we still use GoDaddy for some services, WP Engine definitely has been a major upgrade for our WordPress hosting. In addition to faster load speeds, WP Engine has been more adept at allowing us to manage a high number of websites without straining the system. We have never used Network Solutions for our own hosting needs, but when we do interact with them on behalf of our clients, their systems always seem to be clunky and hard to use, and they often overcharge customers by selling them products they do not need.
Positive - Elastic computer instances make it possible to pay for only for what you need.
Positive - Competitive pricing - some of the products that DigitalOcean offers are much cheaper than those offered by competitors.
Negative - Having to go to other cloud computing platforms for more specific, advanced services like Computer Vision optimized services, GPU cloud compute instances, etc...
Git has saved our organization countless hours having to manually trace code to a breaking change or manage conflicting changes. It has no equal when it comes to scalability or manageability.
Git has allowed our engineering team to build code reviews into its workflow by preventing a developer from approving or merging in their own code; instead, all proposed changes are reviewed by another engineer to assess the impact of the code and whether or not it should be merged in first. This greatly reduces the likelihood of breaking changes getting into production.
Git has at times created some confusion among developers about what to do if they accidentally commit a change they decide later they want to roll back. There are multiple ways to address this problem and the best available option may not be obvious in all cases.
