bcaxis

6 ms·

1.
by bcaxis 2y ago
Start by building a business that isn't differentiated by how many 9s you have. Something customers want so badly that a few hours of inconvenient downtime doesn't move the needle at all. In this situation, blowing up your system
2.
by bcaxis 2y ago
> I like the power that we see with cheap commodity hardware, but we mustn't forget that it's crap. Google grew up (early days) using cheap white box consumer PCs while "best practice" was expensive server boxes. It&#
3.
by bcaxis 2y ago
I think it's more an architecture question. If one box works, stop building on services that force horizontal thinking, and pricing, from the get go. You can solve one box availability with box 2 (hot backup) - all within the same arc
4.
by bcaxis 2y ago
> 2. Unidirectional end-to-end latency only applies to streaming data. Agreed that his "across the world" example is a bit silly. Because he doesn't take into account the connection construction. His primary point is still
5.
by bcaxis 2y ago
I do something similar with stripe. I add two items to the subscription. A base unit that charges a fixed price up front and monthly thereafter. And usage based second item that bills based on usage minus the pre charged items. Usage ba
6.
by bcaxis 2y ago
I do something similar with stripe. I add two items to the subscription. A base unit that charges a fixed price up front and monthly thereafter. And usage based second item that bills based on usage minus the pre charged items.
7.
by bcaxis 2y ago
New billing primitives. Cost per invocation on functions and edge requests where it used to included in GB/h and bandwidth. Cost per cache read and write instead of lumping it all in the bandwidth bill. My reading is that the criticis
8.
by bcaxis 2y ago
Making stuff faster is relatively straightforward engineering. Optimisation is a favored past time of many engineers. Getting stuff that people value enough to pay for, to make money, is the hard part. Any friction you put into the value c
9.
by bcaxis 2y ago
> 2. The founder doesn’t understand that the value in a startup isn’t the idea but the ability to execute and build on that idea. The best startups have both. You can execute, great. But if you have poor industry understanding and no id
10.
by bcaxis 2y ago
I've seen such title inflation work for people. Recently watched a relatively young person parley a position at a small company with a VP title that resulted in a slot at a regionally well known organization as a director and then pres
11.
by bcaxis 2y ago
> it's not like you're going to realize equivalent margins by running your own little server I get even better than their margins. In the neighborhood of 100x cheaper. It's not rocket science. > equivalent availability
12.
by bcaxis 2y ago
AWS spends tons of engineering time on features you don't need. There is a lot more than 30% on the table.
13.
by bcaxis 2y ago
The cheap instances are ipv6 only and only a couple of their regions have them. Atlanta, I think, does. But yeah, it's a teaser that isn't realistic. At least for me.
14.
by bcaxis 2y ago
> nobody measures such metrics: size, bloat, speed... Have you ever looked at the bloat of linkedin web? I've had tabs over 1GB memory use. Most bloated site I've ever used with any kind of regularity. > Not related to Lib
15.
by bcaxis 2y ago
Apparently I don't understand. If the code isn't poor, why throw it away for a new even more complex system? I don't know how code isn't poor, yet is indecipherable. Regardless, the method works even in a complex envir
16.
by bcaxis 2y ago
Sometimes API calls make 5-10 queries to the database. So it's 600ms to setup TLS and make a call at the origin server and the number of db calls is irrelevant. Or a quick TLS connection to the edge and 1000-2000ms to fulfill because
17.
by bcaxis 2y ago
You could solve this other ways. Build a new better monolith and have a reverse proxy route between them and slowly update and move routes over. You will get through a rewrite slowly one bit at a time. If you keep the same database schema
18.
by bcaxis 2y ago
If your database is a long ways off an edge connection could end up with a worse latency situation than TLS setup. Distributed database is usually painful.
19.
by bcaxis 2y ago
> Fewer IT staff for systems mgt This hasn't been my experience. Replace sysadmin with cloud engineer/architect, salary bump, no reduction in quantity. This assumes you are mildly competent as an organization. On managed serv
20.
by bcaxis 2y ago
> 1:1 lift and shift is always obscenely more expensive. Is it? Managed services cost a lot more than a vm. Re writing software cost a lot more. Where are the savings?
21.
by bcaxis 2y ago
> first of all, ahrefs discounts the "people" cost, but that's a huge cost to ignore! It's the hardest to compare. Cloud has a significant people cost too, particularly in the complexity. EC2, lambda, S3, RDS, IAM,
22.
by bcaxis 2y ago
> You save money by re-architecting and using more managed services. Managed services are more expensive, not less, per unit compute, per operation, etc. How exactly does that make things magically cheaper?
23.
by bcaxis 3y ago
Modifying the base alphabet is simple if there are a couple of problem characters. I use 85 in json just fine without escaping overhead. Never tried for URLs or XML.
24.
by bcaxis 3y ago
For your trouble, you save some extra bytes with 85 vs 64.
25.
by bcaxis 3y ago
Rumors are of mainline support pretty quickly. But the proof will be when it actually happens.
26.
by bcaxis 3y ago
Power limits probably affect this. And scaling cores isn't linear, their cores clearly scale poorly. Though Geekbench particularly scales poorly with cores.
27.
by bcaxis 3y ago
Yeah, if you make a bad faith effort to comply you deserve to be sued. If you did your honest reasonable best, a suit shouldn't go anywhere. Systems aren't perfect. They aren't really expected to be either. Given the way th
28.
by bcaxis 3y ago
I'm in a similar boat. Rural Midwest. Worked for 23 years now in professional development. Started in big companies, then moved to smaller companies/startups. I'm very very good at what I do and my salary is up to the point
29.
by bcaxis 3y ago
Metered GB is fine if there isn't a 8,000% markup. 200-300% would be much more reasonable and the angst over this would probably just go away. They are also already doing 5 on ingress. But maybe you consider it 2.
30.
by bcaxis 3y ago
Ssh struggles with high connection counts and has performance issues that crop up and require the forward to be torn down and rebuilt occasionally when I have high connections over time. Performance, while it's working, I've found

More ›