engineering VS Lean and Mean Docker containers

Slim.AI | Fullstack and Backend Engineers | REMOTE, international or Seattle/Bellevue/WA | Full-time | Golang, Node.js, Vue.js/Nuxt.js

I'm the founder and CTO at Slim.AI. We are a well funded seed stage startup (9M+) in the developer tooling space. Our mission is to simplify and accelerate the containerized app delivery (it's too hard, too complicated and with too much manual work). We are about to transition to the next phase and we are expanding our engineering team.

Our engineering team is the innovation engine for our product because we are building a solution to solve our own problems creating and running containerized cloud-native applications.

We use Golang, Node.js Serverless/Lambda and containers. We have frontend, backend and fullstack roles ( https://github.com/slim-ai/engineering ).

Our engineering principles:

* We use what we build.

Slim.AI | Backend and Fullstack Engineers | REMOTE, international or Seattle/Bellevue/WA | Full-time | https://github.com/slim-ai/engineering

We are a well funded seed stage startup (9M+) in the developer tooling space on a mission to redefine how DevOps is done for containerized apps (it's too hard, too complicated and with too much manual work). We are about to transition to the next phase and we are expanding our engineering team.

Our engineering team is the innovation engine for our product because we are building a solution to solve our own problems creating and running containerized cloud-native applications.

We use Golang, Node.js Serverless/Lambda and containers. Take a look at the backend ( https://github.com/slim-ai/engineering/blob/master/roles/bac... ) and fullstack ( https://github.com/slim-ai/engineering/blob/master/roles/ful... ) roles and our engineering principles to see if the role and how we do engineering looks interesting to you ( https://github.com/slim-ai/engineering#engineering-principle... ).

Email me at [email protected] if you'd like to learn more.

P.S.

And take a look at DockerSlim ( https://github.com/docker-slim/docker-slim ) if you are interested in working on the open source project that powers our SaaS.

Slim.AI | REMOTE or Seattle | Full-time | Developer Experience Lead | https://github.com/slim-ai/engineering

Do you enjoy working with lots of different applications stacks? Do you like helping others? Do you want to build lots of different applications? Are you interested in contributing to open source?

We are a funded seed stage startup in the developer tooling and DevOps space empowering developers to build and run their cloud-native applications. The current product is focusing on containers and the friction around them.

We are building a brand new engineering team. We are developer friendly, low on process with no mind-numbing bureaucracy or micromanagement. We are looking for people who'll be excited to be a part of the engineering team in an early stage startup during its inception phase building modern cloud-native applications the right way.

You can find out more about the mission, how we work and the roles here: https://github.com/slim-ai/engineering

Email me at [email protected] if you'd like to learn more.

And if you want to make the container quickly secure without bloats, maybe give this a try https://github.com/slimtoolkit/slim

Slim.ai presents the data in a more user friendly way than many of the other tools in this post. On top of its open source SlimToolkit for identifying the contents of an image, Slim.ai uses Trivy for vulnerability scanning.

What about https://github.com/slimtoolkit/slim?

A last practice that I do not use at all and which may interest you is to use slim toolkit to keep only the useful elements in your final image.

Anyone tried using https://github.com/docker-slim/docker-slim To minify an image?..

Distroless images are better left for people with serious need for lightweight images and good Linux knowledge because they require lot of planning with the build so that they stay light and work. If you need lighter images but docker isn't your main tool and you can't afford to take hours and hours of practicing different build strategies you can check docker-slim (https://dockersl.im/). With this tool you can easily size down the images.

Maybe this would help in that regard: https://github.com/docker-slim/docker-slim