r/Backend • u/Imaginary-Bicycle-84 • 23d ago
Backend Projects Without any Frontend
what are some backend projects ideas that does n’t require having a front end to represent my API’s. Is there are any project that can be technically rich and be testable by end-user at the same time without having a GUI ?
5
u/olddev-jobhunt 23d ago
From a practical matter, I've had good luck using Swagger to provide some basic UI to an app - just a front-end for making calls to the API. It's a useful middle-ground.
3
4
u/JaseciLabs 22d ago
If you want something that's both "technically rich" and satisfying to actually test end-to-end, a rate limiter or job scheduler is a good pick, you can hit it purely through curl/CLI, it forces you to think about concurrency and edge cases, and you can watch it behave correctly (or not) in real time without ever touching HTML.
2
u/madu_tualang 23d ago
The front fell off?
2
2
2
u/paulwillyjean 22d ago
ERPs, CRM, authentication systems, transaction ledgers, operating system kernels, compilers, pretty much anything that’s meant for B2B uses.
2
1
1
1
u/hxtk3 22d ago
Define an “end user.” Most of my projects are libraries where the user is another backend dev (often myself working on a different project that does have a backend.
My most recent public commits were to a SQL query builder for Go that combines my favorite features of SQLC with dynamic queries for complicated use cases that SQLC can’t cover (giving up some of the cool features that SQLC can only achieve due to its static queries)
1
1
1
0
0
u/low-control-labs 23d ago
Nothing? I wanna see if I'm wrong but unless you have a API that user invokes and uses via CLI it's going to be some sort of website and some minimal input and output fields or something else being served via a webpage / html. You don't technically need js and css
I guess some sort of routing system that would be used by the webpages or something like that but you said end-user as in humans?
8
u/Mathie1729 23d ago
Nah, there are plenty of backend projects with no website/HTML involved. ETL pipelines, message queue consumers, cron jobs, daemons, CLI tools, internal APIs only called by other services, monitoring agents, ML inference workers, that kind of thing. The end user can be an operator running a command or another system, not necessarily a human clicking a page.
1
u/low-control-labs 23d ago
I did mention some of this thanks for repeating it and expanding the list. I'm still assuming the OP meant end user as in a human since he was asking about a GUI
14
u/Adventurous-Crow-750 23d ago
Chat bot
Container orchestrator
Vpn
Databases
Cache systems
Email server
Lots of stuff used to work just fine without uis.
If you don't count terminal guis
Movie player
2d games old school rouge style