Shift6

At Redox, we're taking a pragmatic approach to building microservices, especially in how we handle cross-cutting concerns. Most refer to this part of a microservice ecosystem as the chassis—things that every microservice needs to have in order for us to be confident that it's a quality product. The chassis includes:

For the first part in this series, see part one.

Before designing a single service or writing a single line of code for microservices, it’s important to be clear on the problems you’re trying to solve, and the end state for which you’re shooting. At Redox, this end state took the form of a list of principles that we want to adhere to as we create our microservice environment.

What is Lambda and why you should care

AWS Lambda is the standard bearer of a new paradigm in cloud computing generally referred to as "serverless". Before serverless, developers needed to provision servers in the cloud. They needed things like patches, health checks, monitoring software, and all of that takes a toll on the people responsible for keeping them running.

Tech teams move to microservices for many reasons. The flexibility that microservices afford hits on a lot of the “keys to success” agreed to in the industry:

Character encoding is one of the most arcane subjects a technologist will ever encounter, yet it underpins literally every piece of text we see on our computers. This article will focus on HL7v2 and the Redox API, and how they treat different encodings.

In the beginning of September, Redox participated in FHIR Connectathon 16  in San Diego. It was a lot of fun and a very worthwhile experience—we learned a lot, built some awesome prototypes, and met lots of great people.

At Redox, we use AWS for all our infrastructure needs, and logging into the AWS console often reminds me of walking into a toy store as a kid—there are so many cool things to play with. Unfortunately, not all services make sense for Redox. It’s unclear to me, for example, how we might leverage Alexa, although Redox has a lot of visionaries, so I can’t promise that we won’t use it one day.

Redox is live with an actual FHIR integration. I'm pretty sure I predicted it would happen in 2017, but sadly I didn't blog about it. In the spirit of being a prognosticator, I'm going to predict what I think the future of FHIR will look like.

In this post, I'm going to share how I set up a Node.js server behind an AWS load balancer that can receive client certificates.

Welcome to our monthly product update. At Redox, our number one goal is to provide a solution to all of your integration needs, not just one or two of them. That's why even though we've built a modern API for data exchange, our team is constantly improving our product and rolling out new features for you to use. You'll find our most recent updates below, along with highlights on a few of the problems we're currently working to solve.

If anything piques your interest, or if you have any feedback, we are always listening on Slack.