The document discusses the evolution of APIs, highlighting the shift from SOAP and REST to more modern microservice architectures. It emphasizes the importance of open-source solutions like Kong, which has over 4 million downloads and is built on nginx, and showcases its extensibility and performance. Additionally, it outlines the two main communication methods for microservices: synchronous service-to-service communication and asynchronous event-driven communication.

1. The API R(E)volution
The API (R)Evolution

2. The API R(E)volution
● Open-Source
● 4M+ Downloads since 2015
● Built on top of NGINX
● Extensible with Plugins (60+ available)
● Sub-millisecond latency on most use-cases
● Cloud-Native & Platform Agnostic
● Fast and Scalable. Up and running in minutes
● CE and EE editions
Millions of Community (CE) downloads
across multiple platforms.
■ 12,000+ Stars in GitHub
■ 70+ Contributors
■ 107 Meetups
■ 10K Community Members
A few words about Kong

3. The API R(E)volution
I’m Marco Palladino
CTO @ Kong
Located in San Francisco and…
- Singapore
- New York
- London
- Canada
- México
- Brazil
- ...and Finland.
* Used to be Mashape

4. The API R(E)volution
APIs are continuously evolving
SOAP
XML
REST
Primarily JSON
REST+RPC
JSON- gPRC - etc

5. The API R(E)volution
Because architectures are evolving
All product names, logos, and brands are property of their respective owners. All company, product and service names used in this website are for identification purposes only. Use of these names, logos, and brands does
not imply endorsement.

6. The API R(E)volution
Explosion of clients Inside and Outside the organization
FaaS
Other Microservices
Partners
Web Applications
APIs

7. The API R(E)volution
SOAP
● Easier than COM, CORBA, etc
● But still hard to consume
● Heavyweight
● Hard to read
(1999 - 2007)

8. The API R(E)volution
JSON REST
● Easy to consume
● More compact
● Follows HTTP best practices
(2007—Today)

9. The API R(E)volution
At this point applications are still monolithic

10. The API R(E)volution
Primarily edge use-cases

11. The API R(E)volution
But applications got smaller
“Keith Fulton, CIO Bank Solutions, Fiserv”

12. The API R(E)volution
Microservices
vs

13. The API R(E)volution
Microservices - Decentralized

14. The API R(E)volution

15. The API R(E)volution
Running Microservices
Is like running a city

16. The API R(E)volution
A new pattern is emerging

17. The API R(E)volution
Open-Source
is conquering the
World
Enterprise.

18. The API R(E)volution
GW
HTTP(s) HTTP(s)
Service Service
Queue
Queue Producer Queue Consumer
Service Service

19. The API R(E)volution
Service-to-Service
Microservices and clients directly consume and
invoke other microservices
Ideal for external clients and/or response
aggregation use-cases, or when an immediate
response is required
Done via HTTP, TCP/UDP, gRPC, etc
Example: Making a request to retrieve an immediate
response of some sort. External access use-cases
(ie, retrieve list of users)
Asynchronous
Microservices and clients push events into an event
collector that’s being consumed by other
microservices
Ideal for microservice-to-microservice
communication for changing state without requiring
an immediate response
Done via Kafka, RabbitMQ, AWS SQS, etc
Example: Making a request that doesn’t require an
immediate response (ie “orderCreated” event that
triggers an invoice creation by another microservice)
Two ways for Microservice communication:

20. The API R(E)volution
And the Landscape is Rapidly Evolving:

21. The API R(E)volution

22. The API R(E)volution
Not only our applications,
but our clients will have to adapt too.
RESTSOAP REST+RPC
AJAXSync IO Web Sockets

23. The API R(E)volution
ありがとうございました
RESOURCES:
https://konghq.com
https://github.com/Kong/kong
Find me on Twitter @thefosk