Fixed size databases that can run on MYSQL 8.0 are somewhat faster but they don't scale automatically. The serverless database runs only MYSQL 5.7, is slower and costs more but it scales automatically. With RDS you can choose a "serverless database" or a fixed size database. In my opinion the only two tough decisions you have to make are about the RDS database and the cache instance. Especially considering that a "jumpbox" is actually a "t3.nano" EC2 instance which costs next to nothing and that a NAT gateway costs about 30 USD per month. You could remove the NAT gateway and the jumpbox but that would mean your database would be public. Initially when you create a project on the Vapor dashboard you need to spin up quite a few resources: a VPC network, a NAT gateway, an RDS database, a cache instance and a jumpbox. Don't get scared by the amount of resources needed If you are however developing APIs or are working with webhooks you are in for a treat - Treblle will make debugging and logging those a breeze. So just like me, you have to get used to it. Yes, there are Cloudwatch logs, Vapor deployment logs but anyone who ever opened the Cloudwatch dashboard knows how scary that is. When an error happens it's not as easy to debug it and it's not as easy to fix it. This has nothing to do with Vapor of course but rather the notion of running on Serverless. Prepare to lose some controlĪs an "old school guy" being able to FTP or SSH into a server and quickly debug or fix a problem was the part that bothered me most. Here are a couple of things that I wish I knew before starting my Laravel Vapor journey. Just like with everything else I watched it from a distance, read articles about it, watched videos and then I decided to move Treblle to Vapor. So naturally, when Laravel Vapor came out I was stoked. Not a pretty process if you ever tried it. As the rest of the world moved into severless with AWS Lambda we (PHP developers) were stuck with defining thresholds to launch EC2 instances using load balancers. Everything from deploying code, configuring load balances, connecting to database servers, VPCs, scaling rules.I always found that part boring and overwhelming. Not because it was impossible but rather complicated and time consuming. The only thing that always worried me about PHP was scaling it. I started with a split between Lumen and Laravel but quickly decided to make it all run off one single code base. Platforms that handle 10 TB of image data, a couple of million API requests per day, a database of a few GB in size with millions of records.In light of that I've decided to build our entire platform, Treblle, on top of Laravel.Įverything from the website, API to complex processing flows that actually handle all incoming logged requests. Hats off to Taylor □!Īs my love for Laravel grew I got the chance to battle test Laravel on many real life projects. All in all probably the best career choice I could have made was learning Laravel. The second thing that I was obsessed with were Queues. It felt revolutionary that I could write the entire SQL schema in PHP and be able to track table changes in GIT. What attracted me the most were migrations. I watched people use Laravel for at least a year before developing with it in version 5. You get the basics but you can still do whatever you want without much hassle. I discovered Bootstrap on the brink of the responsive design revolution and loved it ever since because it wasn't trying to do much. The only ones that caught my eye were Bootstrap and Laravel. I've also lived through many many frameworks and boilerplates that make your job as a developer easier. It felt like magic to me.Īs time moved on I learned HTML/CSS/JS, Linux server management, AWS, fancy new tools, overly complicated and "modern" ways of developing things. From the moment I created my own makeshift CMS I fell in love with it. Given that I'm 33 now it means I have a solid 18 years of PHP/MYSQL development behind me. I've been working in the PHP ecosystem since I was 15 years old. Before we dive deeper into Laravel Vapor allow me to set the stage for you.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |