It was just after midnight when I walked into the offices of the Prometheus Engineering Company, which is based in Palo Alto, California.
It was my first day at the company, a few months after I’d moved to London and the London-based startup had launched.
Prometheus is a cloud computing company that focuses on building tools for the world’s leading internet-of-things developers.
It’s one of the biggest names in this new market, with a portfolio of projects ranging from autonomous cars to autonomous trucks.
Its latest projects, such as the Prometheus Engine, a software-defined networking (SDN) tool that lets users create networks of data centers that act as servers and switch between multiple applications and services, are used to build huge cloud-scale computing systems.
I’d been asked to join Prometheus for a couple of months, as a senior software engineer, to help develop its next-generation Prometheus Platform for Docker containers.
At the time, I’d joined the company on a limited contract, with my contract to work on the Prometheus Platform expiring in February 2019.
But I was looking forward to being able to take the time to get to know the engineers, and it was also about learning the new product.
I got in touch with Adam, who was the engineering director at the time.
He asked if I would be interested in working on the new Prometheus Engine and asked if there was anything I wanted to know about it.
I thought, Why not?
I was happy to learn about what Prometheus was doing in a new way and I was curious to see how it would evolve.
So I asked Adam what Prometheus Engine was and he said that it was a “software-defined network (SDNs) tool”, a reference to the open source software that powers Docker containers and the Docker Hub.
Prometheus was the first project Prometheus had launched that would allow developers to create SDNs, and I knew the company had been working on it for a while.
Prometheus has been developing the SDN technology since 2015, when it released Prometheus Engine as a standalone product.
At that time, Prometheus was building tools to help developers build SDNs on top of Docker containers to make them easier to use.
The first version of the tool, released in March 2016, was a little buggy and it wasn’t really ready for general use yet.
The company had built a Docker Engine to do some initial testing, but as Docker had been relatively new in the industry, it wasn and would be a slow process to get a working tool into production.
So in 2018, Prometheus started working on an SDN for its Prometheus Engine.
At this time, the company was building an open source version of its Engine, called Prometheus Enterprise.
I wasn’t sure if the tool would eventually be ready for production, so I asked Prometheus to make it available to other companies.
Prometheus also announced the Prometheus SDK, which was an SDK that allowed other developers to build and ship SDNs in their own projects.
In 2020, Prometheus released Prometheus 2.0.3.
The SDK had many features that made it a lot easier to write, debug, and deploy SDNs.
I was impressed with how it worked and I decided to give it a try.
I decided it would be interesting to build some of the tools I had developed in Prometheus and see how they would evolve over time.
I created a small Docker container and ran the Prometheus tool in it.
After a couple seconds of starting up the tool and doing some basic network setup, I was greeted with a very different experience.
The tool’s UI wasn’t as polished as the tools that had been released earlier, but I was able to use the tools as a starting point for building my own tools.
The Prometheus Engine is the engine that powers Prometheus Engine 1, which has since been released to developers as a Docker Compose container.
I could also run the Prometheus tools in the container, which allowed me to use Prometheus Engine to create, modify, and test my own SDN.
The new tools were not just an addition to Prometheus.
They were part of a much bigger set of tools that I had already developed in the past.
The tools I was building were based on existing tools that already existed.
I had been using the tools from the previous versions of Prometheus.
I used the Prometheus Engineer to write new Prometheus tools that would be able to do things that had never been done before, such a network monitoring tool that could monitor traffic on a specific IP address and report back what it detected.
I also used the tools to create a new network monitoring software, which could monitor a network and alert its users if something unusual happened.
The next day, I used my new tools to build an SDNA for a new project that I was working on.
The SDNA is an infrastructure tool that is used to create an autonomous network that serves as a gateway between various services and applications.
The project is called “The Prometheus Engine”, and it has been developed to be used as an application in the Amazon AWS cloud