okteto VS goseaweedfs

There are dedicated tools just for that. Apart from skaffold check also tilt.dev, garden.io, devspace.sh, okteto.com

Check also devspace.sh and okteto.com

You can consider using okteto for development environments, it lets you deploy your local code directly to k8s replacing the existing pods, our team uses it and it works pretty well with Golang.

Okteto is an application that allows you to develop inside a container, along with many features it permit the user to start a development environment and provide an automatic SSL Endpoints for k8s.

With Infrastructure as Code at its current state of maturity, it’s now easier than ever to replicate microservice environments in the cloud. This unlocked a new approach of having a personal production-like cloud environment for every developer, which they can use freely and in isolation. It comes in two flavors - persistent environments, or ephemeral environments created on demand with products like Okteto or Bunnyshell (also sometimes called Environment as a Service)1. This approach overcomes the resource limitations of the local environment but substitutes them for some new difficulties:

Remote development will be popular? Yes.

But developing in a monolithic machine may be not. The development environment should be clean and isolated, and products like gitpod and coder is promising.

Besides this, maybe you can have a look at https://github.com/tensorchord/envd and https://github.com/okteto/okteto

Okteto accelerates the development workflow of Kubernetes applications. You write your code locally and okteto detects the changes and instantly updates your Kubernetes applications.

Hey! Recently, I’ve been playing around with [Okteto](https://www.okteto.com/) to see how it helps with the local development of apps that will run in Kubernetes. It seems to be quite a good option for developers who don’t want to spend their time dealing with setting up and maintaining clusters. Moreover, you can use a development environment from Okteto without thinking about CI/CD pipelines for delivering the app.So, instead of working on your code locally and deploying it then to the cluster, the whole development process is shifted straight to K8s. That makes Okteto approach a bit different from what other projects, like Skaffold and werf, do. To implement this idea, they offer a [CLI tool](https://github.com/okteto/okteto) and their own cloud provided as both SaaS and self-hosted (it has a limited free option).Here is [my overview](https://blog.flant.com/okteto-cloud-for-local-development-in-kubernetes/) of Okteto; any feedback — especially, your own experience — is more than welcome.

There's a long long route to cloudification, but works like Okteto[1] seem like a nice early pass at doing what Docker-Compose was capable of for fast local development, but modern. Pursuing remote-development makes a lot of sense. There's already solid VSCode integration[2].

If you just need a terminal like thing to local-dev in, toolbx[3] is probably the first choice.

[1] https://github.com/okteto/okteto

[2] https://marketplace.visualstudio.com/items?itemName=okteto.r...

[3] https://containertoolbx.org/

Hi Jacob. I am one of the founders of Okteto (https://okteto.com/), a remote development platform for Compose and Kubernetes applications. We use Syncthing to sync code between the developer laptop and pods running in Kubernetes. I would love to know your thoughts on the strengths and weak points of Mutagen vs Syncthing for this use case.

You can check SeaweedFS https://github.com/chrislusf/seaweedfs

ChubaoFS - distributed file system and object storage Longhorn - Cloud-Native distributed block storage built on and for Kubernetes OpenEBS - Kubernetes native - hyperconverged block storage with multiple storage engines Rook - Storage Orchestration for Kubernetes SeaweedFS - Distributed file system supports read-write many volumes TiKV - Distributed transactional key-value database velero - Backup and migrate Kubernetes applications and their persistent volumes Vitess - Vitess is a database clustering system for horizontal scaling of MySQL kaDalu - A lightweight Persistent storage solution for Kubernetes / OpenShift using GlusterFS in background

seaweedfs - SeaweedFS is a simple and highly scalable distributed file system for small files.

Seaweedfs looks quite promising but its public url uuid is in the form of <32-bit volume, 64-bit file key, 32-bit file cookie>. The volume is probably fixed most of the time, the file key is an incrementing number while the file cookie is random. 32-bit seems too small to prevent guessing.

MinIO team care about an issue if you are paid customer, not for people who use the open source. Indeed MinIO is not even fully S3 compatible with many edge cases and close the issues related to it by saying it’s not a priority.

You might want to look at other options as well like SeaweedFS [0] a POSIX compliant S3 compatible distributed file system.

[0] https://github.com/chrislusf/seaweedfs

SeaweedFS is a fast, distributed storage system for blobs, objects, files and data that stores/serves billions of files. Can transparently integrate with the cloud with both fast local access and elastic cloud storage capacity. Blob store has O(1) disk seek, local and cloud tiering. Filer supports cross-cluster active-active replication, Kubernetes, POSIX, S3 API, encryption, Erasure Coding for warm storage, FUSE mount, Hadoop and WebDAV. chrislusf finds "it is much faster than the 'high performance' Minio."

welcome to help with https://github.com/chrislusf/seaweedfs

(I work on SeaweedFS) How about using SeaweedFS? https://github.com/chrislusf/seaweedfs

With your dedicated server, the latency is consistent, No API/network cost. Extra data can be tiered to S3.

Basically it is a key-file store.

https://github.com/chrislusf/seaweedfs/wiki/Filer-as-a-Key-L...

https://github.com/chrislusf/seaweedfs/wiki/Cloud-Tier

I am working on SeaweedFS. But seriously, use http://github.com/chrislusf/seaweedfs