I have created a new article your query, Developers Courses in 2022, https://sourcedcode.com/blog/aem/aem-developers-courses-2022-that-really-helped-me. I hope this helps.

Hi Subasish, in my opinion, when moving to AEM Fullstack, in the very beginning, you will be spending a lot more time understanding the infrastructure of how an AEM website is built; this means understanding components, templates, pages, etc… You’ll spend a lot of time learning about the conventional configuration structures of how AEM ties everything together. Once this is understood, you might work more on Front-end (Micro-services, HTML, CSS, JavaScript) or Back-end (I would say, importing data from a third party, workflows, and data structures in the JCR). Moving away from AEM, the lost knowledge would be the AEM infrasture, which cannot be used, But from the years of AEM Experience that you obtained, you will be able to take all your FE experiences to make ReactJS, Angular, VueJS experiences. For the backend, to me, AEM is somewhat like the Spring.io Framework. So you can be a RESTFUL-API developer writing in Java Backend with the Spring.io framework. You can imagine if you transition away from AEM, you will be working as a Spring.io Framework full-stack web developer.

BUT, AEM is just starting to become more and more popular, and now is the right time to start.

==================

“Adobe Experience Cloud is used by 75% of Fortune 100 companies”

Out of curiosity, I did a little digging…

What I found is interesting.

AEM is used in pretty much most industries, but these are the biggest:

– Pharmaceutical
– Health
– Telecommunication
– Consumer Retail
– Financial Services

Now, there are some BIG companies like Apple and Amazon that use AEM.

But they tend to use it for internal communications or microsites.

I estimate that there are 1,200 +/- US-based companies currently using AEM right now.

What I find most interesting is this represents a small portion of a much bigger pie.

Let me explain…

Adobe over the last few years has started to focus on medium to large size companies.

Think companies with 1,500 employees and 500 million in revenue.

And with “75% of the Fortune 100” already sold to. There isn’t much more “selling” room left.

So consider this enterprise market tapped out.

You also see that over the last few years Adobe’s strategy is to move AEM to the cloud, which they call AEM as a Cloud Service.

And with their latest acquisitions of Marketo and Magento, it gives Adobe a solid footprint into those medium to large size companies.

And given that footprint, it just makes sense that Adobe is going to have a much easier time selling AEM as a Cloud Service and their other enterprise products.
Lastly, Adobe changed its licensing from a cost-per-instance to a usage-based model supported by Adobe managed services and AEM as a Cloud Service.

So all-in-all Adobe’s future with AEM is just getting started.

You’re welcome!

Hi Tina,

I don’t think it will be too rough to context switch from ASP.NET/C#. It will just be new syntax from the Sightly HTL & Java Backend API.

I would recommend you take some courses on pluralsight.com as this website will provide you 20hrs + on AEM training videos on how to get started. You can try to use my promo code here as a free trail – https://www.pluralsight.com/pricing/free-trial?clickid=UlKR0sXprxyIUYvSowSpp0KmUkD2ufQeNTFuTo0&irgwc=1&mpid=3205385&aid=7010a000001xAKZAA2&utm_medium=digital_affiliate&utm_campaign=3205385&utm_source=impactradius

I’ve got an ASP.NET/C#/ASP.NET MVC background with HTML5/CSS/JavaScript, so entering into the Java/Apache arena and trying to get my head around a new IDE and understanding how to build out components feels intimidating.

Do you have any suggestions for someone who has lived mostly in the Microsoft side of things?

Thank you again.