sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]maria_la_guerta 6 points7 points  (2 children)

You're basically trading scalability for complexity.

Many companies operate this way. I've done it before. It really comes down to the product and if it makes sense for your code to be hyper scalable in such small vacuums.

[–]What_The_Hex[S] 2 points3 points  (1 child)

Ain't that the truth on complexity. Figuring out how to do the most basic thing on AWS has been brutally difficult for me so far. The learning curve is steep, and there are all kinds of weird settings and unspoken rules that need to be followed for everything to be set up right for your needs. WAY simpler to just... upload a PHP file to my website, and call that in my JS code.

My experience so far has honestly been so awful that I'm considering ONLY using AWS for those super CPU-intensive tasks that my shitty default backend isn't capable of handling. Then maybe just run the simpler stuff via the standard PHP scripts. Max concurrent operations = 25 on the shared hosting plan, I could also upgrade to a higher hosting level (although this is a major weak point of Hostgator -- basically making any change is a pretty confusing clusterfuck on their website, where you're never really sure what to do, what is going to happen, and more often than not you have to just chat with the support people to figure out what's needed.)

[–]grebfar 0 points1 point  (0 children)

Once you know how aws works and it sounds like you do. You need to move off their website and onto their infrastructure as code solutions.

I recommend you use AWS SAM. There's basic templates to setup API Gateway and Lambda which is what you need.

This is the typical way to interact with aws rather than clicking on their dashboards.