Quick Contact


    UDD is a universal dictionary and it is essentially an abstraction inside this application server that allows us our engineering teams and you to define the metadata shape of your world in Salesforce to create objects to create attribute field types all of the stuff that you need to do as far as defining your business in Salesforce all happens in this layer.

    • It is declarative entity model- means shape of this data isn’t like a bunch of lines of code. In this there are entities, attributes and it’s checked into source control.
    • When you stored in database the point is the declarative entity model- means it allows the same interactions on internal and external platform developers.
    • Internally it didn’t always used to be like that, internally when Salesforce was started it was sales tool and allot of this platform stuff came along, as when start a company there are account objects and got a contacts object. So accounts tables are created in contacts table, in your database which is not effective way to store large data.
    • At runtime UDD is the “ORM”, maps to the database.
    • In this database is not accessed directly there is intermediary application server, or you can access through the layer.
    Structure of the Salesforce ID

    There are Salesforce ID’s is the 15 character IDs. It has its own ID structure having different parts.


    First three characters are considered as “key prefix”, key prefix identifies the entity. Next two bits are the instances, it is for uniqueness that tenant is on which instance to avoid ID collision because IDs are created on different instances. The next two bits are reserved; there are 62 possible characters that can go in any one of these slots, characters are reserved in part of ID. Then next and last part is the unique part of the ID which is 62 to the eight powers. ID with a bunch of uppercase and lowercase numbers and change it all to lowercase which is not so good. So, threw on three extra characters which are a checksum of the rest of the case of all the other characters in the ID, so you can check the case what is supposed to be.

    Now talk about

    • A virtual database on top of physical database. Virtual database containing same components as physical database does as it contains rich model of entities, attributes, relationships. When you work with UI and API then you will see the virtual database scenario.
    • Virtual database is entirely virtual i.e. when you create an entity then it doesn’t create physical structure in relational database like DDL operations. As in this few rows and tables are inserted and system behaves as there is a whole new entity. Virtual can’t allow blocking DDL.
    • Many things in normal database operate virtually like generating foreign or unique keys in DB and mostly indexes are virtual.
    • In physical database there is multi-level partitioning as there are multiple physical nodes, partitioned tables, and there is node to partition mapping, for cache performance.
    • In physical database there are JDBC connection are pooled for each app server.

    It has many ways to perform different operations well like it has own optimizer, heavy DB hints as well as skinny tables etc. and everything is invisible to you i.e. processed internally.

    Copyright 1999- Ducat Creative, All rights reserved.

    Anda bisa mendapatkan server slot online resmi dan terpercaya tentu saja di sini. Sebagai salah satu provider yang menyediakan banyak pilihan permainan.