HNHacker News
TopNewBestAskShowJobs

james_s_tayler

2,220 karma · joined October 30, 2018

submissionscomments
james_s_tayler··on The Myth of the Myth of the 10x Programmer
10x is also about quality. Not raw output. A lot of times the really fast devs are fast because they don't stop to consider how they can do things in a fundamentally much better way, they just churn out the status quo as fast as possible. Those type are not 10x.
james_s_tayler··on What eight years of side projects have taught me (2019)
Pick one you're proud of and have the rest of the unfinished stuff as private repos.
james_s_tayler··on A 2,500-mile radius in Asia contains half the world's population (2017)
You Made My Day?
james_s_tayler··on Facebook quitters report more life satisfaction, less depression and anxiety
How long have you quit the news for?

I sometimes do that but I'm never able to quit it permanently.

james_s_tayler··on Questions to ask before adopting microservices
>That's reasonable. Also consider going the other way: keeping per-tenant logical databases, and splitting up some or all of the compute layer to have single tenancy or bounded tenancy. For example, if your compute layer is a web server, making multiple sets of webservers with something in front of them routing requests to a given set of servers based on a tenant identifier can chunk up your multiple-noisy-neighbors problem into at least multiple noisy "neighborhoods", with the (expensive) extreme of server-per-tenant. If your compute layer is e.g. a service bus/queue/whatnot worker, the same principles apply: multiple sets of workers deciding what to work on based on a tenant ID or per-tenant/group topics or queues. You can put the cross-cutting/weird workloads onto their own areas of hardware, as well

This pretty much describes exactly where we are right now. We've been able to migrate the big customers to a new, less overloaded database server. We could continue to do that. I believe it's what you call a "bridge" architecture, so the compute layer is stateless and can serve any tenant. It's also got a queue/service bus to offload a lot of stuff that the web servers shouldn't be doing. That stuff is all on autoscaling but even that's not a panacea.

james_s_tayler··on Questions to ask before adopting microservices
I work on it every day. The earliest commit to the repo is 2010. The engineering team on average over that time is circa ~20 people.

So... Yeah. Thanks for denying my reality I live every day.

james_s_tayler··on Ever Loved’s funeral marketplace undercuts undertakers
I'm guessing it's a volume thing? The point of market entry for a casket is literally someones death. It's not you can run facebook ads to boost sales of caskets...
james_s_tayler··on Why we need a book about naming
I really like the way you write. You need to write a book. It would be great.
james_s_tayler··on Questions to ask before adopting microservices
I think there are some things we can legitimately improve quite a lot under the current structure, and it seems there are other things that make certain improvements just untenable.

Upgrading a major version of an ORM for instance. It seems there are certain key improvements that boil down to "the only way this can be improved would result in a big-bang release affecting the entire of the system and take a dedicated team quite a long time to do". It's just not palatable for anyone.

For the parts we carve out as microservices we are essentially able to erase that technical debt. That comes at the cost of increased ops complexity. We're not ready or capable of having 50 microservices from an ops perspective, but we are capable of handling more on the order of ~5.

james_s_tayler··on Questions to ask before adopting microservices
This is pretty much my thinking.
james_s_tayler··on Questions to ask before adopting microservices
I definitely think a reasonable degree of performance could be gained under the current structure by streamlining data access and maybe getting a bit smarter with caching. That still leaves us with non-scaling related problems of being unable to upgrade some very core dependencies which are stuck on some quite outdated versions.

Perhaps the strangler application approach could work to resolve that aspect over time.

james_s_tayler··on Questions to ask before adopting microservices
We need to support an order of magnitude more daily active users than we currently do. I'm not exactly sure how close the current system would actually get to that, but my gut feel is it wouldn't hold up. It does OK as is, but only OK.

It's a combination of three different problems working against us in concert.

1) compute layer is multitenant but the databases are single tenant (so one physical DB server can hold several hundred tenant database with each customer having their own).

