Level 104
Based on the information provided, I believe you definitely should (or not) do this.
2 likes
Aug 27, 2018
6
Level 3
I'm making a parking system in Laravel
What do you think? The reason I'm choose to go with Laravel and not language like C#/Java is because I'm more close to Laravel.
Start to analyze and written some API, I feel like it's not difficult but I don't know about the performance.
Level 3
Level 16
Go ahead. Start building it. We're here for your queries.
Level 4
@GTHell I think he poked fun at you because indeed you gave no real info that anyone could tell you if it's a good idea or not.
Generally, performance doesn't matter. If you're caching everything with for example Redis, optimized your long-running queries etc you will be fine at pretty much any scale.
Level 3
Old system is VB.net and it's fail because of huge growing record of SQL. I'm planning to use Redis for caching which will be fine for day to day operation.
The first problem that pop up in my mind is query the relationship table. Well, I might need to find a way to get all the necessary without querying everything.
I analyze and decide to make 3 sub system. One for checkin, one for checkout and one for centralized. The checkin will do the heavy lifting like reading plate number with python and use web protocol to create new temp record in Laravel central server. The checkout system is the most challenging because there're many condition the user want and hence it need to query 3 tables and processing the result and all of this need to be done on central server that running laravel.
I will test it and share the result. If it that bad then maybe I just switch to other language since I wrote most of the logic and schema already.
The thing I'm not familiar with is measuring the speed back and forth from server. eg. From checkin system -> server -> checkin system -> print ticket out. I'm on intranet if that help.
Since, the process is one at a time, I think everything will be fine. The maximum operation can occur at the same time is only 2 because only 2 vehicle can checkin and checkout at the same time. I don't think it will break the system.
Everyday transaction is around 5000 according to the user.
Level 4
It's a very interesting project. Volume sounds very low, you shouldn't have any issues, I have ran Laravel installs that weren't highly optimized with just Elasticache in front of it and had up to 100K daily visitors without breaking a sweat.
I think performance will be your last issue, you should think more in terms of how compatible your technology stack is for this project.
Performance wise, really, imho no issues with 5K tickets per day that need processing
2 likes
Please or to participate in this conversation.