This is THE best explanation of enterprise v. solution architecture I've ever seen. Period.
@JesperLowgren Жыл бұрын
Thank you Marjorie !!
@wizardmaster66397 ай бұрын
Agreed this was a nice way to explain them. A few of my thoughts on why these things have become confusing for some people and yes there are people to blame. An Enterprise Solution - is a System of Systems with common and shared resources and capabilities between the systems - While a stand-alone System/Solution has its own architecture when integrated into an Enterprise, it needs to adhere to the EA principles and use the common features, data, and the technical competence of the Enterprise. The KEY to success of the EA is that it is MODELED properly, implemented intelligently with the right vision in mind that supports future growth as well as answering the right questions for the present needs. We can talk about this a lot, I might start writing a book on the subject - Often people confuse architecting and solutions engineering or architecture with disciplines such as Infrastructure Engineering or Network Engineering (You can 100% blame the HR marketing people who want to be "innovative" to the detriment of finding the right candidates for jobs. Therefore confusing the situation. Not every position is an Architect or an Engineer - There are a ton of positions that should be called Practitioner/SME/Technician - but they are called names like Technical Engineer/Architect to make them sound "trendy" Furthermore, the position description does not match the title). At the end of the day - You can think that the EA is a FAST, large, comfortable, easy-to-drive 18-wheeler that accommodates/replaces your sedan, SUV, Truck, Minivan, and even sports car by integrating them all into one and it offers the one chassis, engine, exhaust system, entertainment package, seat for adult and kids, etc... you got the point while considering the costs, and practicality of its use and operation. I hope it makes sense to you, it does to me because I have been a system Engineer and EA for the past 30 years - If you want to know more - let me know. Unfortunately, I do not have a channel right now - but perhaps in the future where I can help and share.
@TampaCEO Жыл бұрын
"Solutions architecture without enterprise architecture creates silos by focusing only on business requirements.” - Absolutely one of the most brilliant statements I've ever heard. You summed it up perfectly. Unfortunately I've experienced numerous companies whose focus was always on the solutions and never the enterprise. This happens in construction in poorer countries. There is no "central planning" or "zoning laws". Instead, each person focuses in the IMMEDIATE GOAL of building their their personal home or dwelling. This results in cities without proper roads, running water or sewer, electricity, zoning laws, etc. Just look at any of the Favelas in Brazil as an example of poor enterprise planning. This perfectly describes many companies and their IT Infrastructures.
@sianharding Жыл бұрын
Thank you, that analogy was very helpful. I now understand the difference between the two.
@wizardmaster66397 ай бұрын
EA is not cheap - Achieving it and different levels of it require $$, communication, and planning, and it can take a long time to achieve the goals you set (the Target State) - Those countries that do a poor job on their "systems" also are affected by instability, sanctions, lack of resources, levels of education, bribery, and corruption - We cannot look at every country and how they manage themselves from the lens of how we do things in the USA or more advanced countries with $$ and advanced technologies - Wars often cause those situations in many places where instability is in the forefront of everyone's mind and when they are in a position of power corruption creeps - anyways - it is a long story :)
@JesperLowgren4 ай бұрын
Thank you!!
@mixerman1078 Жыл бұрын
I borrowed your framework to explain this difference to some of our trainees. The only change I made, was the order. I prefer to always start with the business perspective. And I put Invisible in quotes, because you could argue that in a digital transformation paradigm this is no longer the case. As Gartner said - already many years ago - "There is no business and IT; IT is the business"... Thanks for sharing!
@JesperLowgren Жыл бұрын
Hi Paul, thanks for your feedback! 😁
@simonwallace699 Жыл бұрын
This is excellent Jesper. You've broken it down into real, practical deliverables rather than the usual wishy-washy mumbo-jumbo I often get from Architects.
@JesperLowgren Жыл бұрын
Thank you Simon Wallace !!
@JohnTube2K Жыл бұрын
Watching this as someone who does EA and SA work. This is a very good video.
@JesperLowgren Жыл бұрын
Thank you !!
@ProfileRNP11 ай бұрын
Dear Content Owner - Big "Thank You" for taking the time and putting the "effort", "energy" to bring the value in this industry via this video. Your video is highly enriching and bringing the passion with the depth to THRIVE ... ....
@Aradhyafouzde43 ай бұрын
I am changing my slides for a cto presentation... awesome explanation
@bladerunner34711 ай бұрын
As always, your explanations are easy to grasp in a subject that can be difficult to understand.
@JesperLowgren11 ай бұрын
Thank you Robert 😁!!
@Rich_H_19722 жыл бұрын
Another great video Jesper! Really succinct and easy to understand. Thanks again!
@ftate6 ай бұрын
Absolutely terrific description. Thank you!
@JesperLowgren5 ай бұрын
Thank you Frank, much appreciated !!
@chemsss8582 Жыл бұрын
So much information in 15mins! Excellent video
@JesperLowgren Жыл бұрын
Thank you Chemsss much appreciated!
@clixerz48442 жыл бұрын
Thank you, I'm delighted
@appstratum9747 Жыл бұрын
An excellent talk. Actually, because this talk is so well thought through it achieves an outstanding level of clarity. It's really quite phenomenal. I don't think I've seen anybody sum up the relationships between Solution and Enterprise Architecture (and their various components) with anything like this level of brevity. First rate.
@JesperLowgren Жыл бұрын
Thank you for that feedback 😁😁😁!
@demigim93172 жыл бұрын
A splendid job! I commend you for your thorough work.
@oriolgarciallurdaАй бұрын
This video is golden
@JesperLowgrenАй бұрын
Thank you !!
@thelettera90412 жыл бұрын
Another excellent video -- thank you!
@KgosiMotlhabi6 күн бұрын
This is brilliant
@JesperLowgren6 күн бұрын
Thank you !! 😁
@brainskool62502 жыл бұрын
Excellent Keep up the good work.
@Steph-jazzАй бұрын
Excellent !
@JesperLowgrenАй бұрын
Thank you !!
@hamiasmai086 ай бұрын
Thanks for this. I need to prepare for for my next role which I feel it is related to this. I might need a coach.
@hamiasmai086 ай бұрын
Also may I know which resource is this? I plan to invest in a training
@tejinder905 ай бұрын
Very Well Explained. Thanks
@calinmarian25538 ай бұрын
Thanks for this great explanation
@JesperLowgren8 ай бұрын
Thank you Calin !! 😁
@bartwybouw46577 ай бұрын
Well, I just figured out what I am going to be watching in the coming weeks ;-)
@hbadrixyz11 ай бұрын
Thanks, that's really so generous and well presented keep up please
@JesperLowgren11 ай бұрын
Thank you Houssam !!
@victorsonde4 ай бұрын
Great explanation. Love it 👍
@kelechijames55772 жыл бұрын
Thanks it was very helpful for me
@daves40264 ай бұрын
awesome video thanks for sharing
@JesperLowgren4 ай бұрын
Thank you!!
@bajanforu Жыл бұрын
Very well explained, thanks Jesper!!
@JesperLowgren Жыл бұрын
Thank you Shekhar !!
@Detriza2 жыл бұрын
It's a pleasure to listen to you
@lehung-up8jv5 ай бұрын
So great video, thank you so so much
@willbabik4042 жыл бұрын
Thanks for the useful information
@imlameasf81672 жыл бұрын
Useful information
@CaponordRevHappy5 ай бұрын
Superb tutorial, thank you.
@EthantheSomethingStudent2 жыл бұрын
Thanks for the review
@kev_gacha50072 жыл бұрын
Exactly right! Keep it up.
@FayçalK-q2x4 ай бұрын
excellent
@omerg3626 Жыл бұрын
Hi on track 6:28 you have an Terror on the Diagram on top left side in the Header. The Letter e is missing in the Second Word. You should Name IT conceptual architecture.
@kayalskettle4063 Жыл бұрын
Awesome video , thank you !
@JesperLowgren Жыл бұрын
My pleasure Kayals!
@kev_gacha50072 жыл бұрын
Beautiful I like your style.
@bushairthayyil19464 ай бұрын
Good explanation
@JesperLowgren4 ай бұрын
Thank you !!
@mcupatriots41132 жыл бұрын
💙💙💙💙 team work = dream work work hard everyday baby this your time .....
@user-wo8on8jd7r2 жыл бұрын
Wonderful review
@7UMUT72 жыл бұрын
Very good
@dollajitt2 жыл бұрын
Everything is excellent
@deleted_user1122 жыл бұрын
Excellent, a lot of new
@tazerwyd2 жыл бұрын
That's a good point. Worthy
@bigboiidevin11152 жыл бұрын
Astounding
@toshyamg9 ай бұрын
Great content 👌 👏
@JesperLowgren9 ай бұрын
Thank you !!
@jewgenijmoldawski33066 ай бұрын
Very cool!
@JesperLowgren6 ай бұрын
Thank you!
@brainskool62502 жыл бұрын
I support him
@nbaopposite34922 жыл бұрын
It helped me a lot
@7UMUT72 жыл бұрын
Helps a lot
@camdencrum1502 жыл бұрын
Amazing as always
@alanjones981810 ай бұрын
Thank you.
@JesperLowgren10 ай бұрын
And thank you !!😁
@BrandonsToyReviewsgaming2 жыл бұрын
Appreciated I like
@clixerz48442 жыл бұрын
A well-developed theme!
@BlueSniper2 жыл бұрын
Like the REVIEW
@DavidHernandez-ur8pl Жыл бұрын
thanks, bravo
@JesperLowgren Жыл бұрын
Thank you David!
@pedrokarandeniya16210 ай бұрын
👌
@JesperLowgren10 ай бұрын
Thank you !! 😁
@waveefn10792 жыл бұрын
Awesome
@NishaUchil7 ай бұрын
Subscribed!
@JesperLowgren7 ай бұрын
Thank you!!
@BlueSniper2 жыл бұрын
Recommend 100%
@chris89492 жыл бұрын
Just great! Thx a lot..;-)
@JesperLowgren2 жыл бұрын
Thank you Chris !!
@chris89492 жыл бұрын
Seriously, most Consultants still fail exactly inbetween, so this was a great picture to start from.. ;-)
@JesperLowgren2 жыл бұрын
@@chris8949 Thank you!
@kidkrupar44712 жыл бұрын
Great EA
@clumpsy66912 жыл бұрын
Just harmony
@Rodrigo-of6lb4 ай бұрын
Masterful, do you think it possible to ask me to share the presentation
@JesperLowgren4 ай бұрын
Please share it !! 😁
@louh67872 жыл бұрын
🔥🔥DEFF🔥🔥
@lamarisd2 жыл бұрын
This is great
@ashishprabhune40592 жыл бұрын
I like this country
@onurcnasjsj85482 жыл бұрын
Nice EA
@xyzguy52362 жыл бұрын
❤️❤️❤️❤️
@bigboiidevin11152 жыл бұрын
5 stars
@ileakhot95632 жыл бұрын
It's priceless
@SpxxkyHighlights2 жыл бұрын
wow
@YoInflated2 жыл бұрын
🔥🔥🔥
@mustafakara82162 жыл бұрын
More videos
@kraloflegend37452 жыл бұрын
Stable
@epictetus8028 Жыл бұрын
Nice video, but you should really reference the book you took all of this from.
@JesperLowgren Жыл бұрын
Hi Epictetus, I did make reference in the video description to the author of the framework, Svyatoslav Kotusev. But you are right, I should have made a reference to it in the vide itself. My apologies.
@gextreme23819 ай бұрын
What's the difference? They all "borrow" each other's stuff...For that matter most of it just writes itself based on what a product does. Think not? The included AWS Reference Architecture is just a diagram of what the product does. Hardly "architecture"... This overall job is one giant fleecing, hats off to a whole group of well paid people who mostly cc: everyone their borrowed goods and call it work. kudos.
@gdahlm6 ай бұрын
ATMs don't use transactions and don't support rollback, it uses compensating actions. I get that this flawed analogy is as old as DTC itself, but at an architect level we need to move on, it has never been 'true'. We are now in a cloud dominated, distributed computing world and need to pay attention when an application shouldn't try to provide strong transactional consistency.
@CheaterVelocity2 жыл бұрын
Like
@MinekEzQMАй бұрын
Horrible video. Audio is slowed down just to get the upload be longer than 10 mins. Clearly can be heard from 1:45 on
@JesperLowgrenАй бұрын
I have absolutely NO idea what you are talking about 😄.
@IntrovertedE Жыл бұрын
i feel this is missing/ignoring the business process layer in solution architecture as well as HR/org changes and business roles. you cannot ignore that stuff if you want a proper solution. architecture has a certain arrogance to it pretending that only IT exists and matters.
@2307vineyard8 ай бұрын
The architecture lacks Solution Cost Estimates, POC, Testing, migration, and DevOps perspectives. Without clear insights into these aspects, none of the architectural artifacts would have meaningful end-to-end context.