2) We're locked into some very old dependencies we cannot upgrade because upgrading one thing Cascades into needing to upgrade everything. This holds us back from leveraging some benefits of more modern tech.

3) certain entities in the system have known limits whereby when a customer exceeds a certain threshold the performance on loading certain screens or reports becomes unacceptable. Most customers don't come near those limits but a few do. The few that do sometimes wind up blowing up a database server from time to time affecting other clients.

For most of the domain stuff, to be honest I'd like to fix the performance problems and deadlocks by just making data access as efficient as possible in those spots. I think that could get us quite a bit more mileage if we took it seriously and pushed it.

For the single tenant database situation, I don't really know how to approach fixing that. I don't see us having enough resource to ever reengineer it as is. Maybe it's possible for us as a team, maybe it's not. The thinking is that for the parts of the domain we're able to split out, we could make those datastores multitenant.

There's also a bunch of integration code stuck in the monolith that causes various noisy neighbor problems that we are trying to carve out. I think that's a legitimate thing to do and will be quite beneficial.

But yeah... It's a path we're dipping our toes into this year in an effort to address all of these problems which are too big for us to tackle one by one.

james_s_tayler··on Questions to ask before adopting microservices
I think this is going to be the approach we wind up taking.

In reality there are maybe 1 ~ 3 hotpots in the domain that reveice many more transactions than the rest.

james_s_tayler··on Questions to ask before adopting microservices
What do you do if you have ~20 people and a decade old million line monolith that you're now bumping up against the limits of?
james_s_tayler··on Why we need a book about naming
And at most once delivery
james_s_tayler··on Why we need a book about naming
And at most once delivery
james_s_tayler··on An Astronaut’s Guide to Mental Models
The entire reason to call them "Mental Models" is to aid in their communication and discovery.

There are many hueristics that are not mental models. There are many things that are frameworks that are not mental models.

Labelling something a "mental model" as used in this context serves the purpose to communicate "here is an abstraction with unusually good power-to-weight ratio that you can leverage to aide your thinking/reasoning about situations that meet a given set of criteria".

It's actually a very specific thing.

james_s_tayler··on Back to the Future
I think Peter Thiel has too much time on his hands.
james_s_tayler··on An Astronaut’s Guide to Mental Models
So... What would you call them instead?
james_s_tayler··on An Astronaut’s Guide to Mental Models
Mental Models are nothing more than useful hueristics to help you navigate and understand reality.

Whether a mental model ends up with a name on a list is largely down to it's utility in aiding that for a wide audience.

In my experience they have been extremely useful.

james_s_tayler··on Ask HN: Best paid courses you've taken?
I second pluralsight for that budget. I've been a customer for a few years, and I find that I've always gotten the value out of it every year. Some months I won't touch it, other months I'll do course after course integrating the learnings into a side-project. Variety is huge.
james_s_tayler··on Dangerous domain corp.com goes up for sale
Why not?
james_s_tayler··on Debt is coming to the tech industry
Agreed.
james_s_tayler··on Dangerous domain corp.com goes up for sale
Isn't that true though?
james_s_tayler··on Toy commercials are being replaced by product placement and YouTube influencers
You just have to be blunt. It feels kind of terrible but it will sit you free.

I stopped participating in Christmas years ago. Was very freeing.

james_s_tayler··on Scaling to 100k Users
This site isn't Microsoft?
james_s_tayler··on What's SAP?
Sounds like a perfectly cromulent database.
james_s_tayler··on C# Pattern Matching
Usually there are blog posts that do a good job at summarizing what's new in a given release.

I find it helpful to read over them even when picking up a new language / framework to see how it has evolved over time.

james_s_tayler··on Tech salaries are risk premiums
They don't really get everything. They often give a lot up to get what they do too.
james_s_tayler··on Tech salaries are risk premiums
>After all, without them no actual work would be done.

Leadership is the other side of that coin.

← PreviousPage 10 of 34Next →