- Visual Studio solution.
- No front end or UI.
- Back end logic for a user.
- C# code for the game: https://en.wikipedia.org/wiki/Battleship_(game)
- Spent lot of time crafting the code.
- Implemented as an Event Sourcing (CQRS) pattern as I feel it's good approach in this case.
- The console project might be easy way to run the code and test the main logic.
- Since lot time spent in coding, test cases are written around the core logic of loading ship on board.
- I feel there are lot of improvements can be done. There might be un-tested code having bugs. Concurrent execution is not handled.
- Memory just stores everything, no restrictions on how many games to store. Since its in memory when redeployed all the data will be lost.
- Number of ships alloted to game is set to one as it was easy to test, can be modified.
- I have included: BattleShip.postman_collection.json and BattleShipEc2Deployed.postman_collection.json Postman collection to test the API as I couldn't detail the spec.
- Deployed on EC2 instance: http://ec2-3-25-255-129.ap-southeast-2.compute.amazonaws.com:55201
- Loader is only used in case HTTP (WebApi).
-
Notifications
You must be signed in to change notification settings - Fork 0
shishirajm/BattleShip
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Folders and files
Name | Name | Last commit message | Last commit date | |
---|---|---|---|---|
Repository files navigation
About
No description, website, or topics provided.
Resources
Stars
Watchers
Forks
Releases
No releases published