What is Amazon EC2?
What is DigitalOcean?
Want advice about which of these to choose?Ask the StackShare community!
What tools integrate with Amazon EC2?
I use DigitalOcean because of the simplicity of using their basic offerings, such as droplets. In AppAttack, we need low-level control of our infrastructure so we can rapidly deploy a custom training web application on-demand for each training session, and building a Kubernetes cluster on top of DigitalOcean droplets allowed us to do exactly that.
Google Compute Engine Amazon Web Services OVH Microsoft Azure Go GitHub
Last week, we released a fresh new release of Komiser with support of multiple AWS accounts. Komiser support multiple AWS accounts through named profiles that are stored in the credentials files.
You can now analyze and identify potential cost savings on unlimited AWS environments (Production, Staging, Sandbox, etc) on one single dashboard.
Read the full story in the blog post.
Google Compute Engine Amazon Web Services Go Docker Material Design for Angular Microsoft Azure GitHub I’m super excited to annonce the release of Komiser:2.1.0 with beta support of Google Cloud Platform. You can now use one single open source tool to detect both AWS and GCP overspending.
Komiser allows you to analyze and manage #cloud cost, usage, #security, and governance in one place. Hence, detecting potential vulnerabilities that could put your cloud environment at risk.
It allows you also to control your usage and create visibility across all used services to achieve maximum cost-effectiveness and get a deep understanding of how you spend on the #AWS, #GCP and #Azure.
I started using DigitalOcean back in January to host a Ghost blog. I was a little worried at first because I didn't have too much experience setting up servers. There was always the option of a full service company that does all the work for you, but the point was that I wanted more control for the purpose of learning. And, learning turned out to be really easy thanks to the great community at DigitalOcean. There are tutorials for just about anything. It has been an amazing learning experience, and now I'm looking forward to hosting more complex projects here. I already have a couple in the works for the near future. I highly recommend it.
I can't rate the Support great or bad, as I haven't really had a need to contact them yet. But everything else has been excellent so far.
A VPS gives the full access that I need, because most of what I do has complex integrations and there is plenty of legacy - very stable, highly tuned code developed over two decades - that I carry with me. My use is also limited to during development, so there is no point going for a full server.
Amazon EC2 is a VPS, except it is cheaper.
Additionally, I used to previously take the code developed on my VPS and deploy it to whatever server the client brought.
With Amazon EC2 the deployment is already done. All that remains it to scale up, add other products like dns, mail, storage and so on, and change the billing so that the client gets invoiced. That makes the process that much more predictable and seamless, and the end result much more stable.
I am a freelancer and a researcher. I have had tried a lot of hosting services over the years. But DIgitalOcean stands out from the rest for its pricing. Its just five dollar a month for a basic node.
And the other reason for loving Digital Ocean is that they support Docker. It you buy a VPS machine, chances are that docker support wont be available as with PV or hypervisor, docker need some extra config.
So far I am loving DO :-)
I use Google Compute Engine instances as flexible, reproducible infrastructure that scale with my data science tasks.
Between Google Cloud and Amazon Web Services, I chose Google Cloud for its intuitive UI. SSH within the browser is very convenient.
Related blog post with example usage: Running an IPython Notebook on Google Compute Engine from Chrome
I use DigitalOcean for testing or hosting my apps. You can set up an Ubuntu server in less than a minute. There are also one-click-install apps, so I don't have to install e.g. the LAMP stack myself. The dashboard has a really easy UI and is easy to use. The costs begin at 5 bucks per month. Also DigitalOcean has a great support and an adorable community. They have a great support page with hundreds of tutorials.
Just started using EC2 myself, but it was the platform used by my previous employer, as well. They are getting easier to use, dashboard improvements over time were well done. Responded fast to outages. They offer a limited free tier which is perfect for my current project, allowing me time to build it to the point where I will need a paid solution. Overall, I'm liking it so far.
About a year and a half ago (written June 2013) we moved from dedicated servers over to AWS. Thanks to AWS, we no longer have to think on a server level. Instead, we think of everything as a cluster of instances, and an instance is essentially a virtual server where we don’t have to worry about the hardware. It’s a relief to not have to worry about the hardware behind the instances.
The clusters we have are: WWW, API, Upload, HAProxy, HBase, MySQL, Memcached, Redis, and ElasticSearch, for an average total of 80 instances. Each cluster handles the job that its name describes, all working together for the common goal of giving you your daily (hourly?) dose of image entertainment.
Below is a diagram of how they all work together:
- I use Google Compute Engine instances as flexible, reproducible infrastructure that scales with my data science tasks.
- Between Google Cloud and Amazon Web Services, I chose Google Cloud for its intuitive UI. SSH within the browser is very convenient.
- Related blog post with example usage: Running an IPython Notebook on Google Compute Engine from Chrome
We liked a lot of things about Heroku. We loved the build packs, and we still in fact use Heroku build packs, but we were frustrated by lack of control about a lot of things. It’s nice to own the complete stack, or rather as far down as AWS goes. It gave us a lot of flexibility and functionality that we didn’t have before. We use a lot of Amazon technology.
I like containers and all, but for zerotoherojs.com I am a one-man band, who also works full time. I don’t have any (dev)ops budget, and therefore I need the reliability and uptime of an actual virtual machine.
That’s where AWS EC2 comes in handy.
Docker containers will be hosted and run on a single Amazon EC2 instance. This will likely be the t2.small or t2.medium instance type as listed here: https://aws.amazon.com/ec2/instance-types/
DigitalOcean offers us everything we need to test out specific scenarios or we expect from small-servers like our monitoring-system. We also use digital-ocean in long-term and are very satisfied with their performance and scalability.
Because servers. Lots of them. Lots of configurations. Great for mission-specific functions. Video encoding, data aggregation, dedicated processing, mission-critical data stores. Anything you can't hang off your Heroku environment.
If not using managed hosting services like Heroku, AWS Lambda, or Google Cloud Functions, used to host programs because of ease of use and low cost.
Generally used less recently for these use cases than managed hosting services.
Because I like having more control of my deployment, I am currently hosting this on DigitalOcean. I don't need to worry about arbitrary row limits and I can be sure that the app is always running.
We use DigitalOcean to host our build tools (namely Drone.io) for a cheap CI and CD server.
We'll be using this to host the server application during alpha phase.
Been hosting with them for a while now. Never had an issue, great support, great docs: can't beat 'em. Though I'd probably move to AWS for large scale projects.
Infrastructure for Google App Engine, Google Cloud Endpoints, Memcached, and Google Cloud SQL components, as well as Git repository and Jenkins CI server.