5 ms·
There's a lot of advantages to API-first. 1. You're not bound to one supplier, you can integrate multiple. 2. You don't need to manage the security for a larg
by tmikaeld 6y ago
There's a lot of advantages to API-first.
1. You're not bound to one supplier, you can integrate multiple.
2. You don't need to manage the security for a large application, instead, the responsibility is distributed to each API.
3. Scaling becomes a non-issue (unless you abuse the rate-limits/grow too fast).
4. The cost of sysops and development goes waaay down.
The dis-advantages: it might be way more expensive, but at least you'll have shipped! (And of course GDPR/data control might be an issue)
- toomuchtodo 6y agoAgree with all of these points, but you’ll need the understanding and competence to rapidly refactor your pain points when you encounter them. Tangentially, I believe low and no code platforms are perfect for prototyping gluing APIs together to prove out concepts, and once you’ve demonstrated traction (whatever that looks like for your product), it’s time to refactor out into your own business line app to control your product’s destiny.
- nuclearnice1 6y agowhich no code platforms have you had success with? I saw AWS got in the game with honeycode.
- toomuchtodo 6y agoAny of the well known products are fine products to be using. Which is right for your use case is dependent on the use case and product features.
- tomashertus 6y ago> You don't need to manage the security for a large application, instead, the responsibility is distributed to each API. Wrong. Third-Party risk management is your responsibility as a service provider. Your customers will want to know what kind of services your application depends on. I would recommend being very thorough in deciding who you will partner with and send data to. If you are a small startup, it most likely doesn't matter, but once you start getting serious business opportunities then data governance is the game.
- tmikaeld 6y agoYou're right, that's why I added GDPR/Data control might be an issue. If you read it again, you can see I'm talking about management of security, not the legal issues of it.