Just-in-time Architecture • Macklin Hartley • YOW! 2022

[@archi-mendel]

I hope this gets a lot of views. The cafe example is something I am going to use too 👍

[@timibolu]

Good talk. Learned a lot

[@stevenhe3462]

This is why the microservice-ish monolith Erlang/Elixir architecture is very good.

[@AlexanderRoempke]

i personaly think thats the way to go, event driven design plus oop seems to try to be elixir but realy never is.

[@krazeemonkee]

a lot of the methods/terms used in the microservices implementation sounded a lot like erlang-land talk w/ processes, managers, events/commands etc ~ however, in the land of erlang, these concerns are components of a monolithic system/network, correct? is there a hybrid architecture that meshes erlang/beam w/ microservices? [i’m still a little programming sprout 🌱 so i hope my question even makes sense]

[@stevenhe3462]

@@krazeemonkee Yes, you just send requests between the Erlang monolith and the microservices. Mixing monoliths and microservices is nothing new.

[@recklessroges]

So this isn't JiT Architecture. It is Architecture that your company migrated to "just in time" for each expansion, development and as additional complexity was added. [The title confused me because I'm used to JiT compilation.] I wonder how much survivor bias this contains?

[@asdqwe4427]

I think focusing on providing value as quickly as possible is the only way to survive as a startup.

[@trejohnson7677]

Exactly wtf what you were expecting?

[@Reashu]

​@@trejohnson7677 as they alluded to, probably "the architecture of a just-in-time compiler"

[@asdqwe4427]

@@Reashu I expected the talk to be about caring about architecture when it tat starts to matter