By speaking of the relative roles of microservices, rather than the direction of data flow, we can have more efficient conversations about them.
Creating new microservices individually via feature flags ensures a low-risk release that will be easy on your devs, network administrators, and end-users
As our software development processes have evolved we’ve mostly said goodbye to the idea of defined product versions. Many modern product delivery teams are taking this a step further – even the concept of a “product release” is starting to fade. Instead our products are becoming a fluid, rapidly evolving set of features, assembled uniquely for any given user.
This is one post in a series about managing the breakup of a monolithic architecture into a small service. In the first post of the series we looked …
In this blog post, we walk through an example of how each customer can be given a different experience depending on the version of product they have installed. While the driving example was Split’s own SDKs, the example is equally relevant to mobile application developers juggling with older versions of their installed apps.