IP address tracker app

What are you most proud of, and what would you do differently next time?

I design this with clean architecture in mind : while not perfect, I try to combine less api call whereas I continue to show explicit use cases and using modules (that group several business cases with coherently). I isolate nextjs to avoid coupling too much react/nextjs with my business logic so that it is reusable and easier to test. I have done some unit tests (it lacks a lot of tests as integration tests and so on). I try to create a infra that minimize api call while I can have if needed a fine grained api calls by items in case it become useful.

I think I must improve my architecture to suppress unused folder/files. I also need to improve validation of the ip address as for now it is the bare minimum (no string manipulation to check format).

I use only one type of IP, I don't bother for now for every variants.

It is still a work in progress.

What challenges did you encounter, and how did you overcome them?

I wanted to get a ip address locally to test it but in a localhost I need to use external tools as the one provided by ngrock or may be nginx. I didn't want that so I directly use vercel for simplicity but this method is not ok in a real professional project as we have a limit in api calls. For the location part, I decide to test with ip address I am sur to know the location instead.

What specific areas of your project would you like help with?

---> I wonder how to improve my performance using nextjs : the use of a cache utils could be could, especially the new use-cache util and deciding the cache life, using a cache tag and so on... I want to implement this and I am curious in any advices. ---> My clean architecture could be improved and is not really finished at every aspects : I would like to have advices about this.

Be careful : I create a way to know if we hit the credits limits for the api so you could arrive on this website when there is 0 credits left (UI will let you know).