Amazing, one more step towards breaking vendor lock in!
89 karma · joined October 1, 2015
Amazing, one more step towards breaking vendor lock in!
Also, I am really curious about the overall breakdown of coding time in high-level categories. Do you mind sharing your average percentages?
- Do you have a right to play? (do you have experience in the field that not many people do, etc)
- Are you passionate about the problem?
If you check all 3 then you're in a good position I would say.
I can't ever imagine using it tho :) If my bash scripts are so complex or critical that I feel the need to type check, I will probably use another scripting language where I can do that more easily while still having readable code.
A lot can be accomplished with simple virtual machines and some sort of auto scaling groups (depending on your cloud provider they have different names).
Kubernetes are amazing at unifying your workloads on any clouds though. If you care about portability, you should either consider using kubernetes for everything or using a tool that abstracts your configuration in a cloud-agnostic way. Although I'm a bit biased on this one.
I'm looking for organic answers rather than the BS that the top websites google sends me to, and often I can find it on reddit.
I would say that 30% of my search queries end with site:reddit.com.
Does this offer the same functionality as google cloud pubsub but using kafka instead?
I fail to see the right usecase right now, I have never seen the need to store more than a few hundred GB of data on a personal computer or to use a lot of computing resources.
Serverless web hosting with one click looks really cool though, but again, I can only see its usefulness in a few niche cases.
> What good is “change failure rate” if you can’t even jump-to-def across your code?
Exactly. Organizations often focus on the externally visible factors without considering the day-to-day of a developer productivity. If only we spent more time to refactor/maintain and general tooling instead of more status updates and unnecessary processes, imagine the productivity we could achieve..
At Google we had this simple problem yet it halted our entire team's productivity: IntelliJ started being insanely slow indexing files and auto completing stuff. It was a mixture of generated code and the monorepo that made it take tens of seconds for any kind of autocompletion. It's been there for years but there wasn't much priority to fix it, so things kept going (and probably still keep going) like this...
Our approach is to embrace cloud native services instead of avoiding them and still not be locked in to a single cloud provider.
We use cloud agnostic to convey that the user can write code that works for any cloud, and we'll translate it to the cloud specific services.
I'll think of different messages - thank you for the feedback!
We're focusing on a terraform provider for now but we want to also provide an SDK and a portal in the future.
Think about the difference in running your own database vs using a cloud managed one. With a managed service you don’t need to think about scaling, availability or replication. Cost is usually higher when you run it yourself as it might not be optimised.
The motivation was the realisation that, even when using Terraform, migrating infrastructure code requires an end-to-end re-write. Even though most core resources are the same in any major cloud, developers need to learn a new provider to deploy the same infrastructure when moving providers.
We are still in early days of development and currently support core services from AWS and Azure:
- Networking (virtual_network, subnet, route_table, security_group, network_interface, public_ip)
- Compute (virtual_machine, managed kubernetes)
- Database (managed MySQL databases)
- Vault (managed secrets)
- Storage (managed storage)
- Abstraction cloud differences (Azure VM public vs AWS EC2 private by default)
- Deployment through Terraform
We’re looking for feedback from developers about our approach and messaging. Let us know your thoughts!