Liferay's Architecture: The beginning of a blog series

Hey guys,

As you have already heard we have done quite a few symposiums during October, starting with the one in San Francisco, followed by Germany and finishing with Spain. And by the way, if you live in Italy and haven't had a chance to go to any of them, don't miss out the opportunity to attend the Liferay Italy Symposium this Friday. You will have an opportunity to meet many people and attend some of the most acclaimed talks done at the other symposiums.

Speaking of which, I have received lots of positive feedback about my presentation about Liferay's Architecture (Thanks so much!) so that has encouraged me to try to reach the wider audience of all of you reading Liferay's blog. This will also give me an opportunity to get to the last set of slides that I didn't have time to cover during the symposiums.

Because there is a lot of content, I'm not going to do one blog entry, but rather a series of them. Most probably one per slide in my presentation, so I can explain each slide properly. In this blog entry I'm just going to show the first slide which actually shows a diagram of Liferay's architecture which I use also as an index of my whole presentation. Here it is:

I will cover each of the elements that can be seen in this diagram in more detail in future blog posts, but here are a few important things to note:

  • For a product as large as Liferay there are many ways to represent its architecture. The perspective that I've chosen for this diagram is one that highlights its layered architecture since I think it is one of the greatest aspect of Liferay.
  • It also highlights how flexible Liferay is in terms of accessing external systems as well as being accessed by all sorts of external "clients" from regular desktops to third party apps going through mobile apps and browsers.
  • How Liferay is buzzword compliant with terms such as SOA, WOA, ... even since before the terms existed ;)
  • How Liferay includes many transversal frameworks that are used inside Liferay but also made available for applications built on top of it.

That's it for now, since I want to try and keep each entry short. I'd love to hear your feedback regarding what you are most interested on regarding Liferay's architecture. Next time I'll dig in more detail into the services layer.

Write a blogpost too!

Write a deep dive into how you use Liferay projects in your technology stack. Or let people know useful tips and tricks for a particular functionality. The Liferay community needs you!

Login or Create an account