Fig 1-1 shows the wonderful, crazy, mixed up environment that is the modern Web.
A service boundary is the point at which your systems meet the bigger web. It's usually a Web server which offers the ability for others to interact with your service in a constrained way.
An agent can be a Web browser on the human web (driven by a human brain providing the 'logic") or it can be a computerised agent with software providing the logic. The Web doesn't care.
Caches support scalability (and hide some unavailability) because they stop the same thing being computed over an over. Instead of a request repeatedly triggering an expensive computation in your service, sometimes it is possible to keep the answer around in a cache and serve it from there. The Web's protocols will used cached responses where they can with very little programming effort. Since caches are cheap, use them to your best advantage.
Hope that helps.
> On 26 Dec 2020, at 16:03, Varuna <varunase...@gmail.com
> Can you please explain the Figure 1-1. How do the caches support resources and URIs for scalability? What is a Service boundary? In the the picture, who is an agent?
> Thank you
> You received this message because you are subscribed to the Google Groups "restinpractice" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to restinpractic...@googlegroups.com
> To view this discussion on the web visit https://groups.google.com/d/msgid/restinpractice/605bbe95-0bb1-4eba-ab01-33ca00863318n%40googlegroups.com