Be part of JetBrains PHPverse 2026 on June 9 – a free online event bringing PHP devs worldwide together.

cooldude's avatar

I am going to use Laravel for a very big project. What should I pay attention to?

Hi! I am going to use Laravel for a web platform that is going to be used by hundreds of students in my University. Without entering into a lot of details, this will be a kind of projects submission platform, with online homework, exams, results consultation, etc., and it will also be used as a relay between the user and other (virtual) machines on which they are going to make some programs run. Do you have any advice for me? Something I should know about Laravel in this situation? Especially in terms of security and load of users connected at the same time. Maybe some mistake

I know this is a pretty general question, but all tips are welcome. Thank you!

0 likes
6 replies
jlrdw's avatar

Watch the laravel 8 from scratch series to start with, just suggestion.

2 likes
cooldude's avatar

@jlrdw Already did, and I agree, it's a very good tutorial. I recommend it too! Thanks.

1 like
drehimself's avatar
  • Having tests will help you maintain your codebase as you continue to build it up and add more features.
  • Having a server setup properly with a good deployment strategy (git repo -> staging, production). Can easily scale if needed.
  • Rely on third-party services to make your life easier (mail services, realtime (pusher), uptime monitoring, error tracking, etc).
  • Making sure frontend assets are optimized
  • I'm a sucker for a good-looking UI and a good UX. Work with a designer or use existing templates.
  • Use a good project management tool to keep track of what needs to be done.
  • Don't stress out too much, you'll learn as you go.

Good luck!

4 likes
martinbean's avatar

@cooldude Follow Laravel’s conventions and don’t get sucked into believing your application is a special snowflake and needs some special architecture.

I’ve worked on probably hundreds of Laravel projects now and the ones that have ended up needing to be rewritten or grown unwieldy and a pain to work on are the ones where developers had decided to do something like DDD or hexagonal architecture.

Stick to well thought out models, resourceful controllers, policies for authorisation and form requests for validation, and you’ll find your application is easy to reason about and navigate.

4 likes
Tray2's avatar

Since it will be a data heavy application you need to have a good database design. If you don't you will have performance problems.

  • A good database design
  • Indexes for your tables
  • Never do something with php that you can handle in the database with SQL
  • Use a tool like debugbar to find n+1 issues

And the most important thing is to try to KISS (Keep it simple stupid). Many developers over complicate things more than necessary.

4 likes

Please or to participate in this conversation.