Live data from Hacker News

You want microservices, but do you need them?

docker.com

1–10 of 151 posts

Re: You want microservices, but do you need them?

#4
post #3

The 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.

I feel that if you have multiple sets of application logic that need to access the same data, there should be an internal API between them and the database that keeps that access to spec.

Re: You want microservices, but do you need them?

#6
post #3

The 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.

A databases is a global variable in disguise.

Re: You want microservices, but do you need them?

#7

I 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?

#8

I 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 ).

highly depends on the wasm runtime we're running things on. I haven't seen any good recent benchmarks (as in the past few years). But, if I remember right wasmer is putting together some and trying to automate the results for them.

Re: You want microservices, but do you need them?

#9
I don't want microservices!

What 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.

Post reply on HN