Need advice about which tool to choose?Ask the StackShare community!
Google Compute Engine vs NATS: What are the differences?
Google Compute Engine: Run large-scale workloads on virtual machines hosted on Google's infrastructure. Google Compute Engine is a service that provides virtual machines that run on Google infrastructure. Google Compute Engine offers scale, performance, and value that allows you to easily launch large compute clusters on Google's infrastructure. There are no upfront investments and you can run up to thousands of virtual CPUs on a system that has been designed from the ground up to be fast, and to offer strong consistency of performance; NATS: Lightweight publish-subscribe & distributed queueing messaging system. Unlike traditional enterprise messaging systems, NATS has an always-on dial tone that does whatever it takes to remain available. This forms a great base for building modern, reliable, and scalable cloud and distributed systems.
Google Compute Engine and NATS are primarily classified as "Cloud Hosting" and "Realtime Backend / API" tools respectively.
"Backed by google" is the top reason why over 86 developers like Google Compute Engine, while over 13 developers mention "Fastest pub-sub system out there" as the leading cause for choosing NATS.
According to the StackShare community, Google Compute Engine has a broader approval, being mentioned in 594 company stacks & 429 developers stacks; compared to NATS, which is listed in 26 company stacks and 12 developer stacks.
GCE is much more user friendly than EC2, though Amazon has come a very long way since the early days (pre-2010's). This can be seen in how easy it is to edit the storage attached to an instance in GCE: it's under the instance details and is edited inline. In AWS you have to click the instance > click the storage block device (new screen) > click the edit option (new modal) > resize the volume > confirm (new model) then wait a very long time. Google's is nearly instant.
- In both cases, the instance much be shut down.
There also the preference between "user burden-of-security" and automatic security: AWS goes for the former, GCE the latter.
Pros of Google Compute Engine
- Backed by google87
- Easy to scale79
- High-performance virtual machines75
- Performance57
- Fast and easy provisioning52
- Load balancing15
- Compliance and security12
- Kubernetes9
- GitHub Integration8
- Consistency7
- Free $300 credit (12 months)4
- One Click Setup Options3
- Good documentation3
- Great integration and product support2
- Escort2
- Ease of Use and GitHub support2
- Nice UI1
- Easy Snapshot and Backup feature1
- Integration with mobile notification services1
- Low cost1
- Support many OS1
- Very Reliable1
Pros of NATS
- Fastest pub-sub system out there22
- Rock solid16
- Easy to grasp12
- Light-weight4
- Easy, Fast, Secure4
- Robust Security Model2
Sign up to add or upvote prosMake informed product decisions
Cons of Google Compute Engine
Cons of NATS
- Persistence with Jetstream supported2
- No Order1
- No Persistence1
Sign up to add or upvote consMake informed product decisions
What is Google Compute Engine?
What is NATS?
Need advice about which tool to choose?Ask the StackShare community!
What companies use NATS?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with Google Compute Engine?
Sign up to get full access to all the tool integrationsMake informed product decisions
Blog Posts
+32
+31
+34+35