3scale/apisonator

- Feature Name: (fill me in with a unique ident, my_awesome_feature)
- Issue: (tracking issue if applicable, leave this empty)
- RFC PR: (leave this empty)
- Implementation PR: (leave empty, fill in when implementing)

# Summary
[summary]: #summary

One paragraph explanation of the feature.

# Motivation
[motivation]: #motivation

Why are we doing this? What use cases does it support? What is the expected outcome?

# Detailed design
[design]: #detailed-design

This is the bulk of the RFC. Explain the design in enough detail for somebody
familiar with Backend to understand, and for somebody familiar with Ruby to
implement.
This should get into specifics and corner-cases, and include examples of how the
feature is used.

# Drawbacks
[drawbacks]: #drawbacks

Why should we *not* do this?

# Alternatives
[alternatives]: #alternatives

What other designs have been considered? What is the impact of not doing this?

# Unresolved questions
[unresolved]: #unresolved-questions

What parts of the design are still TBD?