Ashutosh Mishra ashutosh-mishra

So, You Want to be a Systems Engineer

Systems Engineering (also known as Infrastructure Engineering, Operations Engineering, or DevOps) is a challenging but rewarding career path. Because Systems Engineering draws from a wide variety of smaller topics, it can be hard to know where to start and in what order to begin. This resource is intended to give you a sketch of some of the learning-paths that that can lead you to a career in Systems Engineering.

What do I need to know?

To start, let's examine a high-level list of topics that established systems engineers should have knowledge of. In each of these topics, the level of depth required to get started as a systems engineer may vary, but it's good to have a general breadth of knowledge on all of these topics.

These lists are not exhaustive, rather a good starting point to gain general knowledge.

(Q.1) What is Apache Kafka?

Apache Kafka is a publish-subscribe open source message broker application. This messaging application was coded in “Scala”. Basically, this project was started by the Apache software. Kafka’s design pattern is mainly based on the transactional logs design. For detailed understanding of Kafka, go through,
Kafka Tutorial.

(Q.2) Enlist the several components in Kafka.

The most important elements of Kafka are:

Topic – Kafka Topic is the bunch or a collection of messages.
Producer – In Kafka, Producers issue communications as well as publishes messages to a Kafka topic.
Consumer – Kafka Consumers subscribes to a topic(s) and also reads and processes messages from the topic(s).

How To Work With Multiple Github Accounts on a single Machine

Let suppose I have two github accounts, https://github.com/rahul-office and https://github.com/rahul-personal. Now i want to setup my mac to easily talk to both the github accounts.

NOTE: This logic can be extended to more than two accounts also. :)

The setup can be done in 5 easy steps:

Steps:

Step 1 : Create SSH keys for all accounts
Step 2 : Add SSH keys to SSH Agent

	buf, bodyErr := ioutil.ReadAll(r.Body)
	if bodyErr != nil {
	log.Print("bodyErr ", bodyErr.Error())
	http.Error(w, bodyErr.Error(), http.StatusInternalServerError)
	return
	}

	rdr1 := ioutil.NopCloser(bytes.NewBuffer(buf))
	rdr2 := ioutil.NopCloser(bytes.NewBuffer(buf))
	log.Printf("BODY: %q", rdr1)