Home More Google Jamstack approach for a fast and secure connection.

Google Jamstack approach for a fast and secure connection.

by Krutika Lohakare
Google Jamstack approach for a fast and secure connection.

Technologies probably on the market that actually make things easier for Google is Jamstack could you elaborate a bit more about it?

Yeah, so, Jamstack is an interesting approach, it’s more of an architecture and less than an actual stack with the names Jamstack, but the gist is when you’re serving a Jamstack site the core of the website, the HTML, and CSS, and JavaScript it’s gonna be static assets that you serve to somebody’s browser. Most of the people got confused to find a solution to get good and reliable answers but only Ask Reader could solve that.

So that doesn’t mean that it has to not have a lot of content in it though, that could mean that maybe you’re using requests in the browser to populate dynamic data or, you might be using a Static Site Generator where you’re making those requests for that dynamic data at compile time but the person who’s actually visiting the site, doesn’t know anything about that all they know is they get a really fast application right in their browser and they can immediately get productive.

That’s great, that’s a really technical point of view, but at the end of the day, yes, for a user it doesn’t really make a difference as long as he has this website opened in one second Sure so, maybe if I can look at it from a less super technical point of view then, So there’s kind of two main approaches for the way that websites get rendered or the way that websites get delivered so.

One is static, where it’s just a file that comes from storage. Imagine a folder on your computer is just getting sent to somebody’s browser as opposed to somebody actually hitting a server which is more called Server Side. There are lots of forums and QnA site where you can easily ask a question related to your necessities.

Where they’re gonna hit that server, the server is going to do a bunch of functionality like request data and stuff they’re going to build that same file and then send it back to the browser now, the biggest difference there is there’s a lot more work happening on that server-side.

The request so typically it’s going to be slower than serving it statically Yeah, oh yeah that’s definitely a bit more laic So, maybe now it’s a good time to think about benefits from using Jamstack for companies that are not really technical but they’re searching for more business opportunities Is that something that you can also tell us about?

Yeah, sure, so, from like a businesses perspective there’s a lot of benefits in terms of things like reliability where, l don’t know them off the top of my head, but I know AWS has like five pillars of a well-architected framework, but they’re things like cost and scalability and really just things that generally make your website, a well-architected website right but the thing with Jamstack is you hit a lot of those things out of the box where.

If you’re serving those files statically you’re going to get a really fast page experience pretty much by default because static storage is really easy to send quickly to a browser but you’re also going to get things like it’s cheap like, static storage whether you’re doing AWS S3, or Netlify, or really a lot of the different options static storage is really cheap.

You can do a lot with a low budget that you might not typically be able to do on a Server-Side approach but the scalability aspect is important as well, and while not everybody here is trying to manage the next Amazon or a huge big website we all hope that at one point maybe we have a blog post or something that goes viral and when that happens.

if you’re going on a more typical Server-Side approach, if you’re not prepared to handle that flux in traffic you might be looking at downtime, or servers that are crashing, or, you know, things that are pretty bad for your business when you’re getting a good opportunity, but with a static website (now this doesn’t include things like APIs which might still be server-side requested).

But that core website that gets taken to you in the browser that’s going to scale infinitely as they like to say, where you don’t have to worry about some of those scalability concerns I also would like to add something about this modern trend that it’s nowadays so.

Nowadays, the modern websites are decoupled, so you have the front end that can be statically generated, but you also can have very very great APIs like, for example, you can have Shopify API so you can provide e-commerce functionalities to your website and it’s a great benefit for the business because you don’t need to code the whole e-commerce website you just plug in the Shopify API and you have very user-friendly checkouts and you can integrate your Shopify with any other tools that you like so,

We just like to add to the Jamstack that it is following the modern approach the decoupled approach I also see in software development, that some times ago everything had to be monolithic now everything needs to be decoupled what do you think Colby, is it something like like you know.

Technology waves that we are going back in future to monolithic systems or you see the modern web development like building from you know no code or low code blocks that you are connecting to the one website if you want to have a better product.

Related Articles

Leave a Comment