Mark Heckler never disappoints; delivery is always on point
@MarkHeckler Жыл бұрын
Very kind of you, thank you!
@MohamedDernoun Жыл бұрын
One of the best presentation 👌
@MarkHeckler Жыл бұрын
Thank you, glad you liked it!
@konstln5503 Жыл бұрын
I don’t understand why we need configserver inside k8s if we have native configmaps. This server one more single point of failure. Plus I don’t understand why we still need discovery server if k8s provides native discovery solution. If this video was about how to build applications that use only docker without k8s then maybe… but for k8s should be use different approach
@MarkHeckler Жыл бұрын
I'm not sure why my previous reply was removed by YT, but I'll give it another go. You don't! That's a great question that I address in the session: Config server incorporates many different ways to manage/process/serve up properties to client apps, including K8s configmaps. Config server incorporates many other capabilities (including encryption/decryption of stored props as mentioned, and more - check out the docs!) and is a useful abstraction mechanism. There were several different options you can employ in this type of microservice portfolio, and I stuck to a single "path through the forest" as one example, largely due to time and for clarity. Hope this helps!
@MarkHeckler Жыл бұрын
Re: the glitch in the matrix 😄, I'll check back here periodically and restore this response to ensure it's available for reading so everyone understands they have options. The goal with most sessions aren't to show the "one true way", but to show *a* way, either current best practice(s), recommendations for success, and/or representative examples that clearly communicate the desired/required concepts. Best to you!