Vapor for everything?

I would go with Vapor for everything.

It makes sense to use Vapor for every type of applications, but not static websites :)

@themsaid are you here officially as a representative of Laravel team?

I'm representing myself here :)

@themsaid nice either way. Glad to have you here. Let's all mention Jeffrey to bump you up to top level :)

Vapor for everything?

Should still be discussed on a case by case basis with each client.

Meaning, AWS can be used without Vapor, so if the client is paying, let them choose, and disclose to them exactly what they are paying for.

I would cover several options with them. I've done some programming for a smaller non-profit and their budget was limited.

Just my opinion.

@themsaid I'm working on a SaaS that I (of course) hope is a success. Do you think it makes sense to just launch with Vapor from the start or wait to see if it's a success then move to Vapor?

Obviously it's easier in the long run to just start on Vapor but as a startup you're trying to minimize cost. From what I understand moving away from Vapor is pretty easy if you want to so maybe it's just as easy to wait and get on Vapor when the need arises?

Do you have any thoughts on all of this?

@realrandyallen I think that there are a bunch of cases where people reported that moving to Vapor cut down the expenses since you run only what you need while with VPS you always have to go with more overhead and power.

So best is to go with Vapor from start.

@bugsysha That’s a valid point - thanks for the insight

@realrandyallen

It depends. For example on a $5 forge server you can have your app + workers + database + redis cache + free LE certificate + more. Just for $5. On vapor you'll need to pay for an RDS instance + Cache cluster + lambda costs + APIGateway costs.

Vapor works very well if you're expecting variable load on your app, but if you don't expect so much load then the initial costs to host on Lambda is going to be much higher than a simple Forge server.

@themsaid Thanks for that info! I'm going to have to compare and see :)

@themsaid Do you know on average how much it will cost running all those services with low traffic application!

@themsaid On one hand I agree that it is possible to run all those services on a $5 plan. On the other hand I wonder if an application that really needs all of those additional services, like Redis cache, is so easy to maintain.

The wonderful thing about Vapor is, that I don't have to care about monitoring and updating the servers. And, if the application usage grows fast, I don't have to think about that too (while it probably will also generate enough revenue to cover the Vapor total. cost)

Plus, I can run not just one website, but several on the the same plan.

The wonderful thing about Vapor is, that I don't have to care about monitoring and updating the servers.

Indeed. That's where Vapor shines. Focus on the code not the infrastructure.

@mina as for the cost, it really depends. But the lambda costs are very low for low traffic/medium. Check this post https://divinglaravel.com/cost-performance-optimization-in-laravel-vapor

@themsaid thanks for sharing, I remember reading this post before. I believe things will make more sense once I start running an app on Vapor.