What’s the difference between REST & RESTful

by

Representational state transfer (REST) is a style of software architecture. As described in a dissertation by Roy Fielding, REST is an “architectural style” that basically exploits the existing technology and protocols of the Web.

RESTful is typically used to refer to web services implementing such an architecture.

More Related Contents:

  1. Logout: GET or POST?
  2. What am I not understanding about REST?
  3. What exactly is RESTful programming?
  4. What’s the difference between “Layers” and “Tiers”?
  5. Component based game engine design [closed]
  6. Domain Driven Design: Domain Service, Application Service [closed]
  7. What is RESTful programming?
  8. Why do stacks typically grow downwards?
  9. What is N-Tier architecture?
  10. Servicestack – architecture & reusing POCOs for everything
  11. what is a store buffer?
  12. When are you truly forced to use UUID as part of the design?
  13. Transactions across REST microservices?
  14. On 32-bit CPUs, is an ‘integer’ type more efficient than a ‘short’ type?
  15. Microservices – best practices to retrieve the related data to specific user from the other micro services with the minimal memory/time loss
  16. Best way to store Badge criteria?
  17. How do you organize your small reusable cffunctions?
  18. dma vs interrupt-driven i/o
  19. Difference between a “coroutine” and a “thread”?
  20. How to list supported target architectures in clang?
  21. What is opinionated software?
  22. What is a “feature flag”?
  23. Why do we need RESTful Web Services?
  24. How to detect target architecture using CMake?
  25. CMake Multiarchitecture Compilation
  26. DDD, Anti Corruption layer, how-to?
  27. Where should I store photos? File system or the database? [duplicate]
  28. When to Redis? When to MongoDB? [closed]
  29. What are best practices for REST nested resources?
  30. What’s the best RESTful method to return total number of items in an object?

Leave a Comment