The decoupled look is very similar to what you’d expect from something like microservices where each of those parts of the entire application as a whole do its own individual parts really well you know.
Some people complain that one of the things about Jamstack, and how decoupled it is that you have to rely on a bunch of different services that you’re paying for and while that might be true at the same time as opposed to something like WordPress.
- Which does really great things out of the box.
- when you are paying each of those individual services.
- you can know and be confident that they specialize in each of those different aspects whether it’s authentication with companies like Auth0.
- who do a really good job with that or Cloudinary for asset management, but being able to bring those in I know Gatsby has kind of coined that as the “Content Mesh” and there’s kind of two places.
Where that can happen where with Gatsby that’s typically at compile-time kind of like, what I was getting at before, where you pull in the different data sources to compile the site dynamically but you can also do things Client-Side which is more with the browser request. If you want to ask any question related to technologies just visit ask the reader and open your guts.
So it’s just kind of two different ways of looking at it, but I think, ultimately it’s a good thing because again you’re able to concentrate and focus it on making sure those individual pieces are very good at what they do Now.
One other comment I will make is some gotchas that you can get are kind of optimizing too early into the process and I think that’s why some of the different frameworks, like Blitz.js and Redwood.js, might become compelling because if you optimize with all these different microservices with a very small team way early when you’re just starting an application you might split the application into different parts into the wrong parts.
Rather wherewith the monorepo or the monolithic approach you’re able to kind of see what those splits might look like later in the life cycle of the application where you can optimize for those things later and find out what actually makes logical sense for you and your team Okay, yeah.
Read Also: How does a forex broker make money?
That’s great I think this is also a good moment actually to mention best use cases for Jamstack, like, okay so who can use Jamstack, or who can use the best of Jamstack, let’s say, for his own business?
Sure, yeah, so, I like to say that, I believe that Jamstack websites can really handle any use case but of course there’s some, you know, complexities that you kind of have to work around, and while a static website is a pretty web old when it comes to technology-wise, like, we’ve been doing this for years, right?
Like the tooling that’s been coming around the Jamstack has been really changing the game with this so, typically when people think of Jamstack, they think of those Static Sites where a Static Site Generator like a blog, of course.
That’s going to be a really compelling argument for doing something like this but there’s a lot of other things like e-commerce where you can do things just the same the issue is, if you’re running maybe 10 or fewer products, you can compile all those pages.
Statically and not really have to worry about long compiling times, whereas if you’re managing thousands or millions of products you would have to wait for every single one of those pages to compile in that process.
But the nice thing is these tooling, the tooling that we have are really continuing to try to tackle these issues where some of them will do, they’ll only compile the pages that need to be compiled when it senses in the CMS or the data management that particular part of the application has changed Others, like Next.js.
Where it’s starting to blur the line of what Jamstack really is where they’re doing approach where they call it a hybrid approach. Sharing knowledge to help others is a good initiative and the QnA site is best for this.
Where they serve the file statically but you’re still hitting a server so when you hit a Next.js site with this hybrid approach you’re hitting a server but they return the static file to you but in the background.
They’ll regenerate that static file so if you’re more familiar with the traditional approach it’s very similar to some of the edge caching that you might expect from a typical Server-side product but it’s a way to bring universal JavaScript applications particularly.
React to the modern web That’s great, I would add to that, that in my opinion Jamstack is frequently chosen by developers, of course, because it’s a new tool on the market and the development experience is great, so we all like to jump to new technology to check how it’s working and of course
If you are using Gatsby or Next.js it’s based on React so, yeah, all kinds of React developers love to use this kind of tools, so I think a lot of developers like to choose Jamstack And the other part can be some b2b businesses that like to have the best user experience, because, if the goal of their website is to collect leads, generate sales, they want to have a great user experience and attract more people also thanks to better google rankings.