Datawire Blog

Datawire | Systems Engineer | Boston / Remote OK | Full-time | https://www.datawire.io We build open source tools for Kubernetes, including Ambassador (API Gateway built on Envoy Proxy) and Telepresence (CNCF Sandbox project for developers). We're looking for systems engineers who are comfortable coding and troubleshooting features at all areas of the systems and network stack. Do you know how to override DNS on Linux so that it points to the DNS in your Kubernetes cluster? Then this is a role for you. We code in C++, Golang, Kotlin, and Python. Past experience with Kubernetes, Envoy/NGINX/HAProxy, and/or open source projects a big plus. We love people who are (or want to be) members of the Kubernetes/cloud-native open source community, and virtually all of our engineers have given talks at conferences such as KubeCon, Velocity, ApacheCon, DevOpsDays, and such. Email [email protected].

Datawire | Systems Engineer | Boston / Remote OK | Full-time | https://www.datawire.io We build open source tools for Kubernetes, including Ambassador (API Gateway built on Envoy Proxy) and Telepresence (CNCF Sandbox project for developers). We're looking for systems engineers who are comfortable coding and troubleshooting features at all areas of the systems and network stack. Do you know how to override DNS on Linux so that it points to the DNS in your Kubernetes cluster? Then this is a role for you. We code in C++, Golang, Kotlin, and Python. Past experience with Kubernetes, Envoy/NGINX/HAProxy, and/or open source projects a big plus. We love people who are (or want to be) members of the Kubernetes/cloud-native open source community, and virtually all of our engineers have given talks at conferences such as KubeCon, Velocity, ApacheCon, DevOpsDays, and such. Email [email protected].

Datawire | Boston, MA | Full time | Onsite | Tech lead Interested in open source? Microservices? Cloud-native culture? Datawire is building OSS software for Kubernetes, including Ambassador and Telepresence. We're looking for a tech lead who can lead our commercial products team that builds on our open source stack. Our core stack is Golang, Python, Envoy Proxy, and Kubernetes. Learn more: https://www.datawire.io/ Please email [email protected].

Kotlin is great and we're using at in the backend at Datawire.io. Also we're hiring! Check us out if you're a backend JVM/Kotlin developer and are in the Boston, MA area! https://www.datawire.io/careers/

I wrote a comparison of Draft and another local development tool for Kubernetes that I'm working on, Telepresence: https://www.datawire.io/draft-telepresence-two-new-tools-local-develop…

Correct link: https://www.datawire.io/slides-an-illustrated-guide-to-microservices/

Datawire.io | Boston, SF, NY, Remote | Bad-A$$ Engineers, Microservices Datawire.io is on unstoppable mission to help development organizations scale through microservices. Our team is innovative, intellectually curious, and dedicated to building infrastructure and tools to empower developers and engineering organizations to scale faster than ever. We're building on state-of-the-art infrastructure such as Kafka, Spinnaker, and Docker AND working to enhance these technologies, making them more accessible. We're hiring in Boston, San Francisco, New York & US remote for all positions listed: https://www.datawire.io/careers/ Salary: $85-160K (ie, based on you)

yea, python really feels like an afterthought since it expects json strings [1] and doesn't support python3 [2]. [1] https://www.datawire.io/3-reasons-aws-lambda-not-ready-prime-time/ [2] http://docs.aws.amazon.com/lambda/latest/dg/current-supported-versions…

Cutting your project up and putting the pieces on different hosts and calling them microservices doesn't make it true. Some links that wil hopefully be helpful: - http://www.infoq.com/presentations/scale-gilt - https://www.datawire.io/microservices-stories/ - http://shop.oreilly.com/product/0636920033158.do

Before this article, I've always thought Spotify was an electron app (or something of the sort), so never bothered installing it. I was wondering why you didn't just open a Dev console and inject some JS :). Regarding the Apple code signing requirement: is it the case then for all hooks of this sort that one is effectively required to be in the Developer program? So I was curious if LD_PRELOAD is prevented from working, but seems there's a simple work around: > On macOS there is an additional problem. Newer versions of macOS have a security subsystem called System Integrity Protection. For our purposes the problem is that it prevents injecting code via DYLD_INSERT_LIBRARIES (the macOS equivalent of LD_PRELOAD) into any binary in /bin, /sbin, /usr/bin and /usr/sbin. > Luckily, there’s an easy workaround. Just create a new directory, copy all the binaries from /bin, /sbin, /usr/bin and /usr/sbin into that directory, and then add it to the start of your $PATH environment variable. Once the binaries are out of those special directories code injection works just fine, and since they’re only 100MB copying them is quite fast. From https://www.datawire.io/code-injection-on-linux-and-macos/

I've worked with API Blueprint as it seems to have the widest support across API tooling providers, along with a sane syntax. It's really nice to be able to spec out a blueprint and then simulate an API [1]. Also being able to run tests on the real API, but based on the API docs which describe expected behavior, has exposed many bugs [2]. I just recently watched the "Microservices Summit" from microservices.com/Datawire [3], and the most-repeated lesson from Netflix, Amazon, and Yelp was to design API-first, not data-first. As engineers we tend to design an API around our data -- but developers have to interact primarily with the API, and then with the data. With API spec tools we can quickly fake an API and try to interact with it, then find out what sucks and rewrite it, all before sinking time into the actual implementation. SendGrid does this, and their API has been a breeze to work with [4]. The last step is to use a client SDK generator like Apimatic [5] -- but that only works if the API actually conforms to the docs. It's probably difficult to get an entrenched codebase to switch to spec, but for any new API I wouldn't do it any other way. [1]: https://github.com/localmed/api-mock or https://apiary.io [2]: https://github.com/apiaryio/dredd [3]: https://www.datawire.io/microservices-practitioner-summit-wrap-up-2/ [4]: https://sendgrid.com/blog/quickly-prototype-apis-apiary/ [5]: https://apimatic.io