blog

[lekhajee]

No description provided.

[wbrothers]

How about "Functional tests are used to validate the API contracts and behavior of Auto Scale." The current version seems awkward. Same idea for the System Integration paragraph.

[ynachiket]

Sentences:

Successfully testing Auto Scale meant not only testing the features of Auto Scale itself, but also that it is consistent irrespective of any failures in the upstream systems.

We now have Mimic integrated within our development environment..

Restructuring:
Mimic is an API compatiable mock service ... I would put this as the opening paragraph. Then have sections like motivation/why mimic etc to tell the story.

Small suggestion:
Talk more about the plugin architecture, a small example and why to build it as a plugin.

https://docs.google.com/document/d/17dM5I9_qfNFU5tzwdXkkz4dj_wdNJxfQn7Rb7L0Xk3g/edit#

[lekhajee]

@ynachiket : Thanks for the feedback.

About the restructuring, I am trying it say it like a story and I was thinking giving away what Mimic is in the beginning, might set a certain perspective of what it is, instead of reading through the problems and then understanding what it is solving.

This was just to give an overview of Mimic and how it came into existence, the plan is for @glyph to be following up this blog, with one that talks about the Plugin Architecture, the time control and other cool upcoming features. I could mention that maybe.

[cyli]

I love the examples of positive and negative functional tests. Possibly talking about minEntities and maxEntities might be a bit too specific of an Autoscale detail (and this blog post is mostly about Mimic). Maybe just "create scaling group results in a response code 400 when the request is malformed" ?