4 ms·
Our main product is essential a CRUD desktop application assisted by a lot of background services, mainly various integrations. We're in the process of charting
by magicalhippo 5y ago
Our main product is essential a CRUD desktop application assisted by a lot of background services, mainly various integrations. We're in the process of charting out a path to a cloud-based offering, driven by customer requests.
We're operating in a niche so we'll never have millions of concurrent users. We have ~1000 customers, and number of users per customer follows a power law. Our largest customer by far currently has a ~100GB database and ~100 concurrent users.
Since we're relatively small (currently ~25 employees) we don't have the resources to "constantly" be changing our stack, and so I fear vendor lock-in.
At least Kubernetes seems to be something that'll be around for a while, and it's available from several cloud providers. So while it seems overkill it would appear it has that going for it. However the complexity does scare me a bit. It's a giant leap from our current "dumb" setup of a database and core service on a plain server.
Reading recommendations or helpful suggestions would be appreciated. Are there better options out there for small fish like us?
- eof 5y agoI’d say you don’t need k8s. You just need a good terraform module to set things up for quickly on multiple providers. K8s is worth all the work cus then you can scale magically. You don’t need to scale magically. You just need to be able to easily deploy. In fact if you think scale will never be an issue you could just run it on hardware, seems like everything would easily fit in a single server.
- p_l 5y agoAnd with terraform, you're going to be writing pretty much from scratch with every provider out there, as outside of very basics of infrastructure the offerings differ wildly, and even if all you need is a VM with dumb load balancer you have to write ~5x$CLOUD_PROVIDERS resources and abstract it around. Personally k8s is least interesting in scaling, because you could easily scale with other options if you had money to burn
- jeltz 5y agoThe same is true for Kubernetes too from my experience. Only the very basics of it works cross provider.
- p_l 5y agoThing is, nothing in Terraform works cross-provider - it's just a (often clunky, though it got better) DSL over JSON which makes for nicer way to call vendor APIs. But I need to know all the details of those APIs anyway. With K8s, the basics that "just work" are pretty wide, the bits that are specific to vendor that are necessary are usually small and contained, and for everything else I have extensible API that allows abstractions like crossplane.io
- eof 5y agoecosystem is changing rapidly. i actually couldn't say if this is true as I have not played with any of the hosted k8s environments outside of highly complex real world usage. it does seem completely plausible that within the last year or so hosted environments are stable enough and standardized enough that k8s can be a target directly even for small projects. cool. i will try for my next one
- p_l 5y agoThe state I described above was somewhat solid by early 2017. Biggest possible issues were if you wanted to pass things like cloud credentials to your apps etc., but standard k8s resources worked pretty well with at most some extra annotations to for example link a Service of type LoadBalancer with specific pre-allocated IP.
- magicalhippo 5y ago> You just need a good terraform module Thank you, I've looked into Terraform before, but had half-way forgotten it. Thanks for the reminder, will have to check out again. > seems like everything would easily fit in a single server We probably need a few. Our client application and integrations do quite a lot of crunching at times. The largest client mentioned has a 16-core server with 64GB RAM for DB and integrations alone, and that is not over-provisioned by any means. They have two or three Citrix servers for the client in addition. Obviously things would be a bit different with something web-based, but more crunching would have to move to server-side due to DB latency. For smaller customers we do fit several of them on a single beefy server currently, and could very likely move forward with that.
- mirceal 5y agoare you going to run on multiple clouds or are you targeting just one cloud?
- magicalhippo 5y agoThat's the thing. We would probably be happy on one cloud, but I'm worried about not being able to move if the cloud-vendor conditions change. That's why I'd prefer to avoid getting to married to the solutions from a single cloud vendor.
- eof 5y agoif you stick with terraform; it is true that each implementation will be different for each provider. they will be similar for sure but each will be made individually. that said, that is a very very small task to change cloud providers and shouldn't deter you. also as you said, you can easily just start with one.
- mirceal 5y agochanging cloud providers is not a small task
- 5y ago
- p_l 5y agoPersonally, I'd stick to kubernetes - especially as you can even pack it into VM for on-site classic deployment - avoiding too much cloud-provider-specific bits, and optionally work on optimising away the time necessary to handle it. I assume that for whatever reasons going very close with one PaaS from any of the cloud vendors is out (I am not a fan of them, but that's specific to me being in Poland and not Silicon Valley, and I can't pay Silicon Valley prices) You have ~25 employees, so you need to reduce toil - you can't just throw a person full time to massage and understand each custom thing. 1) Take care to run your components <https://12factor.net/ https://12factor.net/> style. Even if you run them 'classic way' started from a shell script, it will make things easier to move around if necessary. 2) Don't use raw manifests - this gets tiring over time, and is prime example of "toil". Your time will be better served writing anything (whether fancy or not) that can manipulate some basic data structures and spit kubernetes resources in json format. Once you have that, you can template your resources easily and enforce common standards and behaviours. This helps a lot especially when you don't have many employees - I'm not advocating for "employees as cogs", but if you all your applications follow a standard scheme for labelling, where credentials and data is stored, etc. - each of those small improvements reduce a bit of toil - and critical to maintaining that is removing the toil of manually keeping those standards implemented. In one job I might have spent a week tailoring a templated deployment for an application, but the next person (who was dealing with the setup for the first time ever!) configured another, similar application in one day. It's a huge difference when all you need to start a new app is to fill in few blanks like names, maybe some credential, and maybe declare "ok, it needs a >25G temporary storage, and 5G persistent shared storage, plus should be available under this URL" and have the templates fill in the rest. 3) Implement some standards on observability and administration. It doesn't really matter whether you set up your own EFK stack/Grafana/Prometheus/Loki/Victoria Metrics/whatever or go with Datadog (ow, my wallet) or another vendor. K8s generally makes it (comparatively) easy to hook together. Apply templating and standardisation from (2) here. Whether you're a developer or sysadmin or both, having it "just happen automagically" leads to happier people, less burnout, and ultimately more productivity. 4) Abuse the hell of k8s flexibility to get multiple deployments going on. The more expensive the underlying gear is, the more important it is. If your whole deployment is parameterised, and with things like crossplane to integrate tasks like "allocate $VENDORs postgresql offering", you can quickly setup, test/poc/do something fun/do a dog&pony show/etc. then teardown an environment. Can you do it with more classical setup? Sure. Personally I found k8s both faster in wall clock time & development time for this... and definitely less expensive.
- mirceal 5y agoyou probably don’t need k8s. vms + lb + asg may go a long way for you. you can always make things more complicated but once you put k8s in you’re going to have to stick with it