14

Moving a legacy system from micro-services towards a new monolithic Elixir application

top 3 comments
sorted by: hot top controversial new old
[-] empyrean@lemmy.world 6 points 1 year ago

Sometimes we love boring! No need to do Trends Driven Development (TDD)

[-] msage@programming.dev 3 points 1 year ago

Hear hear.

Though, after many professional years, I concluded you just need people at your level of knowledge around you.

You can do basically anything, even trendy stuff, when you deal with people who actually understand the technology.

When I listen to folk yapping about stuff I consider basic, and suddenly adding 'service discovery' into the mix, and see no connection between the topics discussed, I know I'm in for a bad time.

[-] funbike@programming.dev 1 points 1 year ago* (last edited 1 year ago)

This sounds like vertical slicing (incl bounded contexts), which is my preferred architecture for a monolith. It gives you the flexibility to pivot architecture more easily.

I suggest you look into Evolutionary Architecture, with can help keep vertical slicing

We've gone all-in with SSR+FaaS (aka JAMStack) with multiple projects. You get similar benefits to microservices, but without the complexity. However, hosting can be more expensive under high loads.

load more comments
view more: next ›
this post was submitted on 13 Jun 2023
14 points (100.0% liked)

Experienced Devs

3926 readers
1 users here now

A community for discussion amongst professional software developers.

Posts should be relevant to those well into their careers.

For those looking to break into the industry, are hustling for their first job, or have just started their career and are looking for advice, check out:

founded 1 year ago
MODERATORS