|
|
|
|
PaaS for a LAMP service?
|
|
2 points
by majesticbeans
4587 days ago
|
|
|
Currently, I run a LAMP stack on a simple web hosting platform at $7 a month with a dedicated IP. I've decided to ditch them for various reasons. I've been told that launching a service with a simple hosting service is a bad idea and that I should use a PaaS to scale. While maintaining my online anonymity, my web service is nothing more than a simple upload service for all intent and purposes. There is no user-user interaction. The experience is as follows: log in, upload, view history. At least,that's how it will be for the time being. I also run a couple of cron jobs to send users reminders and to scan the DB for changes.
Although I expect my storage needs to multiply over time, I don't see why I can't just purchase more storage from my web hosting guys. Why do I need to use a PaaS, and furthermore, is Heroku something to look at especially if my whole website is written in PHP? I checked it out, and I have no idea what's going on on. Seems super convoluted. But then again, I'm a CS-gradguy just doing a simple side-project. |
|
|
The main benefit is: it's managed. You don't need to care about dependencies, updates, patches yourself. It's made for the needs of PHP web application development – continuous development, multi-staging etc.
We believe that the convenience we offer is more important than the few dollars (well actually Euro in our case as we are based in EU) you can save.
Curious what you think. Is it a fit? Are you missing something? Is it too expensive?