WEEK 2: POST 2

 Today at my internship, I had a whole session about Kubernetes and a brief introduction to some Go programming language code files that my team has built. Kubernetes is basically a container orchestration tool, which is open-source as well. My prior knowledge was that it is only used for hosting containerized applications; however, I was made to realize that it is also used to automate the deployment and management of native cloud applications. I needed to know the basic architecture and set my environment through a Kubernetes host because I will be needing it to deploy my containerized application once my project gets done.  For Go programing, I am expected to use it mainly for developing my project.


Although my buddy explained the architecture of Kubernetes within the firm’s structure, I must confess that I did not grasp the concept of Kubernetes after his explanation. Perhaps, I should have had read about it in detail prior to meeting him today. I failed to dive deeper into the concepts and architecture of the Kubernetes tools because I presumed that I would not have needed to know those concepts. I only thought that all the configurations and the dirty work would be done for me, while I concentrate on building my project with Go programming. Thus, after the Kubernetes session, I spent an hour reading the IBM documentation and video about Kubernetes and it made more sense to me now. The video especially was very helpful.Thus, in the future, I will try to dive deeper into concepts and ideas of a certain topic before scheduling a meeting with him. 


Besides, I looked into the Go programming code base that I was provided as a starter to have a broad overview of how the Go language is used in building large applications. It is not much of a difference from the code lines I practice on the Go online IDEA. I was just learning the Go syntax and data types prior to today and being able to understand some lines of code just by a glance was a great feeling. But, unlike how I used to run the Go code on an online IDE, I didn’t know that Go language needs a whole dependencies file that needs to be implemented before the application is run. Also, I learned that to use Go many functions and features, one needs to name certain packages and import them. So too, Go import statements are very different from Python. This was a new and very distant idea to grasp at first. I must say that with what I have seen on the code lines given to me, I still need to learn more Go programming concepts, especially data types, Goroutines, and loops. Therefore, I will spend the next two days learning these concepts at my internship so that by next week, I will start coding my project.


Comments

Post a Comment

Popular posts from this blog

WEEK 4: ENTRY 3

  Today at my internship, I was assigned the issue of troubleshooting why my GET request Golang code is unable to generate the data from my http server. Since it was a combination of k8s deployment and Golang go, it was trickier and harder than I envisioned. The k8s was mainly used to orchestrate the objects that are needed to generate keytab from my pods. After several debugging: comparing and contrast the referred file I used as a source code coupled with looking up the errors on Stack flow (suggested me to delete my deployment and redeployed), I was still unable to fix the issue. Partly was because I did not understand what the error message was pointing at. Thus, I had to consult a member of the k8s team, who figured out that my deployment.yaml file was missing some configurations that needed to generate my key-tab. Simply, I needed the key-tab in order to be able to make the HTTP Get Request get my desired data.   Although the recommended solution from my consultation wor...
Read more

WEEK 6: ENTRY 3

  At my internship today, I continued unmarshalling the Json data I got back from Big Query API. Having tried replicating the data on the Go playground and using the Go unmarshall function yesterday, I did develop a better understanding of the json structure. I used Go’s struct to do the unmarshalling. Unlike the json data I got from my query, the documentation’s json data does not have any schema metadata and so I thought the same approach would not work. Little did I know that the schema data can be ignored when unmarshalling json data and that you can only concentrate on the part of the Json you want to unmarshall. When I consulted my buddy, he hopped on a zoom call with me and we did pair programming. I was the driver while he was the navigator, basically explaining what we were doing because he has more knowledge on Go and Json data manipulation. Working with him gave me more skills and confidence in what I was doing. He helped in not just using the Go struct, but also in tryi...
Read more

WEEK 7: ENTRY 1

  It sometimes feels like we are not good enough when our tries don’t work. Well at my internship today, I worked on resolving the json unmarshalling issue I was stuck with last Friday. After several back-and-forth consultations with my buddy and manager, I finally got a better understanding of how they wanted me to present the data. Basically, the data should be in a simple json array that could be manipulated easier. This is because as the json comes in key:pair format, I would need to extract all the keys and use those keys to send an HTTPS request to Elasticsearch Rest API.  Even though the approach was well defined and clear to me, I still struggled to implement it using the Golang Struct and Maps. One of the obstacles I had was because after unmarshalling the json data, the output was in a Golang interface type, which was not iterable like say a slice. A Golang slice is the equivalent  of a python array. Therefore, to overcome that barrier, I created an empty slice ...
Read more