Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Countly Enterprise Edition deployment scenarios


Published on

This document guides you through installation and configuration of Countly Enterprise Edition.

Published in: Data & Analytics
  • Be the first to comment

  • Be the first to like this

Countly Enterprise Edition deployment scenarios

  1. 1. Countly 1 Countly Enterprise Edition - Deployment Scenarios
  2. 2. Getting Started web: twitter: @gocountly 2 This guide will take you through; 1. Deployment planning 2. Installation 3. SDK integration 4. Plugins 5. Support requests
  3. 3. Deployment Planning web: twitter: @gocountly 3 Countly Enterprise Server consists of two main nodes; 1. Countly application server 2. MongoDB database server In the next few slides we’ll go over deployment options, talking about replication and high availability scenarios including server specs.
  4. 4. Deployment Planning: Option 1 web: twitter: @gocountly 4 Most basic form of a Countly deployment is a single node acting as both Countly application server and MongoDB database server. Single Node (server) MongoDB Countly API Countly Dashboard Nginx Dashboard User Countly SDK
  5. 5. Node 2Node 1 Deployment Planning: Option 2 web: twitter: @gocountly 5 Most common and recommended way of a production Countly deployment is like below. Two Countly application servers behind a load balancer and a MongoDB replica set with one primary and one secondary. Dashboard UserCountly SDK Countly API Countly Dashboard Nginx Countly API Countly Dashboard Nginx MongoDB Replica Set Primary Secondary Arbiter Load Balancer
  6. 6. Deployment Planning: Server Specs for Option 1 web: twitter: @gocountly 6 • 4GB RAM for each core in your node. • 30GB boot disk. • 100GB+ (depending on your data volume) SSD disk for MongoDB.
  7. 7. Deployment Planning: Server Specs for Option 2 web: twitter: @gocountly 7 • 2GB RAM for each core in Countly application server(s). • 4GB RAM for MongoDB primary and secondary for each core in Countly application server(s). If you have a 4 core Countly deployment, your database servers need 16GB RAM at minimum. • MongoDB servers need minimal CPU resources. • MongoDB arbiter needs minimal resources. You can have a 1 core, 2GB RAM server as your arbiter. Arbiter doesn’t store any data and is only there for replica set member voting procedure. • All 5 servers; 2 Countly, MongoDB primary, secondary and arbiter each needs 30GB boot disks. • Data bearing servers, MongoDB primary and secondary, each needs 100GB+ (depending on your data volume) SSD disks.
  8. 8. Deployment Planning: Ports web: twitter: @gocountly 8 • Countly nodes need 80 (http), 443 (https), 53 (DNS) and 25 (mail) ports to be open. • MongoDB requires 27017 port to be open (for replica set). For all MongoDB ports see this link.
  9. 9. Installation web: twitter: @gocountly 9 1. Upload Countly installation package to Countly node(s) 2. Extract it 3. Follow steps in this document for operating system specific guidance If you are deploying Option 2, you need to; 1. Install a MongoDB replica set as described here 2. Configure both Countly nodes to use the new replica set as described here
  10. 10. SDK Integration web: twitter: @gocountly 10 • This link contains a list of Countly SDKs with integration guides • In order to develop your own SDK you can check out this guide
  11. 11. SDK Integration: Custom Events web: twitter: @gocountly 11 Countly collects session related metrics out of the box. For custom metric tracking Countly offers a mechanism called custom events. Custom events should be planned out carefully before starting SDK integration. For further information; 1. Custom events 2. SDK methods for custom events
  12. 12. Plugins web: twitter: @gocountly 12 Countly offers a plugin architecture where you can develop your own plugin in order to do custom data processing and reporting without touching Countly core codebase.
  13. 13. Plugins: Architecture web: twitter: @gocountly 13 Countly Core My Plugin MongoDB Countly Dashboard Plugin Handler (Backend) Plugin Model Plugin View
  14. 14. Plugins: Development Guidelines web: twitter: @gocountly 14 ● Introduction ● Plugin structure ● Plugin API side ● Frontend server side files ● Frontend browser files ● Frontend client side files ● Extending or modifying modules ● Shared configurations ● Logging
  15. 15. Support web: twitter: @gocountly 15 • You can email for any request • Alternatively, you can submit a request to Countly Support Forum • contains detailed documentation about every aspect of Countly
  16. 16. Countly 16