Scaling Without Failing
What they don’t tell you about mega-orgs.
DemoJam Competitors
Silver
Gold
Platinum
Thank You
Our Sponsors
Igor Chtivelband
Agenda
What I consider to be a Mega Org
Limits, Limits, Limits
DIY Monitoring
Costs Optimization
What I consider to be a Mega Org
Imagine the following Salesforce Org
2K User Licences
Up to 20K Cases created per day
Hundreds of Queues
25M Accounts records
Tens of deployments per day
Variety of niche products in use (e.g. Salesforce Connect)
Limits
One battle after another
These are the limits that will make your life harder
1,000 values per picklist, only 300 of them can be used as a controlling field for a dependent picklist
Daily Limit: 15,000 batches for Bulk API 1.0 or 150M records for Bulk API 2.0
Ingress (250K per hour) and Egress (50K per day) on Platform Events
30M Total Files (ContentDocuments) per Organization
The proposed solutions
1,000 values per picklist, only 300 of them can be used as a controlling field for a dependent picklist => Custom object/metadata + Custom LWC
Daily Limit: 15,000 batches for Bulk API 1.0 or 150M records for Bulk API 2.0 => Be very careful with the third party tools (e.g Hightouch/Census)
Ingress (250K per hour) and Egress (50K per day) on Platform Events => Buy Add-on
30M Total Files (ContentDocuments) per Organization => File Storage Externalisation
DIY Monitoring
Reasons to build DIY Monitoring for Salesforce
Near-real-time alerting
Multi-channel notifications
Custom metrics (e.g. # Active User Sessions)
Better visualization
Alignment with the company’s general tech stack
Recommended Architecture
Dashboard Example
Costs Optimization
The factor that caught me off guard
For an organization with 2,000 users here is how your data storage breaks down for the most common editions
Edition | Base Storage | Storage Added per User | Total |
Enterprise | 10 GB | 20 MB | 50 GB |
Unlimited | 10 GB | 120 MB | 250 GB |
Performance | 10 GB | 120 MB | 250 GB |
Professional | 10 GB | 20 MB | 50 GB |
Is 250 GB a lot or not?
Most of the objects consume 2 KB per record
HTML Emails consume their actual size
250 GB = Approximately 125M records
Assuming your company has 25M customers, you might run out of storage just by serving one support Case per customer
Catalog price for Data Storage is $125 per month for 500MB
An Org with 25M accounts might easily consume 500MB of additional data storage in a day
How to deal with the data storage problem?
Automated Data Retention
Big Object
Externalization
Q & A
DemoJam Competitors
Silver
Gold
Platinum
Thank You
Our Sponsors