Comments on: Developer Ecosystem Acquisitions Makes Build vs Buy Decisions Harder

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Fri, 11 Mar 2016 06:19:41 +0000

In reply to Tony de Sousa. Tony, thanks for sharing. Note that Parse server is now open source, which means it is even better suited for someone who wants more control over his infrastructure :-)

By: Tsahi Levent-Levi

Tsahi Levent-Levi — Fri, 11 Mar 2016 06:19:10 +0000

In reply to Robert Welbourn. Robert, It is a solid recommendation, but there are two tweaks I'd do to it:

Still pick the best PaaS provider for the job
Build that adaptor for my needs and not necessarily based exactly on the API I am using

By: Tony de Sousa

Tony de Sousa — Fri, 11 Mar 2016 05:38:53 +0000

My strategy is not to be taken in by the hottest new thing and snappy PowerPoint presentation. Don’t ride the bleeding edge, be patient, look for teams with a long track record ( a business cycles at least ). Have a plan A, B, and C. Hooe for the best and plan for the worse.

Remember you comp. sci. lessons, encapsulation, modularity, late coupling and abstraction.

Btw, thanks for the info on Parse, one year ago I planned to learn Parse in conjunction with Twilio, luckily I procrastinated and saved myself from learning something now defunct.

By: Robert Welbourn

Robert Welbourn — Thu, 10 Mar 2016 14:28:28 +0000

I’m in the situation of evaluating WebRTC PaaS providers and their APIs right now. The recommendation I made to my client was to pick a service, clone its API, and proxy to it. If they then needed to switch provider, this would insulate their client-side code (especially mobile apps) to some degree, and they would then be left to adapt the proxy.