17 ms·
Microservices – architecture nihilism in minimalism's clothes
- Emanation 6y agoHonestly, a confusing article to read. I think it's difficult to put into abstract words when microservices should be used without bringing up anecdotes of when it shouldn't have been or... that it's simple 'start with one, split with reason,' which is so simple it's hard to follow. I enjoyed reading it, several times.
- jrochkind1 6y agoWow. This is so much cutting through a lot of noise on microservices for me.
- old-gregg 6y agoProgrammers have always partitioned their code in, roughly, the following way: - lines - functions - objects - modules - binaries The languages/terms differed, but that's how software has been constructed since approximately forever, and we've always had debates on optimal size/length of lines/functions/objects/modules, etc. We've also had numerous reincarnations of binaries talking to each other over some form of RPC. What happened here was a marketing knife-war between companies in the container management space. Then someone (we'll never remember who) tried to differentiate by coining this term, which basically means "binaries with RPC". Every binary in your /usr/bin/ is a microservice. Just type `watch date` and enjoy two microservices running, no need for containers/kubernetes :)
- loopz 6y agoThrow IT at wall, see what sticks. You know what, http3 gonna be sick! When you're all alone and feeling insane, you know you lack the sweet sweet 2.0 Webscale.
- remram 6y agoAs a non-native English speaker, I'm always puzzled by Americans rhyming. How does this work? And why does wormhole monocle not?
- pbronez 6y agoOnly the first two lines rhyme.
- loopz 6y agoIt's supposed to make people think ahead. But seems they just get angry instead. Why oh why don't people just see, the true meaning of rhyme, truth and the DDD.
- hsbauauvhabzb 6y agoThis is the first poem I’ve read which mentions DDD. I’ve definitely had enough internet for a while.
- frequentnapper 6y agonone of the lines rhyme.
- eindiran 6y agoRegarding "wormhole" and "monocle", they form a "slant rhyme" or "half rhyme": https://www.thefreedictionary.com/slant+rhyme https://www.thefreedictionary.com/slant+rhyme
- DreamSpinner 6y agowormh_o_le mono_c_le The although both words have the same last two letters - "le", the third last letters are different. This produces a different syllable when pronounced.
- syndacks 6y agoAs a native English speaker, I have no idea what this person was trying to communicate :)
- what-the-grump 6y agoI like it not sure why buried. Guess rings too close to home for some.
- deleted 6y ago[deleted]
- bob1029 6y agoI have found that this applies all the way up to the loftiest levels of abstraction. For instance, we partition our problem space in terms of logical business process once you get to a certain altitude in the architecture. But, the most obvious way to represent these discrete process domains was with... objects. So yeah. It's objects all the way up. The only difference between good and bad code is how the developers handle namespacing, drawing abstraction hierarchies and modeling business facts. Microservices are about organization, not about requests being sent on wires throughout some abomination of a cloud infrastructure. Developing a UserService class and having the audacity to just directly inject it into your application for usage is probably one of the most rebellious things you could do in 2020. Extra jail time if you also decide to use SQLite where appropriate.
- systemvoltage 6y agoWriting straight SQL will land you in a prison.
- collyw 6y agoThings were so much easier 15 years ago. I see very little gain for all the complexity we have added since then. Ok we can scale easily on demand, but the vast majority of places won't need to.
- fxtentacle 6y agoActually, we still can't scale easily on demand. Let's say you get 2x the traffic. Sure, your front-end instances in the cloud can scale to 2x the capacity, but that just moves the bottleneck over to your database. And then you noticed that scaling an Amazon RDS database to a larger instance requires downtime...
- soulofmischief 6y ago> The only difference between good and bad code is how the developers handle namespacing, drawing abstraction hierarchies and modeling business facts. I wish those were the only indicators of bad code, but illegible aesthetics, over-engineered complexity, under-engineered fragile modules, etc. are to be found everywhere.
- nebulous1 6y agoI don't think that definition of microservice is useful and I think it promoting it will add to the confusion around the issue. You can comment on the similarities in the way modern microservices and watch/date are architected without calling the latter microservices.
- dfee 6y agoOne additional level of granularity, above “lines”: tokens. (Expressions mapping nicely to lines, ymmv).
- FpUser 6y agoExactly this. Well hype moves sales when people buy into that marketing crap.
- pjmlp 6y agoEvery couple of years Sun RPC/DCE gets re-invented, basically.
- maxdo 6y agoVersion and dependency is just a tool to achieve expected behavior for API. You still need to change versions centralized. The only difference is that monolith will not let you do that partially. Example there’s vulnerability in package, but only gateway exposed externally. Unless gateway still produced valid json/gRPC etc request it doesn’t really matter , you change a lib version without having impact on all other services that might be affected by library version change. It’s clear that article affected heavily by outdated Java way of building software. Where everything is injected by DI , AOP so even a small change in a core component is a big deal. No it’s not. Unless micro service is doing what expected and passes unit tests I don’t care. Even I change a language or db or network layer.
- boltefnovor 6y agoI prefer lower devops complexity and higher software application complexity. Any day. Microservices is higher devops complexity in exchange for lower software application complexity. A really terrible deal IMO.
- tmotwu 6y agoSure, if you are independently building your service, or working a tight feedback loop with others on the product. As others pointed out, it works for companies who operate and scale engineering teams. Good luck maintaining complex applications across tens to hundreds of developers.
- boltefnovor 6y agoYou are correct and I agree with you. I have not worked in big projects, only small, so that’s where my beliefs come from. I feel the problem is a software problem that should be solved by better development tools/languages rather than throwing up hands and pushing the problem into the operations domain.
- Retric 6y agoTens to low hundreds possibly, but micro services can make things much worse as you scale to thousands of developers. The ultimate limit of any design is how much any one person can understand both from both a complexity standpoint and a rate off change standpoint. It’s the same issue that pushed people from goto > functions > libraries > ... Eventually you need another layer of abstraction. For very large companies doing mergers etc things are always going to be in flux in ways that the startup world tends to ignore.
- andy_ppp 6y agoBut the idea that interacting services can be built by different teams isn’t just dev ops complexity, it’s insanely complex managing that stuff because it involves humans. Never mind that everyone building micro services just goes “fuck transactions and eventual consistency, I’ll go with maybe/probably my data gets corrupted over time” whoop.
- fennecfoxen 6y agoI’ve always seen microservices as primarily used a trendy way to impose basic engineering discipline on projects where there isn’t the will to define interfaces between components explicitly (DNS being a crude service locator pattern, different VMs providing basic encapsulation). Unfortunately this is only a marginal improvement, as the team remains devoid of engineering discipline. :/ This article has meaningful advice but I’m not sure that it will be often applied.
- Twisol 6y ago> Unfortunately this is only a marginal improvement, as the team remains devoid of engineering discipline. :/ This strikes me as the crux here, along with this line from the article: > There were three main reasons for the initial success of microservices as an architectural pattern for software: [...] 3) an excuse for having no architecture. Microservices are a little bit too much of a "just so" story to me. It's a cozy non-answer to the hard problems of system design.
- systemvoltage 6y agoYou nailed it so perfectly. The difference is encapsulation of dependencies and independent scalability of each service. That aside, whether we have a monolith or microservices, you cannot fix bad architecture. It’s like spreading out components with larger copper traces and separating them. If you’re circuit is wrong, no amount of things you can do on the PCB level will fix it. Fix the schematic (circuit) first.
- m0zg 6y agoIMO it's not really about the build at all. It's about people and business. One, for microservices created by the companies themselves, those bascically grow out of their org chart. It is well known that organizations ship their org chart, and this is no exception. Person A wants to become a manager to make more money and ascend the societal hierarchy. Person A's manager wants to grow their fiefdom and have more people under them (which is the only true measure of one's worth as a manager, as far longer term career is concerned), so the person A proposes to their manager that they use "best practices" and carve off a "microservice". Their manager happily obliges, because they don't know anything about distributed systems and consistency. Person A gets promoted. Now person B wants to become a manager to make more money and have their fiefdom... The end result is you have a nightmarish maze of microservices where a single simple monolithic binary would do a better job at one quarter the dev cost. You also have a very deep and branchy org chart, which is the preferred state for the management, since it lets them justify (and increase) their pay. Two, for cloud microservices, they offer a simple way to create recurring, extremely sticky revenue. That's not to say that microservices are useless - they are useful sometimes. It's just that "nobody ever got fired for moving to AWS", and when the incentive structure does not encourage more robust engineering and/or cost savings, your money won't be spent wisely, because nobody gives a shit about that. As with any people problem, the only way to push back against this is by making the desired state the lowest energy state. This can be done several different ways, none of which have anything to do with engineering arguments, at least not if you want it be be effective against such very human things as greed and desire for social status.
- jeremyjh 6y agoI think its kind of both. When you have a lot of people working on a monolithic code base one of the places where you feel the most friction is at the build process. If CI takes 30 minutes for example and you have 80 developers working on the code base (roughly the stats from my previous job) then you can see how just coordinating the build/merge/rebase/build/merge cycle can be an issue without good tooling and practices. At some point service boundaries are inevitable and shipping the org chart is something we've always done. But what is actually happening in some companies is just so far beyond this. There are developers I've talked to at companies where the micro-services outnumber the developers by 5:1 or more. That is insane, and I imagine it did start with the kind of empire building you are talking about.
- shironineja__ 6y agoMost of the issues in the article can be addressed with an API Gateway or similar wrapper abstraction so that consumers may integrate with the gateway one time and then add each feature as-needed.
- boltefnovor 6y agoMy manager at work is a big believer in microservices. I never reveal my true thoughts because I don’t think he would understand the heresy of the unbeliever. Never tell anyone to their face that you don’t believe their god is real.
- deleted 6y ago[deleted]
- bedobi 6y agoI've never understood all this drama. In my experience, monoliths are universally bad in every imaginable way. A huge part of my career has been splitting monoliths into cohesive smaller codebases which could be called microservices. How to split them has never really been a problem, you tend to develop an intuition and the monolith kind of splits itself. Eg, currently we have user profiles (user id > the users names, email etc) in one microservice, relationships between users (user id > other user ids) in another. Each has its own datastore, deployment, scaling etc. It works great and while there is a small overhead cost to pay for splitting things it's vastly preferable to the monolith we used to have, which contained lots of things that had very little to do with each other, took ages to test and deploy, if it went down it was game over etc etc etc.
- nicoburns 6y ago> currently we have user profiles (user id > the users names, email etc) in one microservice, relationships between users (user id > other user ids) in another. What do you do when you need to query data across these boundaries?
- bedobi 6y agoIf most of the callers did need both pieces of data it would have made sense to combine them into a single service. But, overwhelmingly, callers are interested in one piece of data or the other, and the load profile, tolerance for staleness in caching etc etc for each of the two services are vastly, vastly different. This is why we chose to split the two into different services. The few callers that do need to obtain both pieces of data just make concurrent calls to both and them zip them into a single result.
- lowtech 6y agoSounds like you have a simple system, in which case the separation have few drawbacks. It's not uncommon for a customer to ask for a report that to be generated needs to span dozens of tables. Or to save a DTO object that will trigger multiple microservices (and a lot of validations, transactions, rollback, etc). Business rules can be very complex and entangled in some shops.
- spaetzleesser 6y agoI think we need to go back and think about what “micro service” really means. In my company the terms “Web API”, “Service” and “Microservice” are pretty much the same. The only difference is that “Microservice” is cool now.
- OJFord 6y agoAbsolutely, it's applied to everything from tens of thousands of RPCable routines to webapps backed by a handful of 'polyliths'.
- DanielBMarkham 6y agoOverstated. Makes the usual "I hate blah blah" essay mistake of confusing the way something is understood and implemented in the general dev community with what it actually is. Most of the time, things start off for good reason and represent good practices. We just butcher the hell out of them when we start selling them to one another. (Same thing happens in reverse; once enough people destroy any goodness left in a buzzword, people oversell how bad the idea is when they start pitching their plan to get rid of it) To be clear, I don't disagree with the premise that lots of microservices implementations are a clusterfuck of monumental proportions. It's just ranting and raving about devs and dev shops screw up stuff isn't exactly news to anybody. That's the natural state of affairs no matter what your flavor-of-the-week. We get close to something useful near the end, "...focus on the right criteria for splitting a service instead of on its size, and apply those criteria more thoughtfully..." The rest of this looks like a rehash of generally-accepted architectural principles, most of which were misapplied and resulted in us getting here in the first place. I'm not going to line-by-line critique this. There are far too many points to counter and I can't imagine the discussion keeping any sort of reasonable cohesion (hardy har har) if it spreads out that wide. Oddly enough, I find this discussion of why monoliths might be a preferable default state too monolithic to split up into reasonable chunks to analyze. Much irony there. We got to microservices (or I might rather say we _returned_ to microservices) by following good code organization principles. Instead of starting with the resulting implementation (such as the DAGs and various models in this essay) and trying to argue first principles, it's better to start with first principles and then come up with criteria for evaluating various results. I feel I would be neglectful if I didn't add this: if your code is right, whether you're deploying as a microservice or a monolith shouldn't matter. That's a deployment decision. If it's not an easy deployment decision, if you can't change by flipping a bit somewhere, then either your first principles are off somewhere or you made a mistake in implementing them. The way you code should all be about solving a real problem for your users. How you chunk your code and where those chunks go are hardly ever one of those problems.
- nullsense 6y ago>...dev shops screw up stuff isn't exactly news to anybody. That's the natural state of affairs no matter what your flavor-of-the-week. I vote the next flavor of the week paradigm should be centered around this. Devs and dev shops seem to mostly only be able to clusterfuck all the things eventually. What we need is software that is Developer Proof. I'm going to write the Developer Proof Manifesto.
- theptip 6y agoI like this way of thinking about services; decoupling the "project model" from the "deployment model" is a good way of thinking about things. Some random thoughts: * What build toolchains are suited to these arbitrary DAG arrangements? Bazel? Perhaps I missed a reference in the article, but I'd be interested in the author's take on this, and of course any thoughts from the community here. * The "testing monolith" is a pattern that I've used in a less well-named fashion, and it's great for cases where lots of code-services need to execute a business process that might span weeks or months; building a test rig to mock time across an ensemble of microservices sounds like an interesting challenge; mocking time inside a single process running the combined logic of all the services is much more palatable. (This isn't really possible if you use multiple languages though, so it only gets you so far). * DDD bounded contexts as service boundary -- this is a good starting point, especially if you take a loose definition of "service". Under the DDD definition of "Service" you can actually have multiple deployables running; for example a typical Django/Rails monolith will have a DB (SQL) and an async worker (Celery/Sidekiq via Redis/RMQ) and perhaps a cache (Redis) so it's really a bunch of different deployables, even if we refer to it as a "monolith". Likewise with smaller services. If you think of the Service as being a constellation of processes with an external API, then you can start splitting out parts into separate deployables without the outside world caring, say to scale a particular workload independently of the rest of the Service logic. This is kind of the direction that Uber ended up moving in with their "Domain Oriented Architecture" (https://eng.uber.com/microservice-architecture/ https://eng.uber.com/microservice-architecture/). This is actually how Django monoliths already work; you use the same codebase to specify your sync API workers, and your async Celery tasks, and you'll deploy them as separate deployables from the same repo.
- vlfig 6y agoAuthor here. Thanks for reading. > * What build toolchains are suited to these arbitrary DAG arrangements? In general any CI/CD tool that allows for easy composition of jobs/pipelines, where versioned artifacts are a first-class citizen and can be the outputs and the inputs of jobs. Preferably one where the graph is emergent, i.e. just a consequence of declaring which "jobs" (taken loosely) depend on which artifacts. I've had good experiences with GoCD https://gocd.org https://gocd.org and Concourse https://concourse-ci.org https://concourse-ci.org, the latter being a fresher, younger take on these concepts. I haven't surveyed the landscape recently so there may be other tools that work well.
- candiddevmike 6y agoIn my opinion, microservices are all the rage because they're an easily digestible way for doing rewrites. Everyone hates their legacy monolith written in Java, .NET, Ruby, Python, or PHP, and wants to rewrite it in whatever flavor of the month it is. They get buy in by saying it'll be an incremental rewrite using microservices. Fast forward to six months or a year later, the monolith is still around, features are piling up, 20 microservices have been released, and no one has a flipping clue what does what, what to work on or who to blame. The person who originally sold the microservice concept has left the company for greener pastures ("I architected and deployed microservices at my last job!"), and everyone else is floating their resumes under the crushing weight of staying the course. Proceed with caution.
- hyeomans 6y agoTwo years and counting
- rufius 6y agoI actually worked in an org that took the Tick/Tock model and applied it to rewrites. As a big monolith got too unwieldy, we’d refactor major pieces out into another service. Over time, we’d keep adding a piece of functionality into the new service or rarely, create another service. The idea wasn’t to proliferate a million services to monitor but rather to use it as an opportunity to stand up a new Citadel service that encapsulated some related functionality. It’s worked well but it requires planning and discipline. At another level of scale, some functionality got rewritten a second time into yet another citadel.
- will_pseudonym 6y ago> a new Citadel service > yet another citadel What do you mean by citadel in these contexts? I've never encountered that terminology before.
- boo-ga-ga 6y agoProbably this https://m.signalvnoise.com/the-majestic-monolith-can-become-the-citadel/ https://m.signalvnoise.com/the-majestic-monolith-can-become-...
- hendry 6y agoReal life Microservices documentary https://www.youtube.com/watch?v=y8OnoxKotPQ https://www.youtube.com/watch?v=y8OnoxKotPQ
- xwdv 6y agoLast August Delaware rolled out the laws for new Protected Series LLCs. After founding one main LLC for $300, you can then created an unlimited number of LLCs under it, each with their own debts, liabilities and obligations which cannot be enforced against another series, or the original founding LLC as a whole. If one series LLC gets ensnared in a legal dispute, the others can continue operating as usual. You can probably guess where I'm going with this. The idea is a tech company can use this new structure to put each microservice into its own LLC and basically operate as its own company that communicates with others through a rich API and formal company communications. Whats useful about this is you can use it to get around GDPR and other 21st century issues. Microservice LLCs could basically launder data among themselves, buying and selling it, and using creative hollywood style accounting. When a service gets sued for some privacy violation and threatened with a fine, it could shut down and go out of business and be replaced by a new LLC that rises mysteriously from no where. It then becomes increasingly expensive to pursue litigation. Every time you get close to levying a fine or getting justice, the target evaporates and is replaced by entirely new companies with a whole new corporate structure.
- techsin101 6y agothis has to be the craziest i read in 2020, so sudo llc init is going to be a thing soon?
- quickthrower2 6y agoSpeak for yourself pet lover! I’m setting mine up from a terraform file.
- xwdv 6y agoAbsolutely, it would be trivial to create some kind of program that could spin up LLCs on the fly once you have founded the main series.
- wmertens 6y agoOh wow, AFAIK this is basically how AMZN already operates. If they would transition to this setup, there's nothing for regulators to point at for antitrust enforcement.
- chrismsimpson 6y agoLikely a seminal article
- quickthrower2 6y agoI’m saving this article to reread at work a few times. The M word has been mentioned :-)
- revskill 6y agoMonothlics are not good or bad. It's just that monothlic architecture made it easy to add couplings between dependencies, and this is the real problems of software engineering. Loose-coupling is the goal. So to me, microservices made it hard to put coupling between parts of system, so it made system overall easier to maintain, less tech debt.
- nullsense 6y agoI agree with your notions of what the problems are, and what the goals ought to be. Though I think microservices didn't actually make it hard to put coupling between parts of the system. It's the same old story of how everyone is doing Agile wrong. The cargo-cult implementations fail to deliver on the promises because they don't actually follow the principles. "Microservices" often means little more than "not the monolith". It's a pretty low bar. The loosely-coupled property is what is important. If that doesn't hold, then you've almost certainly made things worse. If it holds then you've almost certainly created a path towards making things better.
- shrimpx 6y agoWhat are the problems caused by tight coupling?
- nullsense 6y agoQueues of work that block because of all the dependencies during all parts of the SDLC that increase the lead times, decrease deployment frequency, and can increase the blast radius of failures leading to longer, and more severe outages.
- jacob019 6y agoI love my service based architecture. It's about 10 years old and I can't imagine a better way of separating concerns and keeping a clean, maintainable, and resilient e-commerce operation up and running. I don't have hundreds of services, there are maybe 30. Each service is responsible for a particular domain, and if another service wants access to that domain it must go through the appropriate service. I can't imagine having a single process "monolith" being responsible for so many things, it would be a nightmare. I also can't imagine not enforcing separation of concerns via services, code would be duplicated everywhere. I was thinking the other day about the cost of serialization, which isn't too bad. If it is too bad then you're probably sending too much data over the wire, and should do more processing on the remote end of the wire. I think some people go overboard with the micro part of microservices. If there isn't a clear separation of domain, then there should probably just be one service. You can still modularize the code as much as you want within the service.
- lxe 6y agoSounds like you've hit the SOA sweet-spot.
- lilbobbytables 6y agoDo you get the benefits of separation by using separate data stores as well, or are most fed from a common database?
- jacob019 6y agoMost data is stored in the same database server instance. There is a database access service that with seperate modules for each database, by convention each of these modules has exclusive access to it's tables with the exception of a special module that performs cross-database joins, needed for performance with some reporting tasks. Other services don't talk directly to the database, they go through the database service. Some services use their own data stores in a variety of formats.
- simonw 6y agoHow big is your team? What kind of process do you use to on-board new engineers to the point that they can make good design decisions within your architecture?
- cubano 6y agoDid you seriously mention CORBA as a API interface method in 2020? As a corporate contractor who had to use CORBA back in the iInterface days of Win95, just the mention of it spins me into a semi-PTSD fit. Please...REST is a solid, simple, and powerful transport method and let's maybe do without CORBA moving forward.
- Guthur 6y agoIt's simply Conway's law more explicitly materialised. Essentially the organisation wants to hire more engineers because that makes it all go faster, right? But then you can't have all those engineers in one team so you create lots of small teams. This means you'll get lots of small systems. You then want to make them "autonomous" so they all get their own repo and cicd. And then before you know it you're in micro service "nirvana". There is also that org were one guy read a blog post about Netflix once and then...
- cweill 6y agoThis is the most correct answer here. "Your products will mirror your organizational structure." See "Building Microservices: Designing Fine-Grained Systems" by Sam Newman, chapter 10
- tacitusarc 6y agoThis is a debate I will never understand. The position of the monolithics is "you should have one thing". Well, that's obviously wrong, if you're doing anything even slightly complex. The position of the microservice people is "you should have more than one thing", but it gets pretty fuzzy after that. It's so poorly defined it's not useful. How about have enough things such that all your codebases remain at a size where you don't dread digging into even the one that you're most prolifically incompetent coworker has gone to town on? Enough things that when not very critical things fail, it doesn't matter very much. But only that many things. If you need to update more than one thing when you want to add a simple feature, if small (to medium) changes propagate across multiple codebases, well, ya done messed up. If you're one of the people believing monoliths are The Way, you're making a bizarre bet, because there's N potential pieces you can have to create a complex system, and you're saying the most optimal is N == 1. What are the odds of that? Sometimes, maybe. But mostly N will be like 7 or something. Occasionally 1000. Occasionally 2. But usually 7. Or something. This seems really obvious to me.
- brain5ide 6y agoIt's not actually saying that. It's saying, that the N is not really relevant technologically enough to be worth evaluating every damn time. It maybe relevant organizationally to fit your org chart. Also, putting a barrier to creating a new service is a feature of monolith. Other types of partitionings are still there. They just might require some insight into existing arch.
- 4140tm 6y agoI find it bizarre how many arguments on the topic are just of the type "microservices are the cure" / "microservices are cancer" - no reflection on specific domains and context. It's very much like the case with unit tests. What is a unit? How small is micro? These two questions on their own are subject of debates of religious proportions.
- ryanbrunner 6y ago> If you're one of the people believing monoliths are The Way, you're making a bizarre bet, because there's N potential pieces you can have to create a complex system, and you're saying the most optimal is N == 1. What are the odds of that? Sometimes, maybe. But mostly N will be like 7 or something. Occasionally 1000. Occasionally 2. But usually 7. Or something. "Pieces" is doing some heavy lifting here. You're assuming that isolated parts of a system need to be seperately developed and deployed systems, which absolutely doesn't need to be true. Seperate parts of a system can be modules, namespaces, libraries, or any number of different solutions to decouple code and create domain contexts and boundaries. I've never met anyone who prefers to use monoliths that would also say "just let everything call everything else, you don't need any structure". That doesn't necessarily mean that that the only acceptable boundary is an HTTP interface.
- silentsea90 6y agoIf I may join in this game of hubris, I have discovered a pattern as well. Report 1: Milk is amazing for you. Report 2: We were wrong, milk is terrible for you Report 3: Milk may have some benefits Report n: Whew, milk is good within bounds Repeat for chocolate, microservices, meditation, religion, wine, nuclear power
- frequentnapper 6y agocounter-examples: heroin, opiates, rat poison, etc.
- 8note 6y agoThose have all reached the good within bounds, no?
- sesm 6y agoHow about smoking? Report 1: Smoking is good because it makes you more masculine. Report 2: Smoking is bad because it causes lung cancer. Report N: Smoking is still bad.
- Dirlewanger 6y agoAlso, wine. No amount of alcohol over any time period has been found to be beneficial, it was just feelgood crap wineries/breweries told us.
- silentsea90 6y agoPossible, but the generally held belief is that a bit of red wine is good for you
- frequentnapper 6y agoAlcohol can be beneficial in terms of it being a "social glue" whether you personally believe it or not. Within reason is fine, and won't make you an alcoholic. So that doesn't fit the counter examples.
- peterwwillis 6y agoMicroservices are popular because managing large teams is a pain in the ass and creating a small team to spin off some new business case is really easy to manage. You get budget, you create the new team, if it sucks, reorganize or fire the team (and offload the services to other teams). I'm telling you, it's all Conway's Law. We literally just don't want to think about the design in a complex way, so we make tiny little apps and then hand-wave the complexity away. I've watched software architects get red in the face when you ask them how they're managing dependencies and testing for 100s of interdependent services changing all the time, because they literally don't want to stop and figure it out. Microservices are just a giant cop-out so somebody can push some shit into production without thinking of the 80% maintenance cost.
- hsbauauvhabzb 6y agoCan someone explain where a system would fit which breaks off large chunks (auth, profile, shopping cart, PDF generation) but doesn’t go as granular as per-function services? Aside from PDF generation (which is always a mess) I can’t see why anyone would think a more granular approach would be better in basically anything that’s not amazon and ebay.
- gizzlon 6y agoThe idea that the "Project model" and "Deployment model" could look totally different is and interesting one. Can't remember seeing that in practice, other than many libraries combined into a "monolith". Anyone have other examples?
- maest 6y agoRelated: Any good recommendations for resources regarding architecting service-based systems?
- branko_d 6y agoI think this summarizes the article: > There is no substitute to the effortful application of cognitive power to a problem.
- rytrix 6y agoSometimes a monolith is the way to go and sometimes microservices are the way to go; it really all depends on a number of factors.
- diegoperini 6y agoHonest question: Is there a type-safe way of communicating across microservices without duplicating verification logic, writing extra layers for the protocol overhead and conceding to more cognitive load during programming?
- vbsteven 6y agoIf I go the microservices route I usually implement a service-client library for any services I expect to be called internally often. This way service A which needs to communicate with service B can just pull service-client-B into the project and call its methods. Most verification/errorhandling/transport is abstracted away in the service-client library. This library usually also includes model/dto classes. This approach only works well if most of your services are using the same language (and sometimes framework).
- lxe 6y agoMy take: 1. "I have this application, but I need to process batch jobs / run heavy workflows / do ML etc..." -- definitely split into multiple services. 2. "I have this application, but this one feature I want to add is implemented really well as a library/app that's not easy to integrate" -- same spirit as 1 -- also a good candidate for SOA 3. "I have an application for end users, and various internal tools that differ in their quality/security/privacy requirements" -- probably a good reason to build those separately (but not a necessity) 4. "I have an application and it doesn't scale well with my growth" -- this is one of the most common reason behind implementing microservice architecture, but I think it requires a lot more thought than just 'yup, let's obviously do horizontally scalable microservices' 5' "Our monolith is slow to compile, run and test" -- careful with this one: it's probably easier in the majority of cases to fix your tests, builds, and runtime speeds, than start splitting up your (probably already very complex) application into services 6. "Our org is split into multiple functional groups and we want to move independently" -- not a good reason for SOA/microservices: you're increasing eng complexity and reducing org collaboration and risking a lot of work overlap. 7. "Microservices have been successful in [Big Company]" -- not a good reason. The benefits/trade-offs are usually fairly unique to each organization and require careful "inward" thinking instead of following trends 8. "One microservice per business function is a good pattern and we're going to mandate it" -- terrible idea. Top-down eng culture mandates prevent better solutions from even being considered. Don't do this at your company.