I like RAML because, it gives a flexibility to the developer to customise micro services into convenient way. Designing specification follows a simple YAML structure(well known industry approach) which is easy for anybody to understand as it just contains nouns(i.e. resources) and verbs(i.e methods). RAML is strongly capable to support Security traits and schemes which can be appleid at different levels of API, example API level, resource level and method level. Review collected by and hosted on G2.com.
There are very few areas where a developer dislike RAML constraints, below are the couple of them that I feel, 1. no easy way of defining an API to accept conditional input parameter set to apply in various scenarios(either or way). A complex schema datatype approach has to be followed in order to customer conditional types. 2. type, required constraints on parent fields when a child datatype inherit properties from parent Review collected by and hosted on G2.com.



