Closing keynote with Apigee CTO, Anant Jhingran

1. What we learned

2. What’s this about?

3. Google!Multi-tenant SaaS
for “the cloud”
2007
Physical appliances
for data centers
2012 2017
Along the way we learned some things about technology,
about ourselves, and of course, about APIs.
What’s this about?

4. Gee, what changed since 2007?
What Happened in all that time?
Smartphones JSON
APIs
AndroidiPadGo
Swift

5. What assumptions did we make that
turned out to be good ideas?

6. we built everything assuming that it would be run
in the cloud.

7. {
No Data centers
No Racks
No Server
No Power distribution
No Cooling
No Physical security

8. we assumed that everything had to
be redundant and replicated
across data centers.
We embraced eventual consistency

9. NOC

10. What didn’t work out well?
Ops Blog-chasing
Agile
DevOps
Monolithism

11. We built too much software in a “monolithic” way.

12. NoSQL

13. Agile
DevOps

14. We launched Edge to “the cloud” in 2012.
A lot has changed since then as well.
What has changed?
Containerization ServerlessMicroservices

15. From esoteric to mainstream
Containerization

16. Microservices
Buzzword of the year

17. A new paradigm
Serverless

18. What did we learn from
?

19. securityYou can never be too careful about privacy

20. It’s OK to buck the trend

21. You should never compromise on
developer productivity

22. What does that mean for you
and your organization?
Containers Security RegionsMicroservices DevOps

23. Security
You can’t be too careful!
Cryptography, TLS, Algorithms,
Encryption & Auditing

24. Data
Be open to alternatives
NoSQL? RDBMS? Or both!

25. Containers
Go for it!
Faster & cheaper

26. Microservices
proceed with caution!
More agility and less monitoring

27. Following the blogs
Be yourself!
Don’t blindly follow trends
Agile
DevOps
Languages
Dogs in the
Office
Tools
Standing
Desks

28. Thanks