If you follow eCommerce and CMS platforms then you’ve heard of a buzzed-about technology approach over and over again…headless.
Headless Commerce
Headless CMS
Headless Architectures
Headless Systems
|
||
|
||
|
||
|
Then add in all the individual websites for each hotel, their restaurant websites, and other related websites that all need individual management and you get a better picture of the overall architectural need.
WordPress backend
We start with a Multi-Site WordPress setup for the backend since it is a tried and true Content Management System that has powered a majority of the web for nearly 20 years.
Multiple sites can be managed under one platform allowing for macro and micro management suited for large teams.
Users find it comfortable comfortable and familiar to manage content.
We set it up with simplicity and modularity in mind for as much frontend flexibility as possible.
Elasticache/Redis caching middle layer
These datastores offer ultra-fast data retrieval for the frontend.
They are much faster and more reliable than APIs from WordPress servers or other 3rd parties.
If there are problems with the backend servers, data is safely stored here and the the frontend is undisturbed.
We can easily change format/schema of data here to support frontend needs without requiring updates in the backend.
Ruby on Rails frontend
A robust, fast and easy to work with MVC framework.
We design and build the frontend with curated/branded modularity in mind.
Frontend developers can work independently from backend developers.
With our approach you get the benefits of the headless approach while mitigating or eliminating the drawbacks.
Should you consider headless?
If your brand has a diverse array of offerings that don’t neatly fit into one system, you may want to consider a headless or hybrid headless approach.
You can find the services that best fit your individual needs and your development teams can work independently with modern build systems that can deliver highly performant results.