Hi Ali,

I wrote a post about this a few days ago: http://www.codehb.com/content-hub/umbraco-as-a-backend-system/

We have used Umbraco for a few different business applications, and not just for websites.

We did face a few problems:

• Using Umbraco 6.2, at some point there were a lot of nodes and things started getting really slow, so we had to add these items in a separate table in the database and not as a node.
• One of our clients used Umbraco 6 to host their website and base of clients. They registered each client as a member (there were over 200k members), and Umbraco does not perform well with it.

You can definitely use Umbraco for your business solutions, but you might considering using other structure together with umbraco (database tables, JSON, etc), it all depends on your data structure.

Here's a nice article for you to check if Umbraco is made for what you want: https://our.umbraco.org/documentation/reference/Common-Pitfalls/ This bit is important:

"Using Umbraco content items for volatile data This is one of the worst Umbraco anti-patterns and could very well cause your site to perform ultra poorly.

Umbraco's content should not be used for volatile data, Umbraco's APIs and the way Umbraco's data is persisted was never designed for this. If you need to store/write/track data that changes a lot you should use a custom database table or another service but not Umbraco content nodes.

Some examples of what not to do are:

Hit counters to track the number of times your page has been viewed - use something like Google Analytics for this or a custom database table Creating new nodes for form submissions - this should be stored in a custom database table Importing lots of data into Umbraco content nodes that could easily just be stored in a custom database table (i.e. it's not going to be edited). In some cases this might be ok but many times we've seen bulk imports occur on a hourly/daily schedule which is generally unecessary."