You want microservices, but do you need them?
1–10 of 151 posts
Re: You want microservices, but do you need them?
#2Re: You want microservices, but do you need them?
#3Large, shared database tables have been a huge issue in the last few jobs that I have had, and they are incredibly labor intensive to fix.
Re: You want microservices, but do you need them?
#4The one thing I would like to preserve from microservices is stuff about database table hygiene. Large, shared database tables have been a huge issue in the last few jobs that I have had, and they are incredibly labor intensive to fix.
Re: You want microservices, but do you need them?
#5I don't want microservices, I think what I really want is self contained WebAssembly modules!
Re: You want microservices, but do you need them?
#6The one thing I would like to preserve from microservices is stuff about database table hygiene. Large, shared database tables have been a huge issue in the last few jobs that I have had, and they are incredibly labor intensive to fix.
Re: You want microservices, but do you need them?
#7I don't want microservices, I think what I really want is self contained WebAssembly modules!
Re: You want microservices, but do you need them?
#8I don't want microservices, I think what I really want is self contained WebAssembly modules!
What's the performance trade-off of something like this over containerization? I have heard of an operating system that runs WASM ( https://github.com/JonasKruckenberg/k23 ).
Re: You want microservices, but do you need them?
#9What I want is a lightweight infrastructure for macro-services. I want something to handle the user and machine-to-machine authentication (and maybe authorization).
I don't WANT the usual K8s virtual network for that, just an easy-to-use module inside the service itself.
You should be able to spin up everything localy in a docker-compose container.
Re: You want microservices, but do you need them?
#103 tier architecture proves time and time again to be robust for most workloads.