We make a ERP solution for a ecommerce organization.
Solution include ware house managemnt , POS management , website , admin portal
All modules are linked with admin portal through API (curl on every request),
We aspect average 2 , 3k users every time on website..
And on sales days its goes to 10 15k users.
Is this system(API base) handle this stress ??
@martinbean a website which have direct linked with database is better or a website which get data through curl request from another sub domian where admin portal is placed is better??
@NadeemAkhter You’re really not making a whole lot of sense.
How on earth do you think making a request to your app, and then making the user wait whilst your app makes yet another network request to get some data, “better” then just fetching data from a database?
Where is the second service that you’re making a cURL request to going to get its data from? Oh, that’s right. Most likely a database. You’d just be adding latency to all app requests for absolutely no gain whatsoever.
@NadeemAkhter API verses a regular web database will depend on what you are doing.
Company database = regular
Serving something like weather = API
Or mobile can either be mobile friendly or API depending on what is being served. Most of the API's I've seen questions on here do not need to be an API.
I would say learn what an API is and usage. I have in the past used Adopt a pet API for a Humane Society, that is a use case for an API.
In house bookkeeping for the Humane Society Is Not a use case for an API.
If having to ask, you probably do not need an API.