I’ve just started a side project on it and it’s super great to be up and running quite fast.
But I’ve hit quite a blocker soon in the project when I realized I had to learn the whole AWS ecosystem VPC, NAT Gateway, aws logs, Cloudformation and the serverless project itself (which bref is based on) just to set up an aws managed database.
Suddenly, coming from the usual docker-compose stack, It felt like a steep learning curve to achieve my side project goals.
Got stuck a number of time during Cloudformation deployment in weird “in progress” states where it seems I couldn’t do anything other than wait till next morning or deploy a new stage.
Hopefully doc will provide serverless.yml template to cover those cases. I would really like mysql, redis, rabbitmq aws equivalent services setup for instance. In general, documentation form the point of view of devs that are new to the AWS ecosystem would tremendously help the adoption IMO.
Thanks u/mnapoli for this!
Vpc is biggest blocker for us too. It is so much work to get working networking same way as is fargate working by default. I really hope they will introduce something at reinvent next week
Those are very good points, and I completely agree with that.
These are very annoying details, and as mentioned VPC can be a steep learning curve. We’re brainstorming on that, for example sourceMappingURL=https://www.redditstatic.com/desktop2x/chunkCSS/IdCard.8fe90067a922ef36d4b6.css.map*//u/deleugpn has plenty of ideas (and knowledge) around VPC so hopefully we can make that part simpler.
Huh I’ve been hearing about this project for such a long time I presumed it was already at stable release. Cool and congrats to them!
Thanks! It was stable for production, I just never got around tagging a 1.0 because there never was a reason that was “good enough” ^^
Now that AWS starts promoting Bref itself, that we reach wide adoption and that we needed to transition to “Amazon Linux 2” (a technical detail without real impact on users), might as well do it now.
I’m currently launching my first site with bref. Been hugely impressed with how smooth the experience has been, it’s well made and works great in the AWS ecosystem. If you already building your app in a way that can scale to multiple servers (doesn’t rely on local files) there are almost no changes you need to make, and you get a lot of upsides with it.
Was interested in serverless and started out testing Vapor (building with Laravel). Did not like it for many reasons, deployment and security among those. I think the bref approach makes much more sense and recommend anyone interested in serverless to give it a try.
Brilliant work. I had the pleasure of watching your talk at the PHPUK conference in London at the beginning of the year and was really excited about it. My company had been turning away from PHP for microservices due to lack of serverless solutions and this opens up lots of possibilities
Why is serverless so popular?
Price, performance, scalability, quick deploys.
I don’t get it myself. Using any server less platform you through away
OPCache across instances.
A very low latency cache like memcached or redis.
shared file caches across the servers.
To me that leaves a heck of a lot of performance on the table (even for PHP). I guess this is the type of thing you just outgrow once your business starts to scale?
You already pay a big premium to use managed services, and then on top of that you are losing the ability to do some optimisations that can shave of 50%+ of your request time.
It’s a change of paradigm, instead of having a giant monolith backend, you split it into small chunks of business logic. And interconnect the micro services using tons of Async stuff like SQS/S3 triggers.
It’s way cheaper to run serverless instead of EC2 because instead of paying 24/7 for sometimes no load at all, you only pay for what you use (by chunks of 100ms).
The main issues for serverless architecture after I started playing with this are:
– testing
– lack of tooling
– lack of maturity
– no best practice (everything is too shiny new so everybody is trying to figure out what works best)
Serverless is best used for small standalone projects like refactoring a queue or spooler worker away from a monolith.
It’s very popular because you can hack something that works very quickly without caring about the shape of it or following a framework structure.
I have never heard of this. This seems interesting.
Yea ngl Vapor is burning a hole in my wallet, I will be checking this out.
Members
Online