redact207

15 ms·

91.
by redact207 7y ago
Totally agree. Microservices is an optimization, not an architechure that you start off with. They can absolutely kill your ability to iterate if your boundaries suddenly change, which happens all the time if your startup is pivoting
92.
by redact207 7y ago
What's wrong with a monolith? You can have ones with well organised internal boundaries. Likewise you can have microservices that are a complete mess
93.
by redact207 7y ago
I really love the concepts provided by Domain Driven Design (DDD), regardless if you choose OOP or FP to implement it with. It's fine if you want to choose C#, and there're better ways of addressing the approaches to validation in
94.
by redact207 7y ago
Our coal industry in Australia has the government in their pocket. Despite coal power globally in the decline, the government has agreed to open and subsidise new coal plants. It's all socializing the costs and privitizing the profits.
95.
by redact207 7y ago
Not on my MacBook:/
96.
by redact207 7y ago
I've been building distributed systems, big ones, across banking and gaming for many years now. The only thing that makes it successful is correct data modeling and application boundaries. Domain driven design is a great way to start a
97.
by redact207 7y ago
This was mentioned during the last spike and used to provide justification to crypto. In reality no one there was using it for this as they couldn't even wire their cash out of the country and into the exchange
98.
by redact207 7y ago
Splitting your app up based on "cognitive load" is just as bad a boundary as 100 LOC per microservice. It's an arbitrary measure and varies widely per developer. The most "correct" way I've ever seen applicatio
99.
by redact207 7y ago
I'm bewildered because every senior dev I've ever spoken to has been somewhat unanimous about the use of types and tests. Reading this I'm wondering if there's a special context where this proposed approach is more suita
100.
by redact207 7y ago
I studied this as part of my degree. It's mostly the ice cream vendors problem, where apparently the franchises would prefer to saturate a smaller area with competitors than a larger area with no competition. It's probably an over
101.
by redact207 7y ago
You're absolutely right, in fact I have a whole package that is just that https://node-ts.github.io/bus/packages/bus-workflow/ . The problem is this. Let's say that I want to trigger a step in a &quo
102.
by redact207 7y ago
Author of https://node-ts.github.io/bus/ here. SQS is definitely one of my most favourite message queues. The ability to have a HA managed solution without having to worry about persistence, scaling or connections is h
103.
by redact207 7y ago
I'm a DDD convert, but boy do I still have trouble selling it. "why do we need a ubiquitous language?" "why can't I jam everything into a single domain?" "why can't everything be an aggregate root?&qu
104.
by redact207 7y ago
These principles are the first thing thrown out the window for new apps. I've been developing for around 15 years and I've noticed the excitement of new devs on new projects who'll rush out and just throw something together q
105.
by redact207 7y ago
That's a weird situation, I've never seen that happen personally. A good service bus should avoid this. For example, https://node-ts.github.io/bus/ subscribes it's queue to all message topics that it han
106.
by redact207 7y ago
Why do you say that? I'm someone who's worked on a few very large message based systems in finance for years (100s of devs working together in multiple countries). I found that messaging and workflow orchestration were the things
107.
by redact207 7y ago
This article talks about the benefit of a message bus being pub/sub. This definitely helps to decouple the internals of apps, which in turn makes things easier to maintain. There are many other benefits to using a message bus, and it&#
108.
by redact207 7y ago
this is what I've been looking for for a long time and wish it was more mainstream. I'd go a step further and say I'd prefer not to vote for a party; but rather cast my preferences like your form and then elect parties based
109.
Distributed message based applications in Node – a Framework(node-ts.github.io)
1 points by redact207 7y ago|0 comments
110.
A Domain Driven Design Framework for Node(github.com)
1 points by redact207 7y ago|0 comments
111.
A Starter Project for building distributed message driven apps with Node(github.com)
1 points by redact207 7y ago|0 comments
112.
Ask HN: JavaScript Devs, have you ever built message driven systems?
1 points by redact207 7y ago|1 comments
113.
A Starter Project for Building Distributed, Message Based Node Apps(github.com)
3 points by redact207 7y ago|0 comments
114.
A Starter Project for Building Distributed, Message Based Node Apps(github.com)
2 points by redact207 7y ago|0 comments
115.
Building distributed message driven apps with Node(node-ts.github.io)
2 points by redact207 7y ago|0 comments
116.
Rock Solid Node Apps with Messaging(node-ts.github.io)
1 points by redact207 7y ago|0 comments
117.
Show HN: An Enterprise Service Bus for Node(node-ts.github.io)
1 points by redact207 7y ago|0 comments
118.
by redact207 7y ago
Some great advice here. To add another perspective: sometimes you don't know where your idea will take you. A lot of your competition is locked into their path. Being at the outset of yours, the customers you listen to along the way ma
119.
An Enterprise Service Bus for Node(node-ts.github.io)
1 points by redact207 7y ago|0 comments
120.
by redact207 7y ago
It's certainly acceptable to start workflows explicitly! However it wouldn't be a good fit for the user signup process. In the above example, the user just wants to signup. They don't care about receiving a welcome email or b

More ›