itayB

#include <iostream>

#define MAX_SIZE 1000
#define SHIFT MAX_SIZE/2

using namespace std;

bool check(int dx, int dy, int round, bool board[][MAX_SIZE]) {
	cout << "dx="<< dx << ",dy=" << dy << " [" << (dx*round) << "," << (dy*round) << "]" << endl;
	return board[SHIFT + dx*round][SHIFT + dy*round];

itayB

#include <iostream>
#include <map>
#include <vector>
#include <algorithm>
#include <string>

#define MAX_A 10

using namespace std;

itayB

#include <iostream>

using namespace std;

#define MAX_A 10
#define MAX_B 4

void sortedMerge(int a[], int b[]) {
	int pA = MAX_A - MAX_B - 1;
	int pB = MAX_B - 1;

itayB

#include <string>
#include <set>
#include <iostream>
#include <algorithm>
#include <vector>
#include <sstream>

using namespace std;

void split(const string &s, char delim, vector<string> &elems) {

itayB

// This solution use another char array (which mean space complexity of O(n) where n in the length of the string)

#include <string>
#include <set>
#include <iostream>

using namespace std;

class Dictionary {

itayB

#include <string>

void swap(char* a, char* b) {
		char temp = *a;
		*a = *b;
		*b = temp;
}

void reverse_chars(char* str, int start, int end) {
	// TODO: add nullptr validation

itayB

#include <stdio.h>

class A
{
public:
	A() { printf("A\n"); }
	~A() { printf("~A\n"); }
	void p1() { printf("p1A\n"); }
	virtual void p2() { printf("p2A\n"); }
};

itayB

#include <stdio.h>
#include <iostream>

using namespace std;

/* Get string with number at the beginning of it and returns the number value. for example: "120ab" --> 120 */
int getNumber(char* str) {
	int i = 0;
	int size = strlen(str);
	int value = 0;

itayB

Written by Itay Bittan.

Apache Kafka

Background / Motivation

Our primary product contains a lot of modules (separate processes) talking together. At the beginning we wrote our own IMP (internal message protocol) written in C. It allowed us to send buffers (C structures) between modules over TCP connection. In addition, we developed a communication module - process that responsible to pass messages between all of the system modules. Here are some of the pitfalls we suffered from:

1. Limited queue size - working with TCP sockets queues we find out that we where limited to relatively small size. If you want see your buffer size in terminal, you can take a look at: /proc/sys/net/ipv4/tcp_rmem (for read)

itayB

Written by Itay Bittan.

Google Protocol Buffer

Background / Motivation

Most of our code project was written in C. Here are some of the pitfalls we suffered from:

1. While working with separated modules/sub-projects for each component of the system, we had to maintain some shared place for most of the struct's definitions - so moving data from one module to another could be achieved (for example, via TCP sockets). It turned out that it is not a simple task and lead to a lot of dependencies between sub-projects, redundants headers files includes and sometimes even struct duplications.

2. For persistency, some C structs were written into binary files (for example, query metadata). During the project lifecycle, these structs were changed (increased by more fields most of the time). Trying to read data from the old binaries files (which suitable to the old structs) cause malformed incorrect data and sometimes even caused to segmentation faults and system crash.