The Datenna tech test is designed to allow you to show your strongest skills and
make things as simple or complex as you want.
We want you to create a webserver that serves a simple web page:
- The first time it is accessed it shows the string “Hello” and the next time “World” and then flips between them each time it is visited
- The service/setup you create should be able to be hosted locally or on Kubernetes
- It should be easy for someone to delete and re-create it as needed
- Please provide a link/GIT repo where your code can be downloaded
- Aim to spend 1-2 hours on this
This implementation pushes all logics to the client: no server-side burden.
I will use a cookie to store the current "status", that is the string to be displayed:
- read it (if it exists),
- display the relevant text,
- update the cookie for the next load
This is the simplest implementation I can think of.
Unluckily, this part only works with Firefox (I am on v127.0.1) as other (chromium-based) browsers seem not to handle cookies set by local HTML pages.
I think this is due to the missing "hostname" concept. Not a real problem here as we are going to use an HTTP server anyway.
I will use a simple docker image to run NGINX and serve that page.
By doing so i will be able to run it anywhere a docker container can be run.
Also locally, as I am using a Linux machine with docker v26.1.4.
On macOS is basically the same.
On Windows ... use the Force/WSL, Luke!
In the repository main directory run:
docker build --network host -t datenna .
The --network host is needed to make sure apk can access the internet!
docker run -td -p 8080:8080 datenna
Point your browser to one of your IP addresses, HTTP protocol, port 8080.
In my case I have http://192.168.255.42:8080: YMMV.
Hitting F5 or refreshing the page will show the flipping.
Visiting the service/page from another browser or completely new session will "reset" the flipping status!
It's the cookie, baby, the cookie, and there is nothing you can do about it!
I am not doing this now. The idea is to have a server application and status. We'd need some runtime (like Node.JS and the likes) and a persistent status storage (like a DB or even just a file).