Solution vs Enterprise Architecture Tutorial 

Thank you Marjorie !!

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.

Thank you, that analogy was very helpful. I now understand the difference between the two.

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 :)

Thank you!!

Thank you Chemsss much appreciated!

Thank you Frank, much appreciated !!

Thank you Simon Wallace !!

Hi Paul, thanks for your feedback! 😁

Thank you !!

Thank you Shekhar !!

My pleasure Kayals!

Thank you Robert 😁!!

Thank you Houssam !!

Thank you Calin !! 😁

Thank you!

Thank you!!

And thank you !!😁

Thank you !!

Thank you David!

Thank you !!

Thank you Chris !!

Seriously, most Consultants still fail exactly inbetween, so this was a great picture to start from.. ;-)

@@chris8949 Thank you!

Thank you for that feedback 😁😁😁!

Thank you!!

Also may I know which resource is this? I plan to invest in a training

Thank you !! 😁

Please share it !! 😁

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.

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.

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.