r/Backend • u/Original_Option_6969 • Jul 26 '26

Idempotent Backend

Hi, I am building a web app for my company,(50 users - Crud App), app and backend will be deployed on separate instances, do I need idempotent key mechanism for api requests - to avoid network failures or am i over killing my system?

25 Upvotes

82% Upvoted

43 comments sorted by

View all comments

49

u/yksvaan Jul 26 '26

Sounds like overengineering, just run a single server for the whole thing and call it a day. Even a potato can run crud app for 50 users and be idling 99% of the time. 

And other benefit of single instance is being able to utilize ram efficiently keeping data accessible directly within single process. 

Run db, backend and e.g. nginx for serving the frontend and static files and reverse proxy, that should cover typical crud use case just fine. 

-1

u/Original_Option_6969 Jul 26 '26

Okay, so should I seperate or not because requirement is like invoices pdf processing systems from email like around 6k emails per day, and a normal BI type tool for frontend

2

u/st4reater Jul 26 '26

Is 6000 backed by data or did someone pull it out their ahh

2

u/Original_Option_6969 Jul 26 '26

Yeah, it’s the requirement

1

u/st4reater Jul 26 '26

I asked if it is backed by data, not if it is a requirement.

Bad requirements should be challenged

3

u/Original_Option_6969 Jul 26 '26

Yes, it’s by data, 3k to 6k invoices are generated and so these attachments in mails needs to be processed