After reviewing the pros and cons of monolithic and microservices architectures in part one of this series, it’s time to talk about whether or not you should switch to a microservices architecture.
If you’ve been around in the web development industry, chances are that you’ve heard about microservices architecture and its benefits, such as enabling independent and heterogeneous services to be built by independent teams that can scale differently.
You’ve likely heard of Secure Sockets Layer (SSL) and Transport Layer Security (TLS).
Despite its benefits, adopting DevOps is hard, and many companies struggle to make the transition.
Have you ever wondered what version of PHP your website is running? Or had some really specific question about how PHP is configured and what is enabled/disabled on your site?
What makes a website ‘secure’ can vary, depending on who you’re talking to.
When a web page scrolls, that’s a DOM event. I can find out how far a window has scrolled at any time with window.scrollY.
One of the unique job responsibilities of a front-end developer is to make the sites we build work “acceptably” across the browsers the project has decided to support.
If you’ve ever had to manage servers that are in a traditional data center, you know how difficult and time consuming it can be.
I’m sure plenty of folks know this, but like literally anything else in the world, plenty of folks don’t.
There is so much to know about making websites fast. It’s rather incredible.
So you’ve built your clients a website! That’s awesome.