Up until a few days ago, I mainly consumed Web Services using the “standard” model – SOAP. Now while that is all great and useful, it’s also a bit painful to debug and work with. So when I discovered REST (Representational State Transfer), it looked like a great alternative. At first glance, REST just looks like a normal URL, and in many cases when it comes to receive data,... moreUp until a few days ago, I mainly consumed Web Services using the “standard” model – SOAP. Now while that is all great and useful, it’s also a bit painful to debug and work with. So when I discovered REST (Representational State Transfer), it looked like a great alternative. At first glance, REST just looks like a normal URL, and in many cases when it comes to receive data, it is. As a web developer, you may (should) know what GET and POST is and how they work, and in order to receive data, you often just do a simple GET Request. So why overcomplicate things by wrapping it in a SOAP Envelope? view page