I'm trying to build a Decentralised social media platform using Cassandra. To do this I would like the instances or nodes of the Cassandra database to be hosted on the clients side rather then having it hosted on the cloud. I would like to know if it would be possible for the user to somehow run an instance on their side with part of the data. This will allow the information to be distributed between many computers globally.
You can deploy Cassandra nodes:
on-premise,
on a private cloud,
on a public cloud, or
a hybrid environment of on-premise + cloud.
It is also possible to deploy Cassandra on any combination of the above. Cheers!
Related
I wanted to pull the data from my on-prem server ( hive or oracle ) to Azure data factory. Whereas i am facing issues can you help me in this?
I am asking this on the basis of enterprise issue. I wanted my integration Runtime to be in Onprem server , currently we are installing it in our own laptops and if our laptop is shut down then obviously IR is stopped and data won't be loaded this can't be feasible in production.
Do anybody know that what is meant installing IR in my on prem server? that means in my hive server?
Your help will be really appreciated.
Your SHIR server does not have to be on the same server as your data source. But it should be close to it. Same region or same data center.
You need a server that is always powered and running. Refer to the documentation.
If you want high availability you should refer to this link.
If you want DR, you will need another SHIR on a DR server in your secondary region.
You can also install the SHIR onto a VM running on the cloud. But your Onprem network needs to be connect to the Cloud VNET using Express route or a VPN.
Laptops is fine for testing but as you said, not for production.
Your IT team should also take care of the patching and updates/maintenance of the new server whether it is on prem or on cloud.
I have an application in mind that would be built using node, mongodb + other db, kubernetes , RabbitMQ, docker and react as a front end. The application will be built in a microservice architecture. We all know that for a monolith app all you need is one DB (MongoDB, MySQL etc etc) but for a micro one you can have multiple databases. My question would be, do I need to buy multiple, separate databases and connect each service to them ? or how does it work in a micro-services design.
At the moment a I have a sample microservices app that is running on my local machine using docker and its connected to multiple databases or database/service. I am just to trying to get an idea on how does this work with companies like DigitalOcean or AWS.
Any input on this would be great.
I am just trying to figure out how this going to work when it comes to production later so that I am ware of cost and deployments. I have done some research on Digital ocean, AWS etc etc but I still can figure out how do they work.
thanks in advance.
You don't need having multiple instances of DBMS running. You can easily use one VM with one MongoDB running on it.
When you scale you might want to have separate machines running DB instances for your services, but at start you may just separate it logically to ensure you do not communicate between services using DB.
Chris Richardson on his microservices.io website says:
There are a few different ways to keep a service’s
persistent data private. You do not need to
provision a database server for each service.
For example, if you are using a relational database
then the options are:
- Private-tables-per-service – each service owns a
set of tables that must only be accessed by that
service
- Schema-per-service – each service has a database
schema that’s private to that service
- Database-server-per-service – each service has
it’s own database server.
Source: https://microservices.io/patterns/data/database-per-service.html
For deploy tableau server, can i deploy tableau server HA in three-node configuration on Azure Virtual Machine like this link : High Availability Installations (HA) Three-node configuration
How i do? who have experience about deploy tableau environment on Azure, please advise me.
Yes, running Tableau Server on a Microsoft Azure VM is an excellent choice if you want the flexibility of scaling up and scaling out without having to purchase and maintain an expensive fleet of servers.
For instance, you can configure Tableau Server as three-node to be highly available, and integrate with all of the common enterprise applications (for example, Active Directory) that many organizations rely on.
For more details, you could refer to:
Install Tableau Server on Microsoft Azure
Example: Install and Configure a Three-Node HA Cluster
We are planning to migrate our Enterprise Application(s) from on-premises to Azure. Below are the high level details about our current infrastructure.
One Web Server hosting multiple WebSites (around 30 websites)
One Server with SSIS installed in it which processes huge data coming from multiple data sources and dumps the data into Pre-production database server explained in #3 below
Two Servers (Pre-production and Production) with SQL Server hosted in them where some jobs run on Pre-Produciton Server and the data gets replicated to the Production database server.
One Server where SSRS is hosted that uses data (and stored procedures) from Pre-Production database Server.
Could you please let us know if it is a good option to migrate the current infrastructe to PAAS? Is it really possible? We are also planning to leverage the other Azure features like Load Balancing on Web Servers and High availability on Production Database server with Active-Passive servers.
For migration scenarios, please see the following: https://azure.microsoft.com/en-us/documentation/articles/sql-database-cloud-migrate/
trying to figure out how to create Cassandra cluster in Azure across more than one datacentre.
I am not much interested in Cassandra topology settings yet, but more in how to set Azure endpoints or inter-datacentre communication to allow nodes to connect remotely. Do I need to set endpoint for node communication inside one datacentre?
What about security of azure endpoints?
Thank you.