Talk

INNOQ Technology Lunch: Why “API-first” might not be a good idea

Many enterprise IT departments have become big fans of an “API-first“ strategy. I think that in general, this is a bad idea. When you start with APIs, you really have to have a very good grasp of what that API’s users will need. You typically don’t. Instead, you try to come up with things that will “obviously” be re-usable, and end up with things that are not even useful. Most often, APIs are shaped, and almost always restricted, by the capabilities of underlying systems they encapsulate. That’s great if these are great. They typically aren’t. An API-first strategy assumes that great applications can be built by “just” “orchestrating” the capabilities exposed through APIs. That’s true for some applications, but not for many, and typically not for great ones.

In this talk, I‘ll talk about why you should prefer a strategy for modular application delivery, not only including, but starting from, end-user needs. APIs are a meaningful means to an end for that. Starting with them is going to end badly, independently from your choice of protocol or data format.

Date
2022-03-02
Time
12:15 - 13:15
Online Event
INNOQ Technology Lunch (02.03.2022)
  • Slide 1
    1/30
  • Slide 2
    2/30
  • Slide 3
    3/30
  • Slide 4
    4/30
  • Slide 5
    5/30
  • Slide 6
    6/30
  • Slide 7
    7/30
  • Slide 8
    8/30
  • Slide 9
    9/30
  • Slide 10
    10/30
  • Slide 11
    11/30
  • Slide 12
    12/30
  • Slide 13
    13/30
  • Slide 14
    14/30
  • Slide 15
    15/30
  • Slide 16
    16/30
  • Slide 17
    17/30
  • Slide 18
    18/30
  • Slide 19
    19/30
  • Slide 20
    20/30
  • Slide 21
    21/30
  • Slide 22
    22/30
  • Slide 23
    23/30
  • Slide 24
    24/30
  • Slide 25
    25/30
  • Slide 26
    26/30
  • Slide 27
    27/30
  • Slide 28
    28/30
  • Slide 29
    29/30
  • Slide 30
    30/30

Swipe for more

Scroll or use your arrow keys for more

Scroll for more

Use your arrow keys for more

 Download Slides

TAGS