Taking a new position at a company can be an overwhelming proposition. The insight gained (on both sides) during the interview process suddenly faces the reality of the day-to-day requirements of building a company.
I have had the opportunity, in the embarrassingly long time I’ve been employed, to interview with a wide variety of companies following an even wider variety of interview processes. In all that time, there are few organizations that have impressed me to the extent that Macrometa has (and continues to).
I am humbled, and excited, to join with the responsibility of looking after how we talk about ourselves, the stories we tell, to whom we tell them, and the tools we use to tell these stories. Or, put differently, I am joining as the VP of Marketing.
But why Macrometa?
Of all the opportunities that existed for me, what was it about Macrometa that drew my attention and generated so much excitement?
Simply...the tech and the team.
If you are interested in exploring Macrometa (the tech) without reading my diatribe, you can get started in minutes with a free dev account on Macrometa.com
Each interaction with a company begins with reading how they describe themselves.
Macrometa provides enterprise developers with a secure, global data cloud for building & running real-time, distributed, multi cloud & edge apps/APIs
A compelling bit of boilerplate that, as I dug deeper (and in my still very new relationship with the company and the technology), I summarize as:
The power of a multi-model database with the utility of a CDN.
Or, perhaps, less simply:
Macrometa brings new infrastructure to the cloud wherever people are. Build what you want in a more stateful, distributed, global way than you could before. Macrometa gets your application to within 50-75ms from the majority of humans with an internet-connected device.
The modern developer faces an entirely new set of challenges. As an industry, we have tried to adapt to this with a variety of architectures and tooling. And, yet, when I spin up an application on most cloud providers I am immediately faced with the question: What region do I want to run this application in?
The answer is, of course, all of them.
- The increasing globalization of applications.
- The increasing politicization of data.
- The increasing latency sensitivities of users.
All are problematic when faced with the physical reality of the speed of light as a constant.
Imagine building a database designed to serve users stateful responses anywhere in the world. While also providing engineers the primitives with which they are comfortable (document, K/V pairs, graphs, timeseries, geospatial) and overlaying that with global deployment (150+ edge PoPs) with a p90 of 50ms and a p99 of 75ms alongside functions, containers, streams, and an edge cache.
And, of course, the ability to serve, mutate, and provide stateful operations with consistency guarantees and change replication (CRDTs do, indeed, have commercial usage) is impressive.
You can imagine my excitement.
There is a wealth of interesting information on the blog (articles like Motivating CRDTs) and in a paper entitled CDB: Geo-Replicated, Conflict-Free Document Database with Session Guarantees. And, of course, the documentation is a thing of beauty (and constantly improving).
While I could go on, the easiest way to discover the applicability to you is to try it out. State management at the edge for the win.
I have been very fortunate in my career. I’ve seen success. I’ve seen failure. I’ve seen steady-state companies serving user needs somewhat quietly.
In my time at a variety of companies, I’ve learned that I value telling stories about the software other people build. Similarly, I’ve learned that who you choose to tell the stories with dramatically affects the story-telling and impacts the company’s opportunities.
As a globally distributed team – appropriate for building a globally distributed data network – Macrometa combines the best of asynchronous work and synchronous collaboration. It is an ambitious team…but a startlingly transparent and honest one at the same time.
How we choose to grow, both our team and our culture, matters as much as what we choose to build. I believe in the vision of the founding team. I believe in the capability of the leadership team. And, importantly, I believe in the whole team's emotional maturity to face both success and difficulty with the right balance of motivation and care for each other.
Do you see yourself in what we’re doing? We are growing and building software is all about hiring great humans.