Creating an Enterprise Frontend Library in 2018
summary
Argues that an enterprise frontend must be durable and interoperable, so the company builds Clay component library to implement the Lexicon Experience Language and uses Web Components plus Closure templates for server and client rendering on a Java stack. Gives concrete tradeoffs: need for server-side rendering, documentation, avoiding premature abstractions, and the decision criteria that forced a custom library rather than swapping React/Angular. Shares outcomes and implementation details.
AI-written summary · about
chapters (12)
- 0:00Intro
- 4:07Enterprise Software
- 8:29Why Enterprise
- 15:01Waiting for a Plane
- 16:14Building our own library
- 16:31What we built
- 17:18Understand your needs
- 18:25Premature abstractions
- 19:13Understand your problem
- 19:30Hype
- 20:14Documentation
- 20:46Code
related talks
44mMicro Frontend: the microservice puzzle extended to frontend
35mFrontend Architecture: Multi-format Components in Action
17mJS In The Enterprise - Lessons Learnt
56mThe Web, Its Frameworks and Its Standards: Deconstruct to (Re?)Construct
44mApplications instead of libraries: Micro frontends implemented through module federation
46mMicro Frontend: the microservice puzzle extended to frontend
01h 13mArchitecting complex JavaScript setups for large scale enterprise projects
51mBuilding Better Components — A Journey to a More Resilient Frontend