The Cloud Native Patterns (CNP) you share in your book could be taken as cloud agnostic or these patterns should be taken per platform basis?
Do you provide advice on which cloud platforms support each CNP or all of them are tied to a specific platform?
In the last case, I would guess Cloud Foundry
The patterns are very intentionally agnostic of any particular platform. In fact, I go over the patterns whether the developer is responsible for implementing them or should be looking to a platform to find an implementation thereof. It's super important for the developer to understand the patterns whether they have to implement them or not, because an understanding is critical to know how they should be leveraged.
Chapter 3 is all about platforms though, and how they provide a huge leg up on realizing some of the patterns I teach. But because the book is not about platforms in particular, I do not have any type of a formal listing showing what platforms provide implementation of what patterns.
All of that said, I do have my readers deploy to a platform and while it's a good guess that I would do Cloud Foundry, and initially I planned to do that, you'll see that I use Kubernetes. :-)
Thanks for the great question - you honed right in on one of the points I really hope my readers will get.
Author of Cloud Native Patterns
posted 5 days ago
Thank you Cornelia,
In several comments and articles they say that it's better to pursue the agnosticism while designing an application. Even when sometimes we will require to use some specific features of the platform though.
So I guess the idea of having the patterns to be agnostic to any platform is a good starting.
But what do you think, it's better try to make the application "agnostic" or do it native from the beginning?