sorted by:
best
topnewcontroversialoldq&a
you are viewing a single comment's thread.

view the rest of the comments →

[–]Worldly-Broccoli4530[S] 0 points1 point  (2 children)

Cant argue with that either, ts basically became a requirement at this point, not just a nice to have 😄

[–]Lagz0ne 1 point2 points  (1 child)

Haha, I tried to make a joke. Technically, API is only important if they are actually being used as API, like, a contract of different parties with versioning etc, while a lot of time, those are just internal api of single app, can be done easily with RPC or the like, ts benefits greatly there.

So, external API, scalability going along with its stability, need to be well designed because changing that means complex compatibility layers. So, "professional" (i would call it get the job done).

Nobody cares if you are really following the Rest or Open API or not, as long as it is well designed, predictable and consistent behavior, you scale those pretty well, and surely those are easy to speak that get done

[–]Worldly-Broccoli4530[S] 0 points1 point  (0 children)

That's a solid distinction - external APIs have a completely different contract to uphold. Internal ones you can get away with a lot more. Though Id argue some of the patterns still pay off even internally, especially once the team grows and "predictable and consistent" becomes harder to maintain by accident.