8 ms·
Agreed, anytime I talk with someone about DevOps ... we end up having to hash out the entire process to really know what either of us are actually talking about
by duxup 4y ago
Agreed, anytime I talk with someone about DevOps ... we end up having to hash out the entire process to really know what either of us are actually talking about. Otherwise you have these situations
"Yea the DevOps guy messed up the widget and nobody notic---"
"Wait, what is the DevOps guy doing even touching that widget.... what is even DevOps to you?"
"Bro that widget IS DevOps."
-silence-
Same applies to the topic of "micro-services".
- boppo1 4y ago>microservices I never miss an opportunity to share my favorite piece of comedy this decade: https://youtu.be/y8OnoxKotPQ https://youtu.be/y8OnoxKotPQ
- soperj 4y agoSOA is just Spaghetti Architecture. I haven't seen an implementation that convinces me otherwise.
- duxup 4y agoI feel like it has its place in large organization. But being a large organization means the odds of spaghetti are approaching 100% no matter what you do.
- jedberg 4y agoWhat is your definition of Spaghetti Architecture? Netflix had a good SOA that enabled rapid development and had strong cut lines between services, with no way to access the data of a service without going through the service's API. I think that's where most people go wrong. They put a bunch of services in front of a shared database, which means that they don't have to go through a service's API to get to it's data, and that's what breaks everything.
- eropple 4y agoThis is really important, and I've gotten a lot of quizzical looks when making this assertion over the years: data is owned by one and only one service. If two pieces of code assert ownership of it by mutating that data or looking past the public encapsulation of that data, then that code is the same service. If you see a queue between two services, that is usually an indication that some ownership is being transferred (even briefly), and that is a critical point where you need introspection and observation.
- lamontcg 4y agoYeah, services should be formed around the needs of data, and you shouldn't run multiple services in the same image/container just to split the code up. It shouldn't ever be about the code. Amazon's SOA architecture at least all started out about pulling bits of data spread over hundreds of servers into services that could take advantage of caching.
- wikibob 4y ago> Data sovereignty per microservice > An important rule for microservices architecture is that each microservice must own its domain data and logic . Just as a full application owns its logic and data, so must each microservice own its logic and data under an autonomous lifecycle, with independent deployment per microservice. https://learn.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/data-sovereignty-per-microservice https://learn.microsoft.com/en-us/dotnet/architecture/micros...
- 4y ago
- Kinrany 4y agoAny general purpose architecture allows spaghetti, there's no way around it.
- usrusr 4y agoHas there been an architecture movement that formally embraces the spaghetti, aiming for peaceful coexistence? Detractors will certainly point at SOA and shout "that one!", but I mean one that openly admits..
- Spivak 4y agoI’m not sure if this architecture has a name other than “Event Sourcing” but I think giant org wide shared message bus with all services freely pushing and pulling data from it is the closest to embracing spaghetti.
- rileyphone 4y agoMicroservices should be resource-oriented, not service-oriented. NetKernel takes it to the extreme, it’s a shame it hasn’t seen broader adoption. http://resources.1060research.com/docs/IntroductionToResourceOrientedComputing-1.pdf http://resources.1060research.com/docs/IntroductionToResourc...
- dustymcp 4y agothis devops is also a dumping ground for anything else not happening on a developers computer which they should control but wont because "That is devops job" mostly this happens alot with node projects for some reason..
- duxup 4y agoHumans are kinda terrible when they can just "not my problem" things.
- chrisweekly 4y ago"anything else not happening on a developers computer which they should control but wont" Ok, I've seen this, but IME (24y in industry, the last 6 as a consultant) in the vast majority of cases, it's more like "things devs should control but CAN'T [bc CICD etc are silo'd and owned jealously by an overburdened ops team unable or unwilling to facilitate self-service]".
- outworlder 4y agoSome of the 'jealousy' may also come from bad experiences. It only takes a few instances of people royally messing stuff up in production for their deployment rights to be stripped away – and other groups catch the fallout too, as new "procedures" get implemented.
- dijit 4y ago"Safety rules are written in blood" applies to parts of the organisation too. Sure, there are some overbearing procedure monkeys who really want a process on everything, but a lot of "protection" rules are there because something really bad (and expensive, financially or reputationally) has happened before.
- kazen44 4y agoAlso, some developers do not seem to know what kind of impact a production issue can have. Having something not work during the development cycle is annoying for one person or a team. Having something break in production usually means people get paged and (depending on what you do) the resulting issues can have major societal aswell as economic impact. In the ops world, this is especially visible if you go further down the stack. (from applications down the the network). Network architecture moves at a toad's pace compared to webdevelopment, which is a good thing considering breaking the network will usually break every other system inside a IT department/landscape.
- sbf501 4y ago"Hey, did the front-end new-hire upgrade the Linux distro yet?"
- duxup 4y agoSide rant: There was an angry Ask HN post a while back about how terrible the "new guys" are that are out there. It then complained that the new hire wrote a horrible authentication service. I thought it was an intentionally absurd post about the expectations put on new some rando new guy to write something important / they shouldn't be working alone on ... but they were serious.