The new social network Bark has taken the world by storm. What started in the basement of a dog has now become the most viral sensation of humans.
For the first time dogs and humans are able to interact with each other. In the next 5 days the platform is expecting to attract more than 1million users barking at each other. Is the system ready to grow that much and handle that load? Are there any bugs that need to be fixed? Is the codebase ready so that the development team can scale? Are there any security vulnerabilities that need to be handled?
Your coding prowess is needed to ensure our platform is wagging its tail in joy!
1. php artisan migrate
2. php artisan db:seed ( will take a while )
Project has been setup to start with sail easily but using sail is not a requirement.
Our barkers have shared some "ruff" experiences.
- Barkers have reported that the site is slow, specially for users with high number of friends. The platform should be optimized for reads. We want to make sure that a bark will eventually be displayed to your friends feed. Refactor the code so that the friends feed generation has the same response time no matter how many friends or barks a barker has.
- Barkers have reported that when you have many barks either in your home feed or in your friends feed the data consumption is realy high. Refactor the code to reduce the amount of data is sent. Barkers usually see the first 10 barks in their feed and are not usually scrolling to the bottom.
- Barkers have reported that the error message ("Input is invalid") displayed when the submitted bark is invalid is not very helpful. How can we improve there and display what actually went wrong with the submitted bark message?
- Some times when a back is created it fails with a 500 error message. It seems the problem is in the database schema.
- There seems to be a way for users to tamper with their friends feeds. We shouldn't allow that. Somehow some barkers are able to execute code in their friends feeds.
- Mew_social, the rival social platform that is full of mewers have leaked some data about our current user growth. It seems they have found a way to scrape our data and see the exact amount of barkers that are signed up. How can that be? Can this be fixed asap?
A new engineer got in the team and is really not pleased with our current codebase. He said that too many things happen in the controllers and that we are not taking advantage of laravel features even in routing. If there are any improvements in structure or separation of concerns, you are more than welcome to execute them.
- A bark cannot be more than 500 characters
- A bark must be at least 4 characters
- If the bark message is 4 characters then it can only be the word "Bark"
Ensure that all these conditions are met!
- You are free to add or utilise any extra database that you may need in order to optimize the platform for the expected high feed reads.
- There is no authentication for accessing a user and writing a bark. This is so that you can test easily. Authentication is not part of the exercise and is not related to the security vulnerabilities ( 5 and 6 ).
- The home page (UserController@index) is not part of the exercise. It exists so that you can test easily. It is not part of the exercise and is not related to the security vulnerabilities ( 5 and 6 ).
You should fork the project and submit a pr with your changes when you are done. In your pr you should explain the updates you made, the optimizations you executed and anything that you believe should be outlined based on your solution
Good luck :) Or as our barkers say Bark bark, bark Bark!