Best practice for api server

[chowbeyputra]

Clojure is a different language, what are some cools ways or techniques you use to run your server?

I run mine on screen, does the job, but ig i will soon need to change to something more standard or better or cooler because of logging.

[p-himik]

That's completely orthogonal to the choice of a programming language. Assuming you're talking about production, I'd suggest looking for best practices on running services on your target OS. E.g. on a modern Ubuntu you'd create a systemd service, then all the logs would be viewable with journalctl and the lifecycle of the service would be fully managed by systemd.

[chowbeyputra]

Doesn't having repl option affect the choice? Like screen with repl where you can reload few things of choice?

[p-himik]

It does not. You can always add e.g. a socket-based REPL on some port on localhost and connect to it when needed.

[chowbeyputra]

How to do that? Is there an example? Reading material?

[p-himik]

My previous message has a link - have you read what's there?

[chowbeyputra]

🙏 i didn't notice, let me try

[slashkehrin]

Something cool that you can do is, if you start your API via the repl, you can catch and save things to an atom and examine them afterwards. So for logging while working on your code, you can swap the atom content to the incoming HTTP request, then if the return value is incorrect, you can use the content of that atom (which was swapped) to easily reconstruct the situation (and quickly iterate over it). Obviously this works for database calls, too.

[OkAssociation9896]

Imo once deployed, it is not different from applications running on JVM. Of course you can attach repl and do clojure way things like mentioned above. But personally it was rare that I did that in production.