What exactly is API-First?

Started by
26 comments, last by rpiller 8 years, 6 months ago

I can't help but keep returning to the fact that the OP's article is a terrible, strong-arm sales pitch aimed at non-technical managers of tech teams, trying to trick them into being hyped over a nonsense manufactured trend, which the author intends to profit from

Well, that sounds like every trend in the last 20 years. Anyone had their team agile-buzzword'ed lately?


Unfortunately no, our team got agile-made-up-word'ed instead since the company is innovative and unique. (I like the innovation but the made up words are confusing, with the usual buzzwords you can at least sort-of understand what the suits are referring to)
[size="1"]I don't suffer from insanity, I'm enjoying every minute of it.
The voices in my head may not be real, but they have some good ideas!
Advertisement
The terms "scrum master" and "story captain" still make me laugh. smile.png

I'm always gobsmacked at the number of people in software companies who can with a straight face extoll the virtues of agile development, while actually using a purely waterfall planning process to feed into a vaguely Kanban-like priority queue for the dev team.

Tristam MacDonald. Ex-BigTech Software Engineer. Future farmer. [https://trist.am]


I'm always gobsmacked at the number of people in software companies who can with a straight face extoll the virtues of agile development, while actually using a purely waterfall planning process to feed into a vaguely Kanban-like priority queue for the dev team.
Hahaha so true.

"I AM ZE EMPRAH OPENGL 3.3 THE CORE, I DEMAND FROM THEE ZE SHADERZ AND MATRIXEZ"

My journals: dustArtemis ECS framework and Making a Terrain Generator

Just had a conference today and they talked about micro services. Seems the trend these days is to push a lot of little web api's and then make your products like legos by picking the services you need to complete the project. So literally your app could be made up of 20 different web api's, where each does their very own very specific task. As a developer I like this approach because you can really break the tasks down for your team and keep things very specific and simple to work on. Just better make sure when you change an api you are really careful since it could be used in a hundred different apps.

Meh.

API is just some methods with bunch of parameters, RESTful HTTP stuff.

Looks like a tech journalist with no real technical knowledge got to talk to some bigshot developer at some crowded convention, and the word API got thrown around in the conversation. Having first heard of the word API, this journalist think it's the next big thing. Insert big company names like Google, Intel, HP, and Netflix, API makes it sound like it's a whole new idea that's driving the industry now.

Just had a conference today and they talked about micro services. Seems the trend these days is to push a lot of little web api's and then make your products like legos by picking the services you need to complete the project. So literally your app could be made up of 20 different web api's, where each does their very own very specific task. As a developer I like this approach because you can really break the tasks down for your team and keep things very specific and simple to work on. Just better make sure when you change an api you are really careful since it could be used in a hundred different apps.

Microservices is not a new idea. It's old. It wasn't feasible back in the day because the amount of effort to maintain hundreds of services. For each service, you need a physical machine, sysadmins to maintain the machine, developers to maintain the app, and some deployment process for updates. One service is fine, but when you have hundreds of them, who's going to take care of it all?

Now with virtualization everywhere, Puppet/Chef/Ansible/Salt scripts for server maintenance and deploys, and recently Docker that can simplify deployment dependencies, the microservices idea resurfaced again. It's not a paradigm shift. It's like dusting off an old keyboard and you realized how awesome those springy keys were.

Just had a conference today and they talked about micro services. Seems the trend these days is to push a lot of little web api's and then make your products like legos by picking the services you need to complete the project. So literally your app could be made up of 20 different web api's, where each does their very own very specific task. As a developer I like this approach because you can really break the tasks down for your team and keep things very specific and simple to work on. Just better make sure when you change an api you are really careful since it could be used in a hundred different apps.

Microservices is not a new idea. It's old. It wasn't feasible back in the day because the amount of effort to maintain hundreds of services. For each service, you need a physical machine, sysadmins to maintain the machine, developers to maintain the app, and some deployment process for updates. One service is fine, but when you have hundreds of them, who's going to take care of it all?

Now with virtualization everywhere, Puppet/Chef/Ansible/Salt scripts for server maintenance and deploys, and recently Docker that can simplify deployment dependencies, the microservices idea resurfaced again. It's not a paradigm shift. It's like dusting off an old keyboard and you realized how awesome those springy keys were.

Didn't say it was new, just said it's the recent trend. Although if an idea was thought of before but couldn't be implemented then when it finally is implemented it really is new. Otherwise that's like saying if time travel was finally invented you'd go around saying that's nothing new just because we've thought about it before ya know.

This topic is closed to new replies.

Advertisement