To make it quick: Since you are not a real sysadmin with enough knowledge, hire a professional sys admin or an certified AWS admin. If you have the $, go for AWS since AWS lets you create your very own datacenter with all the features of aws.
Forge vs Heroku vs DIY - AWS
I'm working on the backend for a fairly complex iOS application. We're ready to go into our beta launch I'm trying to decide which route to as far as server mgmt and deployment.
As of now, I'm using Laravel Forge (Digital Ocean) with Envoyer, and a custom Python Script to get everything setup on each box. On Forge, I currently have the following servers:
- 2 Application Servers - 2GB Ram / 2 Cores (iOS facing Applicaion, and a Admin Application)
- (2) DB Severs - 1GB Ram / 1 Core (theres 2 databases)
- (2) Worker Servers - 2GB Ram / 2 Cores
With this setup for development / staging, we've gotten pretty solid performance and quick response times. However, there's several things I know I would still need to setup:
- Load Balancers
- DB Redundancy
- Maybe a Cache Server
That being said, all of this on Forge is pretty affordable. However, I am not a sysadmin and I want to make sure I'm in a position where we can scale easily if needed.
I tried out Heroku the other day, which was somewhat easy to setup, but its very expensive to get anywhere near the same performance and seems somewhat restrictive (you need to do things their way, and thats it). But they do take care of all Load Balancing and Caching, and it's easy to setup DB failovers.
Im wondering what people's experiences have been? I've read article like the one below where people have left Heroku and rolled their own AWS environment: http://www.holovaty.com/writing/aws-notes/
And while that sounds enticing an potentially more affordable, I'm not confident enough as a sysadmin to ensure that I'm not missing any security loop holes and such.
Has anyone done any proper scaling with Forge?
Please or to participate in this conversation.