Public Api architecture

Let's talk about proxies, load balancers, API gateways and API management systems...which ones, how, why and why not. When to use existing third-party software? When to build your own? What tools in the Java ecosystem are there to help you? We should also have a talk about the non-infrastructural part. You know...custom endpoints, integrations, client libraries, documentation, consistency, evolution all through a sustainable and scalable Api governance. All this so that one team can satisfy 30 other teams exposing over 500 endpoints used by thousands of clients sending 100M requests per day in a wide variety of use cases. I want to share our experience how we came to this point and how we are dealing with all this. How and where we failed and succeeded. All in order to try and help you (re)design your own public architecture depending whether you're barely starting, a growing startup or a big company.