Related Posts
Feeling like this
Is anyone here in the UK?
God help us
Additional Posts in Technology/IT Consultants
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
Feeling like this
Is anyone here in the UK?
God help us
This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.
Download the Fishbowl app to unlock all discussions on Fishbowl.
Copy and paste embed code on your site
Send download link to your phone
OR
Scan your QR code to download
Fishbowl app on your mobile
Bowl Leader
So, I’m sorry, i won’t be able to apply this to your software example as I’m more in the infra and cyber space. I’ve been doing this over 20 years and yeah, traditional design patterns are a thing of the past. Cloud, devops etc has been a game changer.
For example, the first thing a lot of companies do when they start moving into the cloud is try to do a 1:1 move. Replicate what they’re doing in their data center in the cloud. Building a perimeter, scaling servers the same as what they have on prem etc. Then they complain that cloud’s more expensive. Completely wrong approach. Companies need to understand that the new perimeter is really about Identities and architecture needs to be agile and scalable to what you’re actually using.
Another example, i honestly just learned about recently is how AWS spins up domains. Basically for say, AWS VDI/workspaces you can spin up AD domains along with it. That’s not something i would normally do as you think about most companies use domains for centralized management. If you think about it the way AWS wants you to think about it, then it totally changes architecture from a traditional IT and cyber standpoint.
So much to learn..
@EY1 The sad part is that the old guard are the ones that are listened to. Selling decade old processes and methodology as new.
I find it painful to see the waste of time, effort and money.
... so are traditional design patterns patterns a thing of the past? Where else would you use the observer pattern, but on a monolith? Otherwise you would just use a service bus. What do you guys think?
I think in overall my point is that the focus on of application design is at a higher level now. It wasn't too long ago that when devs were talking about developing software that needs to do a lot of high speed processing they would immediately talk about having to do it in c++. Today the language probably doesn't matter as much because when we think of high speed we think about distributed processing and auto scaling. So I would readily pick c# or Java over c++ because it's going to be easier to integrate with a modern architecture, even though c++ is usually more performant (when done right). I can make that trade-off because it's the rest of the architecture that's making it a high performance system.
I would think that If traditional models/frameworks are developed around monoliths, then as more companies transition to the cloud and take up micro services/decoupled environment, the frameworks likely need to be adapted as well. In the observer/pub sub example, you could argue that pub sub is a slight variation of observer because it’s similar but adds the msg broker component. So maybe the case is that as we move to the cloud, we will need to look at more variations to the traditional model
I have found that people say they are doing micro services, but have a bunch of API endpoints being called by a monolith.
Some try to apply older methodologies and platforms to more modern problems and technologies. People need to understand the problem and the technology before building a solution.
Are the APIs built and deployed independently? If they are, then technically they are microservices.
The APIs are a step in breaking down the monolith. Most companies don’t have the appetite, resources or budget to rip it out right away as a whole