How we want to help to solve the four core IT problems by introducing the NoOps platform

  1. Architectures became more and more distributed, so now we don’t build one application, but we have to build a bunch of micro applications talking to each other. It complicates infrastructure a lot, especially if these microservices were badly designed, with several ideas for configurations, runtime approaches, logging, security, monitoring, and even health checks. What is even worse, CQRS and Event Sourcing are popular now, which I personally consider to be fantastic design patterns, but from an infrastructure perspective, they add new types of components, combined with DDD made microservices even finer-grained.
  2. Everything is moving into the cloud. Unfortunately, people don’t understand the DevOps culture and who the DevOps Engineer is. Good cloud configuration should be treated as a software project, not as a bunch of scripts and configurations made in graphical wizards. There are still many people who think that the cloud is a regular Data Center and they treat the cloud as a group of virtual machines.
  3. Software Engineers are more and more expensive. What is even worse, from year to year they are becoming more narrowly specialized. It’s reasonable because the requirements are going to be more and more complicated. A different perspective shows, we want to expect our team members to feel responsible for the project, and of course, share their knowledge to make all processes as optimal as possible. This situation isn’t clear, sometimes we find people that are open to everything and will be happy to live in a DevOps culture. Sometimes it is completely opposite, we don’t have any real DevOps Engineer in our team. I wrote about it in a separate article https://cezaryolborski.medium.com/devops-engineer-do-you-know-who-you-want-to-hire-5e14b8707a57.
  4. We have Agile everywhere, which is a great direction itself, but there are many cases when it’s terribly implemented, especially in organizations where we have to face the collaboration between teams. The microservice architecture is very helpful but as I mentioned before, it complicates infrastructure.
Photo by Sebastian Herrmann on Unsplash
  1. The application should be built and run as a Docker image.
  2. It should send logs to the standard output.
  3. It should be fully configurable using environment variables.
  4. It should have a health check endpoint.
  5. It should implement one simple descriptor (box.yaml) defining what, where we want to run and what the dependencies are.
NoOps Platform
  • Distributed architectures
  • Complicated cloud configuration
  • Expensive Software Engineers
  • Agile methodology issues.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store