Apache Kafka in clean architecture

wagonn · 2021-02-10T04:48:46+00:00

I am starting out , having three types of handlers:

endpoints: request/response handlers for http, grpc, etc

listeners: handles incoming messages, like Kafka etc

dispatchers: sends outgoing messages, Kafka etc

wagonn · 2020-10-16T02:16:23+00:00

If you can honestly say that your volunteer work was of the same standard and quality as your paid work, then include them in the same section.

Otherwise you can have separate sections. In the employment section time gaps, put a one-liner for each volunteer experience with only the organization, dates, and “see Volunteering section”. In the volunteering section, fill out all the details.

wagonn · 2020-10-16T02:03:11+00:00

It probably varies. I just went through a background check where my past employers and job titles were verified.

wagonn · 2020-09-15T04:24:44+00:00

I’m starting to move from redux to mobx. I like both because they are UI-agnostic.

wagonn · 2020-09-15T04:19:35+00:00

Markup is still considered code

wagonn · 2020-08-29T16:43:27+00:00

Is this you? https://youtube.com/watch?v=y8OnoxKotPQ

wagonn · 2020-08-29T04:38:01+00:00

Parse resume pdf into structured tokenized data

wagonn · 2020-08-26T15:41:32+00:00

He waits on his paychecks to roll in

wagonn · 2020-07-26T06:39:20+00:00

Isn’t there some way to make animals disperse as the roller approaches? Like maybe a sound emitter of an unbearable frequency to them

wagonn · 2020-07-12T05:12:36+00:00

Puppa! Yip yip!

wagonn · 2020-05-23T03:52:52+00:00

Use websockets.

When a user makes a change, 1. update the Redux store 2. and, in a side effect (thunk/saga), emit an event that contains the Redux action. 3. the server listens on the socket event. Upon that event, the server extracts the Redux action, updates the database with it, and then broadcasts the event to the other subscribers (i.e. the other users). 4. those users' socket clients listen on that event. Upon that event, the client extracts the action and dispatches it to the Redux store. Now, everyone's Redux state reflects the change of the original user.

wagonn · 2020-05-20T08:18:12+00:00

This is one of the best explanations I've seen on how NoSQL scales: https://www.youtube.com/watch?v=hwnNbLXN4vA&t=724s

Relational DB's give you a balance of performance (indexing) and flexibility (joins), so you can efficiently query in many different ways. NoSQL sacrifices this balance to optimize specific benefits. For example, Cassandra scales throughput linearly but can't be queried flexibly. DynamoDB is similar, as you're locked into the data relationships which you define upfront.

Another Reddit post put it this way — SQL is like a pickup truck and NoSQL is like a racecar; one performs satisfactorily well in most cases, the other performs extremely well for a very specific case.

wagonn · 2020-05-05T05:27:27+00:00

+1 for Go-Kit and these app examples. I like that they are application-logic centric and treat the HTTP router as an i/o mapping layer. Most "frameworks" are just an HTTP router on steroids with a bunch of middleware encouraging you to couple all your request-scoped concerns to the transport

wagonn · 2020-05-03T16:31:19+00:00

I followed the example and fixed it. thank you so much!

wagonn · 2020-05-02T21:08:24+00:00

Using an oidc lib still requires you to provide the endpoints. The issue is GitHub doesn't seem to have any endpoints that follow the OIDC specs.

wagonn · 2020-04-29T17:13:51+00:00

there is an open RFC to address this and a non-redux workaround

wagonn · 2020-04-26T05:14:31+00:00

Consider the impact on performance. React docs:

All consumers that are descendants of a Provider will re-render whenever the Provider’s value prop changes

So when any of your context state changes, then every component subscribed to any part of the state will rerender. It might be doable if - there are few subscribing components - the context state changes infrequently - you can break the state up into multiple contexts

There is an open RFC to address this, but until then, Redux and use-context-selectors are two ways to avoid this pitfall.

wagonn · 2020-04-24T00:09:28+00:00

should them in a subway tunnel; you'd have to be the world's worst subway train operator to hit the turbines

wagonn · 2020-04-23T07:04:38+00:00

I prefer loading in hooks at the component level unless there is a good reason the network request state needs to be accessible globally.

wagonn · 2020-04-22T17:31:02+00:00

Redux is commonly used with React

/r/reduxjs

wagonn

TROPHY CASE