/
Headless Architechture
Headless Architechture
Why it is being used in EshopBox ?
Both frontend and backend are seperated from each other
can deploy front-end and back-end on independent servers.
Audience
All software development engineers
Reading Material
Link | Level |
---|---|
Beginner | |
Intermediate | |
Intermediate / Expert |
Dos & Don’ts
Dos
Always use when you want to seperate front-end and backend both.
Recommended to use for multiple delivery platfporms.
Don’ts
, multiple selections available,
Related content
Building Sequence Diagram
Building Sequence Diagram
Read with this
App Engine
App Engine
Read with this
REST API Creation (Cloud Endpoints Framework)
REST API Creation (Cloud Endpoints Framework)
Read with this
HLD: Domain modeling and component diagram
HLD: Domain modeling and component diagram
Read with this
Return-sync infrastructure.
Return-sync infrastructure.
More like this
What is Eshopbox?
What is Eshopbox?
More like this