|
|
|
|
|
by colbyfayock
2103 days ago
|
|
i think there's varying levels of complexity to the different solutions available jamstack or not Jamstack, the complexity might be maintaining different services, such as a headless cms and the front end. the output though is static files that you can dump into static hosting pretty easily on the other hand, you might have a serverful solution thats all in one stack. you run into other complexities with that like having to worry moreso about scaling and managing that server for traffic there are tradeoffs between the 2. jamstack isn't a perfect solution but it has a lot of benefits. it's also relatively young in it's architectural lifecycle, so i would imagine a lot of these pain points to be worked out as it matures the book tries to get into both the good and the challenging |
|