From a16876d8457313824c7ba41f487922444fe2063c Mon Sep 17 00:00:00 2001 From: Ryan Brandt Date: Wed, 16 Dec 2015 14:17:57 -0700 Subject: [PATCH] Minor readme fixes Change-Id: If3d9bda0ebb62edaf05a6c4b35ba2ef717b582d3 --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index f88e7a95..3f207671 100644 --- a/README.md +++ b/README.md @@ -3,7 +3,7 @@ monasca-persister The Monitoring Persister consumes metrics and alarm state transitions from the Message Queue and stores them in the Metrics and Alarms database. -Although the Persister isn't primarly a Web service it uses DropWizard, https://dropwizard.github.io/dropwizard/, which provides a nice Web appliction framework to expose an http endpoint that provides an interface through which metrics about the Persister can be queried as well as health status. +Although the Persister isn't primarily a Web service it uses DropWizard, https://dropwizard.github.io/dropwizard/, which provides a nice Web application framework to expose an http endpoint that provides an interface through which metrics about the Persister can be queried as well as health status. The basic design of the Persister is to have one Kafka consumer publish to a Disruptor, https://github.com/LMAX-Exchange/disruptor, that has output processors. The output processors use prepared batch statements to write to the Metrics and Alarms database.