|
|
|
|
|
|
by tieTYT
4305 days ago
|
|
|
This is on Google Compute Engine, not Google App Engine. It's not straight forward to me what GCE is a good fit for^1. Can someone explain in layman terms? Based on the name, I'd think it be for long running concurrent algorithms that require many resources, but the M of MEAN is throwing me off. Why do you need a persistence layer? Is it to load the data for input? To store the data as output? Is it for anything you want? If the latter, why can't I use this exactly as I'd use GAE? 1: https://cloud.google.com/products/compute-engine/ |
|
|
GCE is a pretty standard IaaS offering, like Amazon EC2.
> Based on the name, I'd think it be for long running concurrent algorithms that require many resources
There's lots of things an IaaS like GCE can be good for; what you are doing with it will determine what size instances you use, and what options you use with them. Certainly, that's one thing GCE could be used for.
But an open IaaS like GCE or EC2 is designed to be a general purpose on-demand dynamically-allocatable server solution, so anything you can use a general purpose server for is an in-scope use of the IaaS.
> If the latter, why can't I use this exactly as I'd use GAE?
You can. An IaaS like GCE is lower level tool on which, with an appropriate software stack loaded (which MEAN might be), you can use the system basically like a PaaS like GAE. The difference is that a PaaS already comes with a particular software stack included, rather than requiring you to bring your own (that's the "platform" in the "platform as a service".)