As of this writing, Mixmax runs 15 Node microservices. We keep this manageable by sharing a ton of code between services, in the form of npm packages both public and private.
To keep those packages manageable, we develop them in their own repositories. But this poses a challenge for local development—how do we quickly test a new version of a package inside another?
At Mixmax, our engineering team strives for a bottoms-up culture of product ownership. This means that anyone on the team, not just the founders or our product leads, can contribute their great ideas! We believe that all of us is smarter than some of us. ;)
Deploying VPNs that effortlessly scale and self-heal is painful. Here's how we do it in a cost-effective and simply manner.
Mixmax is essential to our customers’ workflows. Because of this, when we deploy new features to production, we want to avoid introducing any regressions that might disrupt our customers’ work.
Surveys suggest that as many as 3 in 10 workers in the United States work remotely at least some of the time. In fact, the New York Times suggests that remote work is gaining prevalence faster than any other workplace benefit. Here are some tips from my experience living and working from Japan.
The Mixmax Insights dashboard is like Google Analytics for your mailbox. How many messages did I send? How many were opened? How many received replies? How do I compare to the rest of my team?
Imagine you want to learn more about database performance and you have in your hands a very large book about databases in general. How would you search for your topic of interest? More often than not, the answer will be go to the index of the book which is located at the back, look up the topic and it will say the page where said topic is discussed; well, the way databases find data is not all that different.
search-string is a new open source minimalist npm package for parsing and managing GMail style advanced search strings.
How we prevented bots from clicking meeting links in your Mixmax emails.
Mixmax is built on Gmail. Our product, and its convenience and power, depends on tight user-interface integration with Gmail. In order to add features to Gmail for our users, we need to track the structure of Gmail’s [DOM] and be able to manipulate it. For years, we achieved this by crafting query selectors to identify important elements within Gmail’s DOM, and continuously re-applying these selectors as the page changed.
Process high-volume in jobs in manageable batches with existing infrastructure.
Ever been frustrated when someone decided to play around in the AWS UI? Does managing infrastructure through UI strike fear into your heart?