Abstract: A distributed storage system includes a primary storage system and a secondary storage system. The secondary storage system stores the actual data and the primary storage system stores metadata for the actual data. The metadata references at the primary storage system may be deleted without deleting the corresponding data at the secondary storage system. Snapshots of the metadata at the primary storage system are sent to the secondary storage system. The secondary storage system can compare two metadata snapshots received from the primary storage in order to determine whether data stored at the secondary storage system has been deleted at the primary storage system for longer than a retention period. Such data may be deleted to free up storage space at the secondary storage server.

Abstract: A distributed storage system includes a primary storage system and a secondary storage system. The secondary storage system stores the actual data and the primary storage system stores metadata for the actual data. The metadata references at the primary storage system may be deleted without deleting the corresponding data at the secondary storage system. Snapshots of the metadata at the primary storage system are sent to the secondary storage system. The secondary storage system can compare two metadata snapshots received from the primary storage in order to determine whether data stored at the secondary storage system has been deleted at the primary storage system for longer than a retention period. Such data may be deleted to free up storage space at the secondary storage server.

Abstract: Embodiments include an event services modeling framework. The event services modeling framework includes an event services modeling editor that provides a user interface and mechanism for users to model and customize event flow configurations within a system and/or network. The user interface can be used to connect events with actions that will take place in response to the events. The system components and/or modules that need to receive the information from the events can then react and respond appropriately. Users can modify event configurations based on their own particular needs. the event services editor can be used for generating one or more event services models. The event services models may include events, conditions (rules) for processing the events, activities to be perform during event processing, subscriber modules defined for performing the activities during event processing, and a specified time for processing the events in each modeled event flow.

Abstract: The embodiments described in this disclosure relate to an extendable data model framework that enables users to develop applications without having to write code. The embodiments provide a user interface for users to build and maintain applications based on the framework, create custom user interfaces for the application, as well as define data objects, relationships between objects, workflows, business logic, and rules for applications the users are developing. The extendable data model framework includes an extendable data objects data structure and an extendable data object relationships data structure for users to customize data objects and relationships of the data objects for their applications using the described system. These data structures may include common data objects and relationship elements. The data structures can facilitate extension of data objects of the application as well as definition of new objects to be customized based on the business requirements of users.

Abstract: Embodiments include an event services modeling framework. The event services modeling framework includes an event services modeling editor that provides a user interface and mechanism for users to model and customize event flow configurations within a system and/or network. The user interface can be used to connect events with actions that will take place in response to the events. The system components and/or modules that need to receive the information from the events can then react and respond appropriately. Users can modify event configurations based on their own particular needs. the event services editor can be used for generating one or more event services models. The event services models may include events, conditions (rules) for processing the events, activities to be perform during event processing, subscriber modules defined for performing the activities during event processing, and a specified time for processing the events in each modeled event flow.

Abstract: The embodiments described in this disclosure relate to an extendable data model framework that enables users to develop applications without having to write code. The embodiments provide a user interface for users to build and maintain applications based on the framework, create custom user interfaces for the application, as well as define data objects, relationships between objects, workflows, business logic, and rules for applications the users are developing. The extendable data model framework includes an extendable data objects data structure and an extendable data object relationships data structure for users to customize data objects and relationships of the data objects for their applications using the described system. These data structures may include common data objects and relationship elements. The data structures can facilitate extension of data objects of the application as well as definition of new objects to be customized based on the business requirements of users.