Skip to main content

Big Objects in force.com platform

With Winter'14 salesforce introduced a feature called "Field History Retention". It was in pilot and with Spring'14 release, it's still in pilot. It is first force.com feature that uses big data technologies.


For more scalability, salesforce is working on big data technologies. And for this salesforce is working on new type of SObject 'Big Data'. Big objects are just like regular SObjects with more scalability, but less functionality.



Platform is built on top of relation technology using Oracle as main data repository for multi tenant environment. Now for more scalability salesforce is working on multi tenant big data store using HBase, which is open source database. Salesforce is working on Phoenix project, which allows to run low latency queries on top of HBase.



Initially Big Objects will come with let functionality and more scalability. When to use Big Object:-


  • if record count > 100 millions
  • can live with some platform limitations



In initial version following things will be difficult to do:-


  • Complex SOQL
  • Sharing
  • Isolated Transaction



We can expect following potential features in initial version:-


  • Flexible Schema
  • Powerful Data Processing



Comments

  1. Excellent Blog!!! Such an interesting blog with clear vision, this will definitely help many technologies to make them update.
    Salesforce Training Chennai
    salesforce developer training in chennai

    ReplyDelete
  2. Wonderful blog on Cloud domain, Thank you sharing the informative article with us. Hope your article will reach top of the SERP result to the familiar cloud related queries
    Regards:
    cloud computing training centers in chennai
    cloud computing training institutes in chennai

    ReplyDelete
  3. really pleasurable state. I just staggered a propos your weblog and wanted to guarantee that I have totally cherished perusing your blog entries. Any eccentricity I will buy in your feed and that I want you articulate close to more rapidly. huge gratitude for the helpful data. thanks! Bitdefender Antivirus Plus 2019 Crack

    ReplyDelete

Post a Comment

Popular posts from this blog

Mashup Integration in Salesforce

During preparation for TA certification exam, I came across a word Mashup for integration a number of times. I explored about it and below is description:- Mashups, sometimes called “composites,” are hybrid applications created by bringing together several data sources and Web services to create a new application or to add value to an existing application. Behind the scenes, mashups may require different levels of integration, depending on whether the mashed-up data is only meant to be viewed, whether it can be edited, and whether data is actually transferred between systems. There are three types of mashup:- Client Presentation Mashup - In this type of mashup the integration takes place strictly at the visual level. It makes possible to view data from two or more applications in a browser,  without actually moving data between the applications. Example - Google Maps. Client Service Mashup - As mashups evolve, they are becoming more complex and sophisticated. Client ser

ReadOnly Annotation

Use Case:- You want to show up to 10000 record on single VF page. Count of records based upon some business requirement where number of records could go up to 1 million. So far, it was not possible to achieve above in VF page because of following limitations:- The maximum number of items in a collection that can be iterated over using components such as <apex:dataTable> , <apex:dataList> , and <apex:repeat> is 1000. Normally, queries for a single Visualforce page request may not retrieve more than 50,000 rows. Solution:- But with API version 23.0 , salesforce has introduced ' ReadOnly ' annotation which has following functionality/restriction:- The @ReadOnly annotation allows you to perform unrestricted queries against the Force.comdatabase. All other limits still apply. It's important to note that this annotation, while removing the limit of the number of returned rows for a request, blocks you from performing the following operations

Grant Access Using Hierarchies

Problem There is a custom object say 'XYZ' and OWD for this is set to ' Private ', which means record of this can be seen by only owner and users above in role-hierarchy and territory. However, to share this with other user, we can manually share it. The problem is that I don't want other users, who are above in role-hierarchy and territory of the user with whom record has shared, can see it. Solution We can un-check ' Grant Access Using Hierarchies ' check box for object 'XYZ' on 'Sharing Settings' page. We can go to Setup >> Security Controls >> Sharing Settings and click on ' Edit ' button. On the edit page, we can un-check ' Grant Access Using Hierarchies ' for required object.  Major uses of 'Grant Access Using Hierarchies' are:- If you disable the Grant Access Using Hierarchies option, sharing with a role or territory and subordinates only shares with the users directly asso