Quickly loading large amounts of data into the Salesforce1 Platform is certainly awesome, but can temporarily cause stale full-text search indexes. Do you understand why this can happen? More importantly, do you know why this matters to your application users and strategies for addressing this problem? Read this post for more details.
Tag Archives: architecture
If you’ve read the many blog posts, wikis, webinars, and other content from the Customer Centric Engineering-Technical Enablement team, then you already know how we help customers investigate and solve challenging problems, take what we learn, and teach others how to avoid similar problems. The idea is to make tough roads easier to travel for [...]
The Salesforce Bulk API – Maximizing Parallelism and Throughput Performance When Integrating or Loading Large Data Volumes
One of the most important data loading and integration best practices is simple: When you run a Bulk API job, processing more of its batches in parallel means giving that job a higher degree of parallelism, which in turn gives your run better throughput. But what is a good degree of parallelism, and how can you architect a solution that maximizes the throughput that parallelism gives you?
The Force.com query optimizer is not unlike the cost-based optimizer you’ll find in many traditional relational database systems–it helps map out the most efficient path to the data you request from the database. However, because the Force.com database is multitenant and uses a record-ownership model, it has some remarkable differences to be aware of so that you get the best performance for your applications.
With the powerful Salesforce sharing features, you can support collaboration within your organization while keeping sensitive information secure. And while you must always balance collaboration with security, there are situations in which you might need to make absolutely sure that record access is limited to a very small number of people, regardless of their position within the corporate hierarchy. In this post, you’ll learn about the sharing features and strategies you can use to do just that.
As an experienced Salesforce architect or developer, your job is as dynamic as your organization and its users. You don’t just need to design a sharing model, Force.com applications, and SOQL queries that meet your company’s current security, page performance, and data requirements; you must also design an architecture that can scale to support your organization’s future data volumes and user bases.
So why chance facing additional work and long wait times later, or wishing that you had a time-traveling Delorean to hop in? Just attend Technical Enablement’s sessions and workshops at Dreamforce to learn a few performance-related best practices, test what you learned in a hands-on environment, and scale your organization to success.
Every day, the Technical Enablement team works with customers like you to review their architectures and help them solve implementation challenges on the Salesforce platform. One of those implementation challenges involves a seemingly simple platform feature: formula fields. Under the hood, poorly designed formula fields can consume a lot of resources, lead to slow query response times, and hurt your users’ productivity.
We see these problems in many of our customer cases, and we know that the best way to avoid them involves learning both what makes formula fields efficient and how to build efficient formula fields. If you’re a developer, architect, or administrator who wants to build lightning-fast formula fields, you’ll want to attend our intermediate-level Dreamforce session, “Revving Up the Force.com Formula Engine,” and its associated workshop.
In Salesforce, the foundation of reporting is the retrieval of an organization’s data. If your data isn’t retrieved efficiently, your reports can be incredibly slow and might time out, which will frustrate your users. If you’re a developer or an architect maintaining an organization, you’ll want to attend the “Building Reports that Fly” breakout session at Dreamforce ‘13, as well as that session’s associated Developer Zone workshop.
Join us to learn how governing your organization’s data architecture and your users’ record access can help users find the data they need, and how you can build efficient reports to deliver that data quickly.
Open the hood, have a peek, and learn more about how the Salesforce platform is built to handle more than 1.3 billion transactions per day.
Record ownership is at the core of Salesforce’s record access capabilities, which allow you to specify which users or types of users should be able to access specific records or types of records. Salesforce.com’s architects and developers have spent years creating a highly functional and massively scalable record access infrastructure around record ownership, saving you the monumental effort of building that infrastructure yourself.
In this post, you’ll learn how those years of heavy lifting have actually simplified record access for the most common enterprise security models, allowing you to configure record access declaratively instead of with painstakingly developed code. You’ll also get an “under the hood” view of record access, and learn how to implement your record access model and avoid potential pitfalls along the way.