Displaying 1 to 14 from 14 results

Tars - Tars is a highly performance rpc framework based on naming service using tars protocol and provides a semi-automatic operation platform

  •    C++

Tars comes from the robot in Interstellar movie. Tars is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule. Tars, aka TAF(Total Application Framework), has been used in Tencent since 2008. It supports C++,Java,Nodejs and php for now. This framework offers a set of solution for development, maintenance and testing, which making develop, deploy and testing service efficiently. It integrated extensible protocol for encoding/decoding, high-performance RPC communication framework, name service, monitor, statistics and configuration. You can use it to develop your reliable distributed application based on microservice fast, and reach fully efficient service management.

Tars - Tars is a highly performance rpc framework based on naming service using tars protocol and provides a semi-automatic operation platform

  •    C++

Tars comes from the robot in Interstellar movie. Tars is a high-performance RPC framework based on name service and Tars protocol, also integrated administration platform, and implemented hosting-service via flexible schedule. Tars, aka TAF(Total Application Framework), has been used in Tencent since 2008. It supports C++,Java,Nodejs and php for now. This framework offers a set of solution for development, maintenance and testing, which making develop, deploy and testing service efficiently. It integrated extensible protocol for encoding/decoding, high-performance RPC communication framework, name service, monitor, statistics and configuration. You can use it to develop your reliable distributed application based on microservice fast, and reach fully efficient service management.

kubeadm-ha - Kubernetes high availiability deploy based on kubeadm (for v1

  •    Smarty

kube-apiserver: exposes the Kubernetes API. It is the front-end for the Kubernetes control plane. It is designed to scale horizontally – that is, it scales by deploying more instances. etcd: is used as Kubernetes’ backing store. All cluster data is stored here. Always have a backup plan for etcd’s data for your Kubernetes cluster. kube-scheduler: watches newly created pods that have no node assigned, and selects a node for them to run on. kube-controller-manager: runs controllers, which are the background threads that handle routine tasks in the cluster. Logically, each controller is a separate process, but to reduce complexity, they are all compiled into a single binary and run in a single process. kubelet: is the primary node agent. It watches for pods that have been assigned to its node (either by apiserver or via local configuration file) kube-proxy: enables the Kubernetes service abstraction by maintaining network rules on the host and performing connection forwarding. keepalived cluster config a virtual IP address (192.168.20.10), this virtual IP address point to k8s-master01, k8s-master02, k8s-master03. nginx service as the load balancer of k8s-master01, k8s-master02, k8s-master03's apiserver. The other nodes kubernetes services connect the keepalived virtual ip address (192.168.20.10) and nginx exposed port (16443) to communicate with the master cluster's apiservers.

nsfailover - Let's Make DNS Outage Suck Less

  •    Shell

Read a longer introduction on my blog which was featured on Hacker News. This simple program makes DNS outages suck less.




PAF - PostgreSQL Automatic Failover: High-Availibility for Postgres, based on Pacemaker and Corosync

  •    Perl

High-Availibility for Postgres, based on industry references Pacemaker and Corosync. Pacemaker is nowadays the industry reference for High Availability. In the same fashion than for Systemd, all Linux distributions moved (or are moving) to this unique Pacemaker+Corosync stack, removing all other existing high availability stacks (CMAN, RGManager, OpenAIS, ...). It is able to detect failure on various services and automatically decide to failover the failing resource to another node when possible.

ha-postgres-docker-stack - Postgres + patroni + wal-e + haproxy + etcd

  •    PLpgSQL

This is a docker compose file and some helper scripts to demonstrate how to deploy a highly available postgres cluster with automatic failover using docker swarm. Use the docker-stack.test.yml when running the suite or testing the stack on docker for mac for example.

docker-compose-ha-consul-vault-ui - A docker-compose example of HA Consul + Vault + Vault UI

  •    

This project is an example of using Consul, Vault, and Vault UI in a high availability (HA) configuration. Conveniently packaged as Docker services for provisioning via Docker Compose. Remove --scale vault=3 if you want to start one instance of Vault. docker-compose up -d would bring only Consul up in HA configuration.


ServerSideApplication-Series - :books: 服务端应用程序开发与系统架构/微服务架构与实践,基础篇 | Spring 篇 | Node

  •    

:books: 服务端应用程序开发与系统架构/微服务架构与实践,基础篇 | Spring 篇 | Node.js 篇 | DevOps 篇 | 信息安全与渗透测试篇

navigators-guide - Book and code examples that help to build infrastructure on DigitalOcean

  •    Shell

This repository contains the book: The Navigator's Guide to DigitalOcean along with the code examples used throughout the book.

Backend-Series - :books: 服务端应用程序开发与系统架构/微服务架构与实践,基础篇 | Spring 篇 | Node.js 篇 | DevOps 篇 | 信息安全与渗透测试篇

  •    

:books: 服务端应用程序开发与系统架构/微服务架构与实践,基础篇 | Spring 篇 | Node.js 篇 | DevOps 篇 | 信息安全与渗透测试篇





We have large collection of open source products. Follow the tags from Tag Cloud >>


Open source products are scattered around the web. Please provide information about the open source projects you own / you use. Add Projects.