Hi Ana-Maria, tell us who you are and what lead you into microservices?<\/b><\/p>\n
I am a custom application development enthusiast and an adopter of challenging development scenarios. I am also a lifelong learner, interested in architecture, new technologies\/languages\/frameworks and how to combine those in order to fulfil different context needs. Hence my interest in microservices. My belief is that microservices provide flexibility to use different languages\/frameworks, while fostering a culture of automation and cross-team collaboration. Business domain modelling of microservices contributes towards a <\/span>shared nothing<\/span><\/i> architecture and independently deploying each component. The ability to deploy one service without affecting any other service paves the way to Continuous Delivery. In fast-changing environments is extremely useful to benefit from deployment pipelines that rigorously test code and automate tasks (machine provisioning, deployment etc).\u00a0<\/span><\/p>\n \u00a0<\/span><\/p>\n What will you be talking about at Voxxed Days Microservices?\u00a0<\/b><\/p>\n I will speak about how to employ Helm (the package manager for Kubernetes) in order to speed up the ways of working with Kubernetes. Kubernetes seems very complex from a developer\u2019s perspective because it requires expertise on how to combine inputs for various configurations together with the applications rollout from Kubernetes manifests. In my opinion, Helm simplifies this through its charts hierarchy, allowing developers to make changes on their application and Kubernetes configuration by using a consistent interface.<\/span><\/p>\n <\/p>\n So we have Docker, Kubernetes and now Helm. Each one is targeted to simplify the developers and ops lives. With all these tools, are we really simplifying the deployment of our applications (simple and complex ones) ? Anything after Helm ?<\/b><\/p>\n These are tools that best serve us at this moment in certain contexts and as professionals we uncover new needs daily. In my opinion, tools contribute to \u201chow\u201d that architecture can be done, yet understanding the context comes first. Thinking of my own experience, whenever someone mentions \u201cmanually do X\u201d I think at which tools can be programmed to replace that effort. Since us as humans find something to improve about ourselves, for sure the software created nowadays can benefit from the same; the key is to write it in such a manner that can be evolved incrementally.<\/span><\/p>\n <\/p>\n Good, see you soon then\u00a0<\/b><\/p>\n I was delightfully surprised to receive the acceptance at Voxxed Days Microservices! I would like to thank you for giving me the opportunity to interact with your lovely community and experts around the world!<\/span><\/p>\n \u00a0<\/span><\/p>\n #Kubernetes #PackageManagement #BestPractices\u00a0<\/span><\/p>\n <\/p>\n My contact information<\/b><\/p>\n Twitter: <\/span>@ammbra1508<\/span><\/p>\n <\/p>\n","protected":false},"excerpt":{"rendered":" Hi Ana-Maria, tell us who you are and what lead you into microservices? I am a custom application development enthusiast and an adopter of challenging development scenarios. I am also a lifelong learner, interested in architecture, new technologies\/languages\/frameworks and how to combine those in order to fulfil different context needs. Hence my interest in microservices. […]<\/p>\n","protected":false},"author":1301,"featured_media":2083,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[],"acf":[],"yoast_head":"\n