Sorry to spam but thinking of examples as they come through.
This is actually based off a chat with Stephen at Fuel which we just realised...
The scenario:
You got some API work going on with the Web app of a website going to something else.
Your client goes over 1k items in their web app and day to day managing of their site and that web app.
Based on this post..
- Your API will not get any more items
- You will need to work out how to detect this and then with your API solution generate another web app to carry on
- You have 1 or x records over the 1k limit you have to delete from one web app and move to another
- You have to tell your client that may happen and that if it does they need to stop using the other web app and use the new one (which they will be confused about and will not like)
- You have to run regular checks on the first and any other web app created for this one solution to check if the client had forgot and made a new web app item in the admin. OR BC now introduces a total 1k web app limit full stop (Which would be even worse)
- If the client comes to you and asks for changes that mean 3 more custom fields and it goes over the 20 limit - You have to tell them NO, or do changes across multiple web apps and API solution which may involve 2 web apps per 1 web app use the client then has to manage. So where you may have had to scale to 3 web apps already, you know have to do 1-1 data source for front end and 6 web apps total.
That would be nuts.