Found 90 results for "tour usecases mongodb"
The search executed in 0.001223875 seconds. That's fast.
Gitana / 3.2 / Guide / Guide / Supported StacksSupported Stacks Cloud CMS certifies certain supported stacks for on-premise Cloud CMS 3.2 installations. This information is relevant to customers who run Cloud CMS 3.2 on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Cloud CMS runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled compon
Score: 11.2156105
|
|
Gitana / 4.0 / Self Managed / Supported Stacks / OverviewSupported Stacks Gitana certifies certain supported stacks for on-premise Gitana 4.x installations. This information is relevant to customers who run Gitana 4.x on-premise and manage their own Elastic Search and MongoDB database tiers. This information is not applicable to SaaS customers since Gitana runs that infrastructure for hosted subscribers. The following links provide detailed information on the combinations of operating systems, databases, application servers, bundled components and thi
Score: 11.112226
|
|
Gitana / 3.2 / Guide / Guide / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 11.059414
|
|
Gitana / 4.0 / Data Engine / Discovery / QueryQuery Cloud CMS provides SQL-like, structured query for all of your content. The platform uses MongoDB under the hood to store the JSON for your content. MongoDB offers a powerful, unmatched query engine so that you can execute complex lookups of your content to support both your editorial and runtime application needs. The platform also offers "composite" query operations which let you layer MongoDB queries on top of Elastic Search DSL searches and traversals around node objects. Cloud CMS auto
Score: 11.059414
|
|
Gitana / 3.2 / Guide / Guide / FindFind The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on
Score: 8.197219
|
|
Gitana / 4.0 / Data Engine / Discovery / FindFind The Cloud CMS Find Service lets you discover and retrieve content using combinations of its three primary content retrieval mechanisms. These mechanisms are: Query (powered by Mongo DB) Search (powered by Elastic Search) Traversal (provides Graph Traversal) A "Find" operation provides a way for you to execute a single API lookup that runs one or more of the above and composes them into a single result set. How it Works When you make a "Find" call, you provide a recipe containing at least on
Score: 8.197219
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / MongoDB Replica SetMongoDB Replica Set The MongoDB Replica Set kit defines an environment with a 3 node MongoDB replica set and two Cloud CMS environments running against it The configuration files for this kit can be found in the Gitana SDK Running Start the mongo servers first and then initialize the cluster: docker login --username {docker-username} --password '{docker-password}' docker-compose up -d mongodb1 mongodb2 mongodb3 Initialize the replic set. only have to do this once since the mongo servers persist
Score: 7.530616
|
|
Gitana / 3.2 / Guide / Guide / Integrations / Amazon Web Services / Amazon DocumentDBAmazon DocumentDB Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Cloud CMS works out-of-the-box with Amazon DocumentDB as an alternative to running MongoDB on your own or using a MongoDB hosted service. Amazon DocumentDB provides an easy and convenient way for customers to manage their own MongoDB installations, data and backup. To learn more, check out API Server.
Score: 6.5537558
|
|
Gitana / 4.0 / Data Engine / Integrations / Amazon Web Services / Amazon DocumentDBAmazon DocumentDB Amazon DocumentDB (with MongoDB compatibility) is a fast, scalable, highly available, and fully managed document database service that supports MongoDB workloads. Cloud CMS works out-of-the-box with Amazon DocumentDB as an alternative to running MongoDB on your own or using a MongoDB hosted service. Amazon DocumentDB provides an easy and convenient way for customers to manage their own MongoDB installations, data and backup. To learn more, check out API Server.
Score: 6.5537558
|
|
Gitana / 3.2 / Guide / Guide / Docker / Configuration / SupportSupport In this section, we provide best practices that should be considered when submitting support tickets for on-premise Cloud CMS installations. When submitting tickets to Cloud CMS, the objective should be to provide as much information as possible so that the ticket can be worked on as quickly as possible. Very often, tickets are submitted that do not have sufficient detail or information to either understand the problem or reproduce it. Tickets that include things like log files, database
Score: 5.6942635
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.6339035
|
|
Gitana / 4.0 / Self Managed / Kits / QuickstartQuickstart The Quickstart kit defines the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To access the API directly: https://localhost:8080 docker-compose.yml version: "2" services: ui: build: ./ui networks: - cloudcms depends_on: - api env_file: - ./ui/ui.env ports: - "80:80" api:
Score: 2.6339035
|
|
Hazelcast, MongoDB and Cloud CMSWe’ve had a few requests for the Cloud CMS presentation we gave on Hazelcast and distributed caching at the Boston MongoDB conference last November. I thought I’d take a moment to provide a link to it for the benefit of the community. Hazelcast and MongoDB at Cloud CMS Interested in running Cloud CMS in your own private cloud? Contact us at info@cloudcms.com to get started!
Score: 2.5920832
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / API ClusterAPI Cluster The api-cluster kit defines the following services: ui api1 api2 apilb mongodb elasticsearch This kit differs from the quickstart in how it handles API requests. Requests are sent to the apilb container which runs a load balancer, distributing work between api1 and api2. It is worth reviewing the cluster settings for both of your api servers in order for them to correctly communicate. Running Use the following commands: docker-compose build --force-rm docker-compose up And then open
Score: 2.5878162
|
|
Gitana / 3.2 / Guide / Guide / Docker / KitsKits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the
Score: 2.4934673
|
|
Recommended environmentThis is a big subject and, as you know, there are many ways to set things up to be robust. That said, some practices are better than others. I can relate at least what we do and what we've seen customers do. First, I'd recommend thinking of Cloud CMS as black box application that runs on top of MongoDB, Elastic Search (both of which can be thought of as databases) and a binary storage provider. Cloud CMS is a stateless application whose setup is actually quite simple. It doesn't maintain any sta
Score: 2.4793622
|
|
Gitana / 4.0 / Self Managed / Kits / OverviewKits Cloud CMS ships a number of pre-built kits containing Docker configuration files to help you get start. These kits are built from customer feedback to provide the most commonly requested scenarios. They can be used straight away or at the very least can serve as a useful reference. To download the Cloud CMS Docker Kits, please visit our Docker download page. Kits All of the Docker kits utilize Docker and Docker Compose. In each kit, you'll find a docker-compose.yml file which describes the
Score: 2.4497058
|
|
Gitana / 3.2 / Guide / Guide / Binary Files / GridFS Binary StorageGridFS Binary Storage Cloud CMS supports MongoDB GridFS by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avoid going back to
Score: 2.4074943
|
|
Gitana / 4.0 / Data Engine / Platform / Binary Files / GridFS Binary StorageGridFS Binary Storage Cloud CMS supports MongoDB GridFS by allowing it to serve as a backend provider for the storage of binary files within Cloud CMS. When files are uploaded to Cloud CMS, they are parsed and worked with and then eventually sent over to Amazon S3 for persistence. When users seek to download those binary files, they are streamed back from S3. Depending on how you elect to configure your binary storage providers, Cloud CMS may employ an TTL cache in between to avoid going back to
Score: 2.4074943
|
|
Gitana / 3.2 / Guide / Guide / Docker / Kits / OEMOEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acc
Score: 2.3419852
|
|
Gitana / 4.0 / Self Managed / Kits / OEMOEM The OEM kit provides a way for developers, integrators, partners and those who are embedded Cloud CMS in custom solutions to build and test extensions. These extensions include UI extensions as well as API extensions in the form of Java / Spring beans. The kit consists of the following services: ui api mongodb elasticsearch These are connected like this: Running Use the following commands: docker-compose build --force-rm docker-compose up And then open a browser to: http://localhost To acc
Score: 2.3419852
|
|
Query PerformanceApplication queries Application code which consumes Cloud CMS content typically runs query API calls. These queries can be optimized in the following ways: Request only the properties needed When an application requires only a few properties from a set of nodes you should use “_fields” to limit the properties returned. This can drastically reduce the size of the payload and therefore the response time. In this example, we only need “_doc”, “title” and “_type” so these are the only fields that wi
Score: 2.1943378
|
|
Gitana / 3.2 / Guide / Guide / Docker / Maintenance / Repository CompressionRepository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif
Score: 2.1443193
|
|
Gitana / 4.0 / Self Managed / Maintenance / Repository CompressionRepository Compression Cloud CMS content is stored within a Repository. A Repository differs from other types of data stores in that it provides Copy-On-Write mechanics using Changeset-driven versioning. Every time you create, update or delete content within a repository, those adjustments are written onto a new Changeset. Changesets are layered automatically and provide a stack of differences that, over time, allow you to scroll back to any moment in time to see a perfect capture of every modif
Score: 2.1443193
|
|
How we use Docker at Cloud CMSAt Cloud CMS, we use Docker to provision our cloud infrastructure servers on top of Amazon Web Services. Our stack consists of five different clusters: Cloud CMS API Cloud CMS UI Cloud CMS App Server for Dynamic Hosting Elastic Search MongoDB With the exception of MongoDB, all of these clusters are allocated using elastic load balancing and are architected in such a way that we can spin up new servers and tear down old ones with elastic demand. That is to say, they are fully elastic in design. T
Score: 2.1083016
|