Hello Aviad -
I read your article, https://medium.com/faun/dry-helm-charts-for-micro-services-db3a1d6ecb80, and thought it was very substantive. I am supporting a program that is developing system following a micro-services based architecture, containerizing code deliveries, using Kubernetes and Helm. I am very interested in using an umbrella chart to manage the system as a whole and had some questions. You indicate in your article, that the use of an umbrella chart allows developers to continue to deploy services independently if they would like to as well as enabling deployment and management of the system as a whole. Can you expand on this? How does this approach enable one to deploy services independently. Secondly, developers have asked how an umbrella chart deals with/accomodates the values.yaml files of each specific microservice. Do you have any insight into this? a good email for me is: david_snyde...@yahoo.com. Thank you! VR, Dave On Thursday, April 14, 2016 at 4:57:18 PM UTC-4, Aviad Moreshet wrote: > > Hello, > > I'm making a research on distributed systems and would like to gather some > information about App Engine's underlying implementations, especially in > the following topics: > > Architecture, Underlying processes, Communication, Synchronization, > Consistency and Replication, Fault Tolerance and Security of course. > > I've been googling for hours but all the info I found is about the > features the system offers instead of what I'm looking for. > > Any intel would be appreciated, so don't hesitate. > > Thanks for helpers! > -- You received this message because you are subscribed to the Google Groups "Google App Engine" group. To unsubscribe from this group and stop receiving emails from it, send an email to google-appengine+unsubscr...@googlegroups.com. To view this discussion on the web visit https://groups.google.com/d/msgid/google-appengine/0040e0bb-8998-44cf-baf9-bc66acd54550o%40googlegroups.com.
