2 ms·
You have the following constraints: 1. You do not control the update cycle of the client layer 2. You want to decouple platform support. You can do this for t
by renewiltord 4y ago
You have the following constraints:
1. You do not control the update cycle of the client layer
2. You want to decouple platform support. You can do this for technical reasons and for org reasons (you can scale up teams independently)
This way, you can have the client be simple with a slow update cycle. You restrict its slowness to it alone and not to the whole product. You can then scale your backend services teams independently. You can throw away entire backend services while your front-end team modifies their API layer to ensure that legacy clients can handle things. The front-end team working on a client with a slow upgrade cycle can mock API responses or something. Meanwhile, the front-end team that's working on a client with a fast upgrade cycle can just move on.
You can thin your platform-specific client and move more logic into the platform-specific backend while keeping your platform-agnostic backend moving fast.