Moving a legacy system from micro-services towards a new monolithic Elixir application
Sometimes we love boring! No need to do Trends Driven Development (TDD)
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.
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.
