When app a, b and c need to know about each other . . .
One approach is a deployment system with config files where you enter the location of each of the apps. This works ok unless things change a lot or you have lots of apps that need to know about each other.
The slam dunk is to not configure anything. When you deploy your app it tells the service discovery system about itself, and the service discovery system takes care of letting other apps know what they need to know.
How does this work in practice?
We deploy app a. It tells the service discovery system it's at 220.127.116.11:294. The service discovery system sees that app a's info has changed. It updates the config files of the other apps and tells them their config files have changed. The service discovery system could update environment variables as well.
With this approach your applications don't know anything about the service discovery system. They just need a way to be notified about config changes. Or you could just restart the app whenever there's a change.
This approach can be used for anything else apps need to know about each other, feature flags, etc.
Consul along with consul-template and envconsul allow you to do all this fairly simply.
One of the defining features of Elasticsearch is that it’s exposed as a (loosely) RESTful service over HTTP.
The benefits are easy to spell out, of course: the API is familiar and predictable to all web developers. It’s easy to use with “bare hands” via the curl command, or in the browser. It’s easy to write API wrappers in various programming languages.
Nevertheless, the importance of the HTTP-based nature of Elasticsearch is rooted deeper: in the way it fits into the existing paradigm of software development and architecture.
So I have a domain from GoDaddy and I want to manage just one or more subdomains of that domain on AWS Route 53. Actually I tried to do this with my NetworkSolutions account, but on phone they said it is not possible.
Building Scalable and Responsive Big Data Interfaces with AWS Lambda
July 10, 2015 FireEye AWS Lambda
This is a guest post by Martin Holste, a co-founder of the Threat Analytics Platform at FireEye where he is a senior researcher specializing in prototypes.
At FireEye, Inc., we process billions of security events every day with our Threat Analytics Platform, running on AWS. In building our platform, one of the problems we had to solve was how to be efficient and responsive with user-driven event analysis at this scale. Our analysis falls into three basic categories: threat intelligence matching, anomaly detection, and user-driven queries. We relentlessly search for ways to improve our efficiency and responsiveness, and AWS Lambda is a solution that has shown significant value in fulfilling these goals by providing a simple platform for scaling user-driven workloads.
The DigitalOcean ELK Stack One-Click Application provides you with a quick way to launch a centralized logging server. The ELK Stack is made up of three key pieces of software: Elasticsearch, Logstash, and Kibana. Together they allow you to collect, search, and analyze logs files from across your infrastructure. Logstash collects and parses the incoming logs, Elasticsearch indexes them, and Kibana gives you a powerful web interface to visualize the data.
This tutorial will show you how to launch an ELK instance and set up Logstash Forwarder on your other servers to send their logs to your new centralized logging server.
A few weeks ago here at Hone, we decided to spin a new server cluster in DigitalOcean’s NYC3 data center.
DigitalOcean introduced ‘private’ networking just over a year ago. However, it turns out that DigitalOcean actually refers to this as Shared Private Networking—and many of the comments under their announcement point out that their private networking isn’t really too private.
We decided to use OpenVPN to layer a secure network on top of DigitalOcean’s shared private networking.
Visa and FireEye Join Forces to Help Merchants, Financial Institutions Defend Against Targeted Attacks on Consumer Payment Data
New Visa and FireEye cyber watch program will provide advanced cyber protection capabilities for merchants of all sizes
San Francisco and Milpitas, Calif. – June 3, 2015 – Visa Inc. (NYSE: V) and FireEye, Inc. (NASDAQ: FEYE) today announced their intention to co-develop tools and services to help merchants and issuers protect against advanced cyber attacks targeting payment data. The first of its kind Visa and FireEye Community Threat Intelligence (CTI) offering will bring together threat information from both companies, allowing merchants and issuers to quickly detect and respond to attacks against their IT and payment infrastructure. Under the offering, FireEye will operate the easy-to-use web based service to enhance stakeholders’ knowledge of attacks targeting the ecosystem, providing a significant improvement over current industry practices of sharing threat intelligence via e-mail or static documents.
Cybersecurity company FireEye (NASDAQ: FEYE) keeps posting numbers that suggest a sustained demand for its threat detection, prevention, and resolution services. The company's recently filed first-quarter 2015 results revealed a leap in revenue of 69% from the prior-year quarter.