
Registered since September 28th, 2017
Has a total of 4246 bookmarks.
Showing top Tags within 6 bookmarks
howto information development guide reference administration design website software solution service product online business uk tool company linux code server system application web list video marine create data experience description tutorial explanation technology build blog article learn world project boat download windows security lookup free performance javascript technical network control beautiful support london tools course file research purchase library programming image youtube example php construction html opensource quality install community computer profile feature power browser music platform mobile user process work database share manage hardware professional buy industry internet dance advice installation developer 3d search access customer material travel camera test standard review documentation css money engineering develop webdesign engine device photography digital api speed source program management phone discussion question event client story simple water marketing app yacht content setup package fast idea interface account communication cheap compare script study market live easy google resource operation startup monitor training
Tag selected: high availability.
Looking up high availability tag. Showing 6 results. Clear
Saved by uncleflo on July 11th, 2019.
It’s a few weeks after AWS re:Invent 2018 and my head is still spinning from all of the information released at this year’s conference. This year I was able to enjoy a few sessions focused on Aurora deep dives. In fact, I walked away from the conference realizing that my own understanding of High Availability (HA), Disaster Recovery (DR), and Durability in Aurora had been off for quite a while. Consequently, I decided to put this blog out there, both to collect the ideas in one place for myself, and to share them in general. Unlike some of our previous blogs, I’m not focused on analyzing Aurora performance or examining the architecture behind Aurora. Instead, I want to focus on how HA, DR, and Durability are defined and implemented within the Aurora ecosystem. We’ll get just deep enough into the weeds to be able to examine these capabilities alone.
aurora durability replication workload redundancy configuration diligence database automation informative replica latency storage layer cluster duplicate priority transaction development administration blog article discussion realize system define examine high availability disaster recovery dr explanation
Saved by uncleflo on June 27th, 2018.
Production experience for the last decade(s). Peter Zaitsev, CEO, Percona. June 19, 2018. Percona Technical Webinars. Please join Percona’s CEO, Peter Zaitsev as he presents MySQL: Scaling and High Availability – Production Experience Over the Last Decade(s) on Tuesday, June 19th, 2018 at 7:00 AM PDT (UTC-7) / 10:00 AM EDT (UTC-4). Percona is known as the MySQL performance experts. With over 4,000 customers, we’ve studied, mastered and executed many different ways of scaling applications. Percona can help ensure your application is highly available. Come learn from our playbook, and leave this talk knowing your MySQL database will run faster and more optimized than before.
experience percona technical webinar scaling high availability performance application presentation pdf database fast speed howto mysql insight explanation references administration production
Saved by uncleflo on February 26th, 2018.
At work, we run a simple high-availability (HA) MariaDB setup that consists of an active master that handles all read and write queries from our applications, a passive master that can take over for the active master at any time, and a read-only replication slave (not shown) that we use for backups and analytics. Replication is configured so that the active master follows the passive master, the passive master follows the active master, and the analytics slave follows one of the masters. For the remainders of this post, I will refer to the active master as the master and the passive master as the standby. The benefits of this master-master configuration is that it allows us not only to failover from master to standby if the master becomes unhealthy, but also allows us to perform patching, reboots, lengthy migrations, and other kinds of database maintenance without impacting our users. Well, almost...
high availability mariadb master slave query db dbms backup replication failover painless administration configuration perform patch reboot application remain impact user configure maintain
Saved by uncleflo on February 26th, 2018.
In information technology, High Availability refers to a system or component that is continuously operational for a desirably long length of time: Wikipedia up time / total time. Here, the presentation discusses MariaDB MaxScale, setup to see how it works.
connector mariadb nosql crud api core application development administration parse plugin source optimise memory connect graph extend high availability available syncronise audit replicate production howto discussion technology cluster tool db dbms distributed databases
Saved by uncleflo on February 25th, 2018.
This is a follow-up blog post that expands on the subject of highly available cluster, discussed in MariaDB MaxScale High Availability: Active-Standby Cluster. Replication Manager is a tool that manages MariaDB 10 clusters. It supports both interactive and automated failover of the master server. It verifies the integrity of the slave servers before promoting one of them as the replacement master and it also protects the slaves by automatically setting them into read-only mode. You can find more information on the replication-manager from the replication-manager GitHub repository. Using Replication Manager allows us to automate the replication failover. This reduces the amount of manual work required to adapt to changes in the cluster topology and makes for a more highly available database cluster. In this blog post, we'll cover the topic of backend database HA and we’ll use Replication Manager to create a complete HA solution. We build on the setup described in the earlier blog post and integrate Replication Manager into it. We're using Centos 7 as our OS and we'll use the 0.7.0-rc2 version of the replication-manager.
replication cluster high availability manager manage administration topology master slave automatic failover failsafe integration howto article description use software mariasql verify repository expansion readonly server information standby blog post subject discuss backend solution
Saved by uncleflo on December 27th, 2017.
HAProxy is a free, very fast and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic web sites and powers quite a number of the world's most visited ones. Over the years it has become the de-facto standard opensource load balancer, is now shipped with most mainstream Linux distributions, and is often deployed by default in cloud platforms. Since it does not advertise itself, we only know it's used when the admins report it :-) Its mode of operation makes its integration into existing architectures very easy and riskless, while still offering the possibility not to expose fragile web servers to the net. Each version brought its set of features on top of the previous one. Upwards compatibility is a very important aspect of HAProxy, and even version 1.5 is able to run with configurations made for version 1.0 13 years before. Version 1.6 dropped a few long-deprecated keywords and suggests alternatives. The most differenciating features of each version are listed below :
proxy load balancer solution availability proxying tcp http application traffic website power standard opensource linux distribution architecture operation feature compatibility configuration explanation software server howto free fast webserver development administration production business high availability
No further bookmarks found.