Vapor - Taylor Otwell presentation

Very promising 😎

What are your thoughts guys? Lambda cost is very small but what are other costs associated with this structure?

1. SES - mail
2. Database
3. Cache
4. Queues
5. S3
6. SQS - queues

Seems like all of that will be separate charge. How that might add up?

Wow - this seems amazing in many respects, so I can take any laravel app, load it up into Vapour and take advantage of lambda without doing anything else? That is magic - I mean how?

Curious as to complete costs too - if it works out cheaper than $5 a month as suggested in the article then it seems like a no brainier!

... but, and maybe I am old and grumpy, but 'serverless'??? If there is no server how is anything ever served? Something somewhere must be serving something!

Seems to me like this is a lot of little servers each one doing their own little thing, I think it needs a better name!

but, and maybe I am old and grumpy, but 'serverless'??? If there is no server how is anything ever served? Something somewhere must be serving something!

https://mattstauffer.com/blog/introducing-laravel-vapor/

Funny I had this back in 2006, all I did is send a war file, the professional company we used took care of the servers. This is nothing new. Perhaps lower cost now.

warning:

Still backup the data your self. Never trust a Host (no matter the host) to have backups you need.

I guess if many use vapor it will cut down on server questions here on the forum, Haha.

Serverless in 2006. Ok.

Heh, I only said that as a precursor to the suggestion that it needed a new name ;)

Price is $39/mo, $399/year (plus all your AWS costs).

I don't think I will be convincing any or my clients that this is a good deal any time soon, maybe it makes sense with very large numbers of users, but definitely out of my scope.

Still... very interesting and good to know.

Serverless in 2006. Ok.

You realize there are really servers, right. (I know you do). Oh wait code floats in the clouds.

Do you know where the term cloud for computing came from, I will give you a hint it was during World War 2.

Do you realize that term is just a word that one large company starting using again several years back, suddenly many companies re-coined it.

Web database and cloud database are the same, but since the term "caught on", companies suddenly advertised:

"Cloud computing"

Been around since WW2 folks. Even had internet back then, but only for military and scientist.

Okay, playing devils advocate a little, did you pay for your server in 2006 with a monthly/annual fee or did the hosting company only charge you when it was used and only on a call by call basis?

Actually to correct that, it would be a standing charge for no use, then on a call by call basis!

I am also curious about the WW2 reference, I didn't know this, got a good link to share? I had a quick search and didn't find anything in particular.

Cheers :)))

See next to last answer here: https://stackoverflow.com/questions/2616427/why-is-it-called-cloud

And the article referred to has been changed since. But there was an old photo at one time of a scientist who had drawn a picture of the network being used, and made a statement it reminded him of clouds. I can't find now that ww2 reference, but it came up again in the 60's.

And

https://www.businessinsider.com/best-larry-ellison-quotes-2013-4#cloud-computing-maybe-im-an-idiot-but-i-have-no-idea-what-anyone-is-talking-about-1

Basically saying "re-coining a term" sales, wow, wow, wow. See how he compared it to "fashion".

Folks, come on. But this is a good articles, talking about the "same technology", just a re-name.

But what you are talking about, is not what they are talking about, as usual. Apples and oranges, despite your usage of buzzwords that I never used so you can make a big long post. Maybe you should read up a bit more on lambda and autoscaling before commenting further. "cloud computing" lol. I never mentioned that buzzword. Your whole post is talking about stuff I never mentioned.

@jlrdw

You asked recently why forum members single you out. This is why.

A 4 word post triggered you, once again, into typing long irrelevant rants that nobody cares about.

You are hijacking a thread with complete nonsense. Please stop.

Anyway... :D

Is there anyone here for whom this makes financial sense and is willing to share breakpoint figures? Or anyone who knows AWS well enough to be able to take a rough guess?

I am just curious, this is purely out of interest and I guess to make a kind of mental note in case any projects I work on reach these figures.

Yes I admit

Serverless in 2006. Ok.

Got me. Thanks @cronix I'm better now.

is it $39 per instance, or like forge, you can publish many sites under your account?

@snapey It appears to be like Forge, at the bottom: https://vapor.laravel.com/

"unlimited projects, unlimited deployments"

so I guess the challenge for developers like @kel_ is whether they want to provide a managed service for clients or get the client to pay hosting costs and just publish the site to their server

This is the strange thing about Lambda, it can be pennies to run your site if traffic is low, but really its aimed at big traffic sites where $39/month is trivial

I'll have to look into this more when I have time, but it seems like it might be useful for us. Our main app is running on 5 medium sized web servers behind a load balancer, connected to external db/redis instances. I might be able to eliminate a lot of that infrastructure. The thing with all of this AWS stuff though, is it's pretty hard to get an accurate cost before taking the plunge and actually trying it. I don't think any of our initial quotes or "cost calculators" were accurate once all was in place, set up, and actually being used. We generally add 30% to what they say and it's closer to reality when we get the bill.

Just back to the hotel after the second day of Laracon. What a blast!

As a Heroku customer, Vapor looks really interesting to me. Especially the $39/month price tag.

On first mention, I balked a little at that price point, but then considered that it is a one-off charge and I can host unlimited applications for that charge. Weighing up that I have multiple Heroku apps with at least two $7 dynos each (web and worker), then it looks like Vapor may work out cheaper than Heroku for me.

So looking forward to getting my invite, running an application on there for a month or two and seeing how the cost compares. I’m already using SES, SQS, and S3 in my applications. I just need to see how the other costs (database, Lambda function invocations) compare to the ~$17/month I’m paying per app on Heroku.

@martinbean I had some issues with AWS billing and this really is my only concern. They will charge you for everything and as Lambda might be close to nothing and also able to handle the spikes some other services like RDS and connections between them might generate some fixed costs.

It looks definitely like a tool to use when your customer plans to make TV appearances all right ;-)

@martinbean thanks for letting us know about your upcoming comparison. Your findings will be highly appreciated. 👍

Laravel is so awesome.. the reason I chose php. 😎

hi guys, can we use another queue driver in Vapor? as Amazon SQS has limitation for delaying send the message at maximum of 15 minutes.

Thanks