[throwaway122kk]

Arghh the biggest issue in current place (I be leaving before year end) is the amount of "engineers" who are pathologically afraid of relational database.

You have dozens microservices per teams, split between k8s, meso, aws, azure, physical servers each on using everything under the moon to store data up to storing files in s3

Needless to say the amount of issues due to data inconsistencies is incredible. And of course the amount of actual users of the overall product is tiny being an enterprise products, maybe few thousand concurrent users at peak.

They now want regional replication and screwed due to so many sources of data. Where postgres alone would have done

[hinkley]

I currently have a bunch of clowns who are indistinguishable from most of the clowns in my profession. Application slow? We’ll just add caches instead of trying to create an architecture.

“But we have an architecture.” No, you don’t. You have a set of idioms that you arrange like dominoes until an answer you like comes out the other end. That’s only an architecture in the way suffering is a personality.

You don’t need more caches. You need an architecture and dynamic programming. Someone save me from promise caches. First couple times they were so cool, now they’re a golden hammer for lack of even the most rudimentary of data flow analysis.

[wpietri]

I've long thought that caching is to software architecture what ketchup is to diner food. Something's not right with your meal? Just apply more ketchup.

[abdusco]

Isn't dynamic programming (specifically memoization) a specialized type of caching? Am I missing something?

[amelius]

Perhaps you need an architecture which uses caches ... And you were both right.

[andy_ppp]

This is standard practice in the micro services world, bin ACID compliance and replace it with network partitions because you’re so fashionable you have no users and no data.

In the system I’m working on (it’s mongodb tastic) someone had added a try catch around everything (EVERYTHING) that reverts the service manually in the catch block. I don’t need to explain to people here how moronic rolling your own transactions like this is...

Everywhere using micro services appears to be the same :-/

[hinkley]

I don’t think we’ve quite cracked how to have a bunch of things behave the same without being the same thing. With DCVS, containers, monitoring systems and the like, we are nibbling at the edges but there’s a lot left to be desired.

You and I should be able to benefit from a set of corporate- or at least division-standard data retention services without sharing a database, let alone each other’s schema.

[tsjq]

Looks like every single engineer / lead wanted to have their favourite bleeding edge technology.