Search Results

API / Content Services / Statistics

Statistics Cloud CMS automatically collects and aggregates node statistics for you as you connect nodes together in the content graph. Nodes are entities and associations are used to connect them together through a series of relationships. As nodes are connected together, both the source and target node will have their statistics computed and updated so that you can quickly find out how many relationships a given node has to its neighbors. The basic mechanics behind node statistics are similar t

Score: 12.121226

API / Features / Rates

Rates QName: f:rates Applied to an association to indicate that the target node contains a property with a rating value that should be used to aggregate (increment or decrement) rating statistics on the source. This feature automatically computes rating statistics on the source node for the property indicated on the target node. The following statistics are aggregated on the source node: { "_statistics": { "ratingTotalCount": , "ratingTotalValue": , "r

Score: 11.738892

API / Features / Stats Sum Counter

Stats Sum Counter QName: f:stats-sum-counter Applied to an association to indicate that a statistics counter from one of end of the association should be aggregated up into another counter on the other end of the association. This feature builds on the existing Node Statistics capabilities of Cloud CMS by letting you define custom sum counters from one end of an association to be applied to the other end. Statistics counters are accumulated once on create and decremented once on delete. Configur

Score: 10.635509

AWS loadbalancer healthchecks

For AWS LB healthchecks, we recommend the following path off the API: /healthcheck This route hands back a 200 if the API server is healthy. It determines whether it is healthy by checking a few statistics such as the amount of free memory, the amount of free disk space, network connectivity, file handle usage, CPU utilization and more. If it returns a non-200, then that serves as a signal that the server is in some sort of degraded state and should be rolled over (which elastic scaling groups w

Score: 5.910369

Mitigating the OWASP Top 10

An explanation of how Cloud CMS addresses each of the Top 10 OWASP topics: Mitigating-the-OWASP-Top-10.pdf

Score: 5.797893

API / Data Types / Platform

Platform Configuration As with all data stores, this data store maintain a configuration document that contains system and custom properties. You can write your own properties onto this configuration document if you wish. You might use those properties to query and retrieve the directory at a later time. Some system properties are read-only and others are writable. You can adjust the writable properties to modify the behavior and characteristics of the directory. The following table presents you

Score: 5.6638093

API / Actions / Start Workflow

Start Workflow ID: startWorkflow Starts a workflow with the given node placed into the payload. Configuration Property Type Required Default Description model text true The ID of the workflow model to be used. swimlanes object false Identifies principals to be assigned into workflow swimlanes. The structure is: { "swimlane1": ["domainId1/principalId1"], "swimlane2": ["domainId2/principalId2"] } runtime object false Allows for manual specification of runtime properties including applica

Score: 5.657179

API / Integrations / Amazon SNS

Amazon SNS The Amazon Simple Notification Service (SNS) is a fast, flexible, fully managed pub-sub messaging service. Use it as a cloud-based mobile app notification service to send push notifications, email, and SMS messages; or as an enterprise-messaging infrastructure. Amazon SNS provides support for Push Notification of messages as well as distribution of messages to custom HTTP endpoints or via conventional SMS, email and other messaging channels. Cloud CMS API Cloud CMS connects to Amazon

Score: 4.9350677

Node Lifecycle Events

First, you configure your tenant with the AWS credentials of an IAM user and a SNS topic ARN that you wish to publish notification events to. This can be on your own AWS account so that you can work with these notifications any way you'd like. The notifications are for a variety of node lifecycle events. The primary one is "node_invalidation" which happens whenever a node's state changes. It's an indication that anyone caching anything downstream might want to reconsider their cache state. In te

Score: 4.931111

Cache invalidation via SNS

At present, Cloud CMS can be configured to publish notifications to Amazon SNS. Thus, to take advantage of this, you'd have to first have an Amazon Web Services account and an SNS topic created. Cloud CMS publishes notifications to it. Your topic can then do anything it wants with these notifications. Your cluster can listen for these events and process messages to invalidate cache. Most commonly, people hook the SNS services to the SQS service for queue-based event management. We've chosen this

Score: 4.8412786