A snippet of Tableau’s recommended architecture for a three-node cluster is below. There is an initial node and two worker nodes with a few shared services that provide redundancy in case of failure on one of the nodes. The setup for High-Availability (HA) requires at least a three-node cluster. Once you establish trust in your data, the next step is to establish trust in your infrastructure - the confidence in your clients and colleagues to know that their data will be available when they need it. If you’ve encountered an outage before during the middle of the night, with colleagues blowing up your phone (or even worse, clients,) you know exactly what I’m talking about. If your team has already found success in fostering a Tableau-forward culture at your organization, have an active developer community in your Slack or Teams, and have an established and formal devops process in place: first off - congrats! Secondly, you may have started to think about how to ensure that your environment maintains a proper enterprise-level uptime now that you are maintaining enterprise-level insights that are critical to running your business. Using a public cloud like Amazon’s AWS or Google Cloud? Then it’s even easier, as these platforms now offer an (almost) one-click solution to spin up a default Tableau Server environment in minutes. ![]() Set up a machine, run the installer, set up a service account, and you’re good to go. ![]() ![]() One of many attributes of Tableau Server that has been historically praised is its ease of setup and maintenance.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |