In less than 2 hours I had auth'd https rest endpoints up and running with logging.
Deploying new endpoints is as easy as exporting a function in my code and typing deploy on the command line. This isn't after some sort of complex configuration, it is after creating a new project via 1 cli command that asks for the project name and not much else!
Google's cloud stuff, especially everything under the Firebase branding, is incredibly easy to use. Getting my serverless functions talking to my DB is almost automatic (couple lines of code).
Everything just works. The docs are wonky in places, but everything just works. The other day I threw in cloud storage, never done cloud storage before, had photo hosting working in about an hour, most of that being front end UI dev time. Everything fully end to end authenticated for editing and non-auth for reads, super easy to set that all up. No confusing service names, no need to glue stuff together, just call the API and tell it to start uploading. (Still need to add a progress indicator and a retry button...)
Everything about Google's cloud services has been like that so far. While I regret going no-sql, I can't fault the services for usability.
And you could do the same thing with lambda/DynamoDB/API Gateway just as easily by using one of the wizards.
What you can do as a hobby project is much different than the parent poster who was trying to deploy an enterprise grade setup with an existing legacy infrastructure. How would you know if GCP is easy based on your limited experience? Not trying to sound harsh, as well as I know AWS, I would be completely loss trying to manage any non AWS infrastructure. Just like I said about the front end in my original response, if I were responsible for setting up a complicated on prem or colo infrastructure from scratch, I would hire someone.
“It’s a poor craftsmen who blames his tools”.
A guy that works with us was also an inexperienced back end developer except with PHP. He was able to easily figure out how to host his front end code with S3 and create lambdas in Node after I sent him a link to a $12 Udemy course. I only had to explain to him how to configure the security groups to connect to our Aurora/MySQL instance.
I can't really explain how easy it is. There are no hidden charges, monthly usage is easy and clear to understand. For small to medium sized apps there isn't even any configuration. I'll be throwing tens of thousands of users, tiny I know, on a service that had 0 configuration done beyond typing its name. In fact I'm 100% sure my VMs on DO are going to give under load first.
To put it another way, there is a healthy industry of people whose sole job is to come in and figure out why AWS is billing too much.
FWIW I showed one of my friends at Amazon how easily I can create and deploy serverless code on Firebase, he admitted it is far easier than what AWS offers.
The downside of this is that options are fewer. If I want a beefier VM my choices are limited, and the way pooling and VM reuse is done is well documented and not at all under my control. It is like cloud on training wheels (TBF to gcp it is possible to opt-in to more complexity for many services, but the serverless function stuff is pretty bare bones on options, arguably as it should be)
But take auth for example. Firebase auth is amazing. Using it is beyond simple, and within the Google ecosystem everything just works so well.
Guess what? Do you really think that there aren’t GCP consultants for any serious development?
Lambda, cognito, api Gateway and DynamoDB is dead simple.
You’re not doing anything complicated. Just because you can set up a little hobby project doesn’t mean it would be any simpler for a real enterprise app.
The number of users as long as the Serverless offerings from cloud providers has everything you need isn’t complicated based on the number of users. All Serverless offerings are optimized for this.
There are also WordPress consultants, does that mean that Wordpress is complicated or that there are people without the capacity (time not intelligence) to learn it.
You don’t have to “explain” how easy it is. The Node tutorial I use to learn it used Firebase.
“Millions of people use AWS” you say in a thread where people are complaining about AWS’s poor usability linked to a comment thread on another site where even more people are complaining about AWS’s usability.
The biggest and best rebuttal against your comment is the mere existence of every other comment in both of these threads.
Yes because an HN thread with 236 comments including people who know what they are doing is representative of anything.
Would it also be proof that React is an unusable framework just because I haven’t taken time to learn it even though millions of people use it everyday?
You can find “rebuttals” about the safety of vaccines on the Internet. Does that mean anything?
Literally millions of people use AWS everyday. So what’s more likely that the issue is with AWS or the implementer?
It took me watching one Pluralsight video to map what I knew about an on prem implementation to AWS. Of course I learned more as I went along.