Pick and Choose:
The micro services approach is not an all-or-nothing decision; the big benefit of the micro service approach means you can pick and choose which services you want to use. Additionally, the micro services can often be used in both the CMS and file-based development.
For example:
An answerSpace in the CMS environment can store logs in the Analytics service, and still access the PDF Builder services.
You may even choose to write your app using a completely different tool, but harness BlinkMobile’s BaaS functionality as a middleware layer.
You could download your older CMS based BIC3 answerSpace and use it to produce an app using the new Hybrid App Buildbots.
Each service is designed to be able to be used either individually, or as a whole, depending on your needs.
A big benefit of the BlinkMobile ecosystem means that no matter which services you choose (some or all), you can rest assured that each service has been specifically designed to work with the other services meaning integration, and maintenance will be a seamless experience for both developers and project owners.