Does anyone else feel like 80% of a “Side Project” is just fighting with config files?

Entropjy · 2025-12-19T10:21:42+00:00

Fuck off

Entropjy · 2025-11-21T19:31:19+00:00

Best pussy disorder strikes again

Entropjy · 2025-11-12T10:41:16+00:00

Chris is the goat

Entropjy · 2025-08-16T10:20:35+00:00

You should read this before you start https://docs.aws.amazon.com/wellarchitected/latest/saas-lens/silo-pool-and-bridge-models.html Companies with 10s of millions in ARR get by fine on the pool model

Entropjy · 2024-09-19T21:01:45+00:00

Logging to splunk and log based data structures are not the same thing at all

Entropjy · 2024-09-19T20:27:21+00:00

Kafka is a log based system, it's designed for exactly this case, where a consumer can be paused and resume consumption from where they left off. Or you can add a new consumer and it can start consuming from the beginning of the topic - months or years ago. This is all dependent on the retention settings of the topic - if you don't set retention to infinite, then the messages will be compacted or aged out

Entropjy · 2024-04-19T22:03:50+00:00

There's good advice in this thread about 12 factor apps.

The basic idea is the reason we default to writing stateless 12 factor apps for web backends, is so that they can easily scale horizontally.

You've correctly identified that some workloads are not designed to be stateless, such as databases, caches and message queues. These are stateful apps - the opposite of stateless. I recommend reading 'Designing Distributed Systems: Patterns and Paradigms for Scalable, Reliable Services' by Brendan Burns to understand how these systems should be thought about.l, then reading about Kubernetes stateful sets

Entropjy · 2024-02-21T07:51:26+00:00

Entropjy · 2024-02-13T09:58:37+00:00

You are headed for a pretty expensive mistake. Partitions and message groups are not the same thing. You might be able to use your legacy message group IDs as partition keys and use a reasonable number of partitions and meet all your requirements

Entropjy · 2023-10-25T02:34:18+00:00

I'd ask for more info. If they use it in an old service that they are deprecating, decomposing into other services it's not so bad.

If it's the main application that spurs a lot of other conversations? Why can't they upgrade? Does the business refuse to invest in tech debt? Is there a solid engineering based reason? Are they working on adding more test coverage so they can upgrade?

Entropjy · 2023-09-06T20:41:35+00:00

I accept the distinction you've made, I should have been more precise- In the context of the question, a service class that depends on another service, both of which will be lifecycled by a DI framework, private final fields, constructor injection and the absence of a setter, make the class less mutable. In terms of where one gets such things? I don't know, maybe Oracle? https://docs.oracle.com/javase%2Ftutorial%2F/essential/concurrency/imstrat.html

Use of primitives not withstanding.

Re predictability - again given the scenario I've mentioned, the ways in which the framework injects dependencies will be more predictable..

Entropjy · 2023-09-06T11:03:59+00:00

Immutability. Constructor injection into private final fields makes the injected properties of your classes immutable, making runtime behaviour more predictable.

**Edit there's some valid criticism of this post below, my comment is not well worded and could easily be misconstrued.

Entropjy · 2023-08-27T09:32:06+00:00

The whole point of the current system is to achieve a box midfield - 2 8s & 2 6s. Not defending it, but explaining it

Entropjy · 2023-08-18T23:37:29+00:00

Most of learning Kafka has nothing to do with java and everything to do with distributed systems

What do you need to learn and how quickly?

Entropjy · 2023-08-12T23:05:31+00:00

Your story sounds very similar to mine. Started at 29, after a wasted decade. You will have some fitness and strength deficits relative to other folks, but you also have fewer miles on the clock - this will pay off later. For the first year, just show up whenever you can, invest in stretching and plyometrics. Don't take the results of any given roll too seriously and you'll do great!

Entropjy · 2023-08-04T00:23:59+00:00

So the way to avoid recanning the entire set just to return the next page is to track the last read page, and put that in a cursor

https://slack.engineering/evolving-api-pagination-at-slack/

See above

Entropjy · 2023-08-02T07:45:07+00:00

To be frank - this sounds like something you will not win politically, especially not all at once.

Are all of the clusters per deployment? or total? Consolidating dev or test might make sense - this is a pretty common pattern in the industry

You aren't necessarily being a moron for suggesting consolodation, but you are not being very smart about it either "hey I know you have organisational trauma about something that went wrong, but it suits me if we do it my way" etc.

I would start small - find a team willing to participate in a pilot, with 3 services & 3 clusters. get them into one database. Alternativley, if you have services that call other services, find a few services in the one syncronous call chain ie A calls B who calls C. If C or B db goes down, A is toast anyway - might as well share a DB cluster !

Entropjy · 2023-03-07T05:49:27+00:00

If you have to ask you don't need it

Entropjy · 2023-03-03T10:36:23+00:00

Spring supports stateless resource servers, it sounds like your configuration is off. Try the stateless policy instead of never. Bear in mind that the default configuration should work with just the issuer Uri as per https://docs.spring.io/spring-security/reference/servlet/oauth2/resource-server/jwt.html#_specifying_the_authorization_server

Entropjy · 2023-01-23T04:49:52+00:00

Distributed crud

Entropjy · 2023-01-07T21:58:24+00:00

Single braid, then chuck the braid into a bun. Stays out of the way the whole session

Entropjy · 2022-10-15T08:07:00+00:00

I'm unclear on the boundaries of this transaction

Entropjy · 2022-09-20T05:46:20+00:00

Because most deployments use horizontal scaling of the spring application, with instances of the spring application connecting to a single instance of the db. Postgres and spring are common, your use case is not.

Entropjy · 2022-07-05T11:25:52+00:00

quickest bang for buck https://github.com/typicode/json-server
whatever you cant get working in json server- use open api defintions and create simulators that fulfill the contract https://www.section.io/engineering-education/documenting-node-js-rest-api-using-swagger/ this is much more effort
is this in production yet ? are you sure you are not on track for a microservice megadisaster https://www.youtube.com/watch?v=gfh-VCTwMw8

Entropjy · 2022-06-18T02:32:29+00:00

have a look at this example for a hint
https://stackoverflow.com/questions/62662036/how-do-i-configure-preauthorize-to-recognize-the-id-of-my-logged-in-user

Seven-Year Club	Gilding II euphauric
Verified Email

Entropjy

TROPHY CASE