We think first mile data hasn’t gotten the attention it deserves. So much emphasis is placed on centralizing internal data that organizations haven’t had a place to track first mile data. Enter Datasets.
We’ve built a system of record specific to first mile data. However, such a system has multiple stakeholders across an organization. One set of stakeholders are the frontline teams, the people who use Osmos. The other set of stakeholders are people on the engineering side who need to receive the clean data for use.
As part of our work to bridge the gap between operations and engineering teams, we are proud to announce the launch of our Osmos API.
So far, we’ve enabled this through the use of Connectors. While this is a low friction approach, it often leaves operations teams unable to revisit that data in the future. Plus it leaves teams with no concept of how the data has changed or what’s different. The Osmos API allows engineers to access the high-fidelity, cleaned data in Osmos, so Datasets can function as a single-source of truth across teams.
Before Osmos, incoming data would go through a chain of 5-6 systems which each did their own transformations without a single transformation log. Different people on the team would see different snapshots with different degrees of staleness. Each of the teams that maintained those systems had to provide a way for other teams to access that data and to explain how the data is set up and how it can be queried.
Teams depended on the inner workings of each other’s databases schemas making everything more complicated and brittle. So when something breaks or someone goes looking for answers, it becomes a huge, expensive data and systems archaeology project.
One version of the truth to ensure data quality
Datasets, in tandem with the new Osmos API, enables frontline teams to bring in customer data while engineering teams can programmatically access all the details of every record, every cell in the system to ensure this data is usable.
For Datasets to truly be a single source of truth, teams are now able to track the history of the data and its transformations. All stakeholders can now see the who, what, where, when, why, and how to ensure data quality.
Built with dev teams in mind
Our all new Osmos API not only provides simple request-response semantics to read and write data, but it also provides rich data history, lineage, and auditability.
We carefully designed the Osmos API to be truly REST-ful, and it comes with a full OpenAPI (Swagger) specification. The specification can be found here and documentation can be found here. The Osmos API documentation is served at the same subdomain as the actual endpoints which enables us to provide deployment-versioned APIs for our multi-region and private tenant customers.
This work grants devs the ability to generate clients, SDKs, and CLIs in any language of their choosing and interact with the system while maintaining data tenancy guarantees. The Osmos API also makes it easy to connect other no-code tools directly to Osmos to automate the other non-data parts of your operations.
The world's most innovative companies use Osmos
Contact us to learn how you can break down data silos and bridge the gap between devs and frontline teams with Osmos.
Should You Build or Buy a Data Importer?
But before you jump headfirst into building your own solution make sure you consider these eleven often overlooked and underestimated variables.
view the GUIDE
%201.svg)