Availability
The Netflix OSS "stack"
The Netflix Open Source
Software suite of products. http://netflix.github.io/#repo.
Karyon: The nucleus of a Composable Web Service. More: http://techblog.netflix.com/2013/03/karyon-nucleus-of-composable-web-service.html
Hystrix is a latency and fault tolerance library designed to isolate points of access to remote systems, services and 3rd party libraries, stop cascading failure and enable resilience in complex distributed systems where failure is inevitable. https://github.com/Netflix/Hystrix http://techblog.netflix.com/2012/02/fault-tolerance-in-high-volume.html
ZooKeeper: ZooKeeper is a centralized service for maintaining configuration information, naming, providing distributed synchronization, and providing group services. http://www-01.ibm.com/software/data/infosphere/hadoop/zookeeper/ https://www.hakkalabs.co/articles/apache-zookeeper-introduction/ https://www.usenix.org/legacy/event/usenix10/tech/full_papers/Hunt.pdf
Curator - ZooKeeper client wrapper and rich ZooKeeper framework http://netflix.github.com/curator
Archaius - Library for configuration management API https://github.com/Netflix/archaius http://techblog.netflix.com/2012/06/annoucing-archaius-dynamic-properties.html http://jlordiales.me/2014/10/07/configuration-management-with-archaius-from-netflix/
Ribbon is a Inter Process Communication (remote procedure calls) library with built in software load balancers. The primary usage model involves REST calls with various serialization scheme support. https://github.com/Netflix/ribbon
Eureka - Service registry for resilient mid-tier load balancing and failover. https://github.com/Netflix/eureka
Zuul is an edge service that provides dynamic routing, monitoring, resiliency, security, and more: https://github.com/Netflix/zuul
Asgard: Web-based Cloud Management and Deployment: http://techblog.netflix.com/2012/06/asgard-web-based-cloud-management-and.html https://github.com/Netflix/asgard
Cloud Services Powered by IBM SoftLayer and NetflixOSS: http://www.slideshare.net/aspyker/cloud-servicespoweredbyib-mandnetflixoss
Cloud Services Fabric (and NetflixOSS) on Docker – Demo at IBM Impact 2014: http://ispyker.blogspot.com/2014/05/cloud-services-fabric-and-netflixoss-on.html
A sample reference architecture application demonstrating the use of many Netflix Open Source projects: https://github.com/cfregly/fluxcapacitor
http://nirmata.com/2014/08/getting-started-with-microservices-using-netflix-oss-docker/ |
Micro Services Architecture versus SOA
Micro-service architecture and the human body
No it does not. It might hurt big-time, and I might need to get some help on the long term, but the first few minutes, seconds or maybe even hours, my brain will probably ignore the signals sent by the nerve receptors, and I should probably try to reduce the amount of blood loss I have. My adrenaline levels will rise, I will ignore the pain signals, and I might be able to run faster and longer then I ever imagined. The information highwayThink about the way our body communicates with our brain: the brain has two main paths for communicating with the body: the nerves and the blood vessels. They both have a distinct function:
This is a gross simplification, but is in essence how your body works. Some remarks
This brings us to the MSADoes your brain know how your nerves and blood vessels are organised? I don’t think so; what matters to the brain is cause and consequence. MSA’s work just like that:
The gist of itHere’s the difference between SOA and MSA: as long as the “hormones”(=used to generate business metrics) do not signal a problem, you don’t care about the organs (i.e. individual services), f.e. if you don’t know what a service is doing, just shut it down. If the business metrics don’t show it, it was useless. If people start making a fuss about it, add the proper business metric, and reboot the service. Have an extra feature or a customer-specific thing? Just let both services run, and let the one processing those responses decide which answer to take. Does a service fail? As long as your business metrics don’t show it, you don’t have a problem… In fact, because your business rules might change every once in a while, services will get redundant. Embrace failure and shut-down services at random during office hours. If your business metrics show failure, make sure that there are always at least 2 of them running, so the next time one of them fails, you will no longer have that issue… Or just write another service - after all, it’s just a couple of 100 lines - that does what it is supposed to do, and maybe even way better then before. If a system fails, you go back to the nerves to check what might be the cause, or just decide to fix it by launching another service. Experience will tell you. Where all of this is coming fromAs Nassim Taleb explains in Antifragile: Things That Gain from Disorder The essence of MSA is monitoring the “what”, while EDA and SOA typically monitor the “how”. You don’t care about how the system works, just that it works… If it fails, you fix it by adding another service or adjusting the existing service. By making failure a non-event, you become essentially resistant to it. |
CentOS Encrypted Incremental Backup for AWS
There are many documented solutions available on the internet for achieving full and incremental backups for CentOS servers to AWS S3 or even to AWS Glacier. Most of them rely on a tool called Duplicity, which relies on Python and BOTO. Backups can also be encrypted for added security to your data. Check it out!!! |
Tutorial - High Availability for AWS
This article provides all the necessary resources, including an easy-to-use script,and instructions on how you can leverage bidirectional monitoring between two NAT instances to implement a high availability (HA) failover solution for network address translation (NAT). |
Create an OpenBSD 5.5 HAproxy HTTPS TCP proxy
Assuming you already have a working OpenBSD 5.5 system, this task if very straightforward.
First, install HAproxy from your favorite repository:
pkg_add http://mirror.internode.on.net/pub/OpenBSD/5.5/packages/amd64/haproxy-1.4.24.tgz
pkg_add http://mirror.internode.on.net/pub/OpenBSD/5.5/packages/amd64/nano-2.2.6.tgz
You can then edit the HAproxy configuration file:nano /etc/haproxy/haproxy.cfg
Last step, make sure that the service starts when the server is rebooted: nano /etc/rc.conf
|
Nutanix "Cluster in a box" solution and more!
How Nutanix WorksWatch this animation and learn how the Nutanix Virtual Computing Platform Works. http://www.nutanix.com/how-nutanix-works/ |
vSphere Storage Appliance
http://www.vmware.com/products/vsphere-storage-appliance/ VMware vSphere® Storage Appliance™ is a software-based shared storage solution that enables high availability and automation in vSphere without shared storage hardware. |
Oracle High Availability
This excellent document by Oracle defines some of the High Availability concepts and terminology. |