<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by Bryan Soltis on Medium]]></title>
        <description><![CDATA[Stories by Bryan Soltis on Medium]]></description>
        <link>https://medium.com/@bryan_soltis?source=rss-7b17752b4823------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/0*21EKlgu0dVuVnpMz.jpg</url>
            <title>Stories by Bryan Soltis on Medium</title>
            <link>https://medium.com/@bryan_soltis?source=rss-7b17752b4823------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Tue, 17 Nov 2026 22:01:36 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@bryan_soltis/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com/" rel="hub"/>
        <item>
            <title><![CDATA[2 Decades of Web Forms. Now, I’m Learning MVC.]]></title>
            <link>https://medium.com/hackernoon/2-decades-of-web-forms-now-im-learning-mvc-88c51ee97c50?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/88c51ee97c50</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[developer]]></category>
            <category><![CDATA[mvc]]></category>
            <category><![CDATA[web-forms]]></category>
            <category><![CDATA[online-form]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Wed, 28 Nov 2018 15:56:40 GMT</pubDate>
            <atom:updated>2018-11-28T17:34:05.684Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*1ikmLYVFqKipfhYSPOtXHA.jpeg" /></figure><p>This is a true story.</p><p>For starters, I’m not an MVC expert.</p><p>This isn’t a blog with all the answers someone transitioning to MVC is looking for.</p><p>I, like you, have searched the interwebs for such a publication, only to find that everything is pretty much task-oriented, focused on migrating a specific site or function to MVC. I found many blogs about why MVC is better, all the amazing benefits it brings to developers and marketers a like, and why Web Forms should(?) be buried deep in the ground, never to be seen again.</p><p>What I really wanted to find was someone who knew Web Forms and was starting to work with MVC. I wanted to know their process, challenges, and thoughts on the framework and how easily their skills related. So, I’m making an article from my point of view. A well-seasoned Web Forms developer who’s been thrust into the world of MVC. Sure, I’ve developed lots of sites using .NET. Over 19 years’ worth, actually. But that was using Web Forms, which is officially the newest inhabitant of the Island of Misfit toys. While I created many (self-proclaimed) awesome solutions with Microsoft’s legacy framework, MVC was never in the mix.</p><p>Until you’re the technical evangelist for a content management system that declares MVC as their primary focus. And then the fun begins.</p><p><a href="https://www.kentico.com/product/mvc-transition-guide">Learn more about Kentico’s new MVC support</a></p><p>When I first started seriously looking at MVC over 2 years ago, I knew it was going to take some time to master. When so much of the platform goes against nearly 20 years of Web Forms thinking, I found it was sometimes tough to fully grasp core concepts. While MVC’s approach to routing, requests, and architecture aren’t completely foreign ideas, they still contradicted many of the techniques and designs I had built a career on.</p><p>Of course, there were a lot of similarities, which helped things a lot. Both frameworks have the concept of compartmentalized functionality and the same request/response capabilities. But under the hood, things are drastically different, and I’ve spent the better part of the past 24 months trying to make sense of it all.</p><p>Why has it taken so long? Well, when you’re a technical evangelist, you don’t really work on “real” projects anymore. Sure, I make a ton of POCs and enough demos to kill a donkey. But unless you work on a production-level, enterprise application, you never get the trial-by-fire experience for learning a new technology. Because of that, I’ve had to work at a different pace to get my MVC skills up to speed, using training, boilerplates, and a lot of trial-and-error.</p><p>Through all that, here are some of biggest takeaways thus far.</p><p><strong>DISCLAIMER</strong></p><p>No donkeys were harmed in the making of this article.</p><h3><strong>Architecture</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*d6HZLPABaaasFHv3d03ILg.jpeg" /></figure><p>Right from the start, the architectural differences between Web Forms and MVC are glaringly obvious. Long gone are code-behinds and designer files. Oh, and Web Forms page lifecycle? That’s outta here, too. Instead, there are Controllers, Views, Models, and helper classes for all your favorite code. The structure is clean, minimal, and easy to manage. Most of the sample sites set up this concept very well, and it’s pretty much the first thing every MVC training course will cover. Understanding the folder structure and naming conventions is key, and luckily this wasn’t too big of a challenge.</p><p>Over the years, I had tried to adopt good practices when it came to structuring and storing my code (for reusability), so the idea of specialized classes and folders for each MVC component was a natural concept. There were some parts that still confused me, like where’s the best place for interfaces and connectors, when to use partial/full views, and how in the heck you code the posting of a form. These were concepts that I was well versed in Web Forms, so transitioning them to MVC took a little while to get. But, with enough practice, anything is possible.</p><p><strong>Key takeaways</strong></p><ul><li>MVC projects have a unique structure that allows the application to fulfill requests and match controllers to views automatically.</li><li>Having a proper project structure is key to having the site function properly, as well as portability of the code to other applications.</li><li>Microsoft has basically mandated that MVC is the future and the long-term support of Web Forms is not a guarantee. This means transitioning to MVC is an essential self-preservation move developers need to make if they like having jobs and money and food.</li></ul><p><strong>Concepts to grasp</strong></p><ul><li>View inheritance is a key concept. Understanding how and when to include the “master” layout will help you code your sites faster, and make one-off pages easier to develop.</li><li>By default, MVC sites are all about presentation. If you want to capture data, you often need to add in components to accept the responses, validate them, and process them correctly.</li><li>With MVC, developer tooling is geared to NuGet and package management. This means learning those systems is key to working with the framework as nearly everything will be brought in as a separate library.</li></ul><h3>Understanding requests</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*bLYySTSZRJvUXB21fWv8-Q.jpeg" /></figure><p>As I mentioned above, requests in MVC work significantly different than in Web Forms. While both MVC and Web Forms handle requests at the same stage of the life-cycle, getting the web server to interpret (and accept) the post is another challenge. Back in ye old days of Web Forms, you have the trusty Request object (technically, this is there in MVC, but the framework abstracts some of the details away for you). This canyon mule is capable of sending every bit of information about the user to and from the server. You can quickly pull out the values that you need and shove the rest of it into memory for a rainy day.</p><p>With MVC, things are much different. Because MVC is about modularity and light-weight applications, you have to build up every bit of the response from scratch. This means your controllers have to have the correct Action attributes so the application knows what to call, your models need to be updated to hold the entered data, and you need to ensure you properly validate all the responses. I found this to be a bit of a challenge in my learning, as I wasn’t used to having to create everything manually. After a lot of experimenting (and using some online form templates), I was able to grasp the concept and learn how to properly receive posted data into my MVC apps.</p><p><strong>Key takeaways</strong></p><ul><li>With MVC, your forms will be created from the ground up. While this is more work, you can ensure your application is as light-weight as possible.</li><li>Everything in MVC is about making something happen in a controller. Ensuring your Actions and results are properly configured are essential to your application handling requests properly.</li></ul><p><strong>Concepts to grasp</strong></p><ul><li>When you first start with MVC, you generally have a pretty basic model. When it comes to forms, you’re going to have to update your models / view models with the appropriate properties to handle your data. This may go against your initial thinking of how data is handled, so be sure you understand exactly how it will function in your scenario.</li><li>Requests go hand-in-hand with routing, so make sure your routes are properly defined.</li></ul><h3>Layout controls</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Jnh2-4fdd-3g9dljieE3rw.jpeg" /></figure><p>Because of the minimalist approach to things, MVC is all about complete control over the layout. Compare this to Web Forms “Let’s drag a control from the toolbox and have it wire everything up” functionality, and you’ll quickly see some pretty big differences. Where Web Forms is all about pre-wiring existing components, MVC is more about starting from nothing and only adding what you need.</p><p>Now, throughout all my WF development, I was never really a fan of the drag-and-drop controls, opting to build my own layouts from scratch. I did, however, always use server-side controls to build my designs, as this gave me access to the controls from the code-behind. This was pretty much the way every developer did it and it was a good model for web development for nearly 20 years.</p><p>While Web Forms provides the simplicity of design, it comes with a whole lot of overhead. All those server controls have ViewState, event handler capability, and auto-generated ids that run on for miles. While some controls like repeaters and grids gave the option to design on a per-item basis, the overall design was very elementary, and very limiting.</p><p>With MVC, the tables have been completely turned, and all the control lies with the developer and designers. Designers have full control over the layout, allowing them to use many of the built-in HTML Helpers to layout their page, or standard HTML input controls for even cleaner markup. Per-item layouts can be handled with Display templates easily, ensuring no pre-manufactured table layout will get injected into your otherwise flawless responsive site. This means only the essential elements are added to the View, without any of the 800-pound gorilla-Web Form baggage.</p><p><strong>Key takeaways</strong></p><ul><li>MVC is aimed at simplicity. This means that developers are free to add only the elements and controls they need. This reduces the overall application and page size and drastically improves performance.</li><li>Layouts can be created with simple HTML elements, HTML Helpers, or a combination of both. This gives designers free-reign to implement their design without fighting the pre-generated output of the application.</li></ul><p><strong>Concepts to grasp</strong></p><ul><li>MVC is a minimalist approach to development. This means any design requirements have to be included manually by the developer. Things like supporting JavaScript, validators, and 3rd party libraries need to be included on the appropriate views if the layout depends on them.</li><li>Giving designers free roam over the presentation is a very powerful ability. You’ll need to work with them closely so that the application can implement their layouts correctly and still function properly.</li></ul><h3>Helpful stuff</h3><p>If you want to know the resources I used, here’s a list. There’s certainly a lot more stuff out there, but this should give you a good starting point.</p><ul><li><a href="https://www.asp.net/mvc/overview">ASP.NET MVC Documentation</a></li><li><a href="https://docs.microsoft.com/en-us/aspnet/#pivot=aspnet">Microsoft ASP.NET Documentation</a></li><li><a href="https://www.pluralsight.com/paths/mvc5">Pluralsight ASP.NET MVC 5 Training Path</a></li><li><a href="https://docs.microsoft.com/en-us/nuget/">Microsoft NuGet documentation</a></li><li><a href="https://docs.kentico.com/k12/developing-websites/mvc-development-overview">Kentico 12 MVC documentation</a></li></ul><h3>Wrapping up</h3><p>This article was about telling you the things I wish I knew before I started transitioning to MVC. There’s certainly more to the process than what I covered, however, these are some the important areas I had questions about. If you’re thinking about changing your skillset over to MVC, I recommend you start your studying now! Whether it’s online learning, books or peeking over the cubicle at the MVC-guru beside you, the main point is to get started. Time will most likely prove to be the best teacher as you work through your projects and gain more experience. It may seem like a big hill to climb but trust me, you can do it. In the end, it’s all web development and part of the developer gig.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88c51ee97c50" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/2-decades-of-web-forms-now-im-learning-mvc-88c51ee97c50">2 Decades of Web Forms. Now, I’m Learning MVC.</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Developers deserve endorsement deals, too]]></title>
            <link>https://medium.com/hackernoon/developers-deserve-endorsement-deals-too-602f048771c?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/602f048771c</guid>
            <category><![CDATA[development]]></category>
            <category><![CDATA[professional-development]]></category>
            <category><![CDATA[compensation]]></category>
            <category><![CDATA[testimonials]]></category>
            <category><![CDATA[endorsement-deals]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Thu, 17 May 2018 20:15:41 GMT</pubDate>
            <atom:updated>2018-05-17T23:52:00.488Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*W9ogoen4Ypf32wIL8-cnHQ.jpeg" /></figure><p>They cut the lights.</p><p>That 90s stadium jam blares over the intercom.</p><p>The office mascot starts break-dancing in the conference room.</p><p>“And now…..leading today’s daily standup……..it’s the backend developer in the corner with all those bobbleheads and weird sci-fi characters on his desk!!!!”</p><p>That’s what it’s like when you go to work, right? Well, it should be.</p><p>I was talking with a good friend recently and he mentioned that developers were a lot like athletes. We have marketable skills, amazing potential, and it seems we are in very high demand. Maybe we don’t appear on as many cereal boxes and highlight reels, but the glory is there all the same.</p><p>It seems everywhere you read, companies are scrambling to fill their positions. It’s nothing new, really. For the last few decades, software has shaped our daily lives, and someone needs to be around to write it. But lately, it seems as if the crunch is really hitting the industry hard.</p><p>So, guess what that makes you? A superstar! A finely tuned athlete, capable of leading any team to victory! A champion! Don’t believe me? Here’s why…</p><h3>More alley, less oops</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*Jt8vEZ07xF4y9klJcKQ-1Q.jpeg" /></figure><p>First and foremost, developers have skills. If you’ve been developing ten months or ten years, you have some amazing abilities that most people don’t possess. You may be the master of the latest technologies out there like Azure Functions or Vue.js. Or you may have vast experience in legacy technologies like ASP, .NET 1.1, or Silverlight. But, you are always capable of learning more, including the next new thing.</p><p>Some are better than others. But that doesn’t mean every developer is not skilled in some way. Try sitting down your dentist in front of your laptop and get them to understand a block of code. Maybe give him that funny gas first, just to see what happens.</p><p>When I was first developing, I was amazed at a developer at my company that “knew 12 programming languages”. Wha-what??? That’s amazing! Now, I can look at just about any code file and at least understand what’s going on. It’s not like I know every platform there. I just can interpret the logic. That’s the skill I’m talking about. Developing isn’t knowing a specific platform or language. It’s understanding how applications work, how to logically process information, and how to bury your Easter Eggs <em>just</em> deep enough for people to find them without being obvious.</p><p>But, just like any pro athlete, you need to keep your skills honed. Practice them. Attend a conference on something new. Review your work. Open something up from 10 years ago and shriek in horror at your egregious lack of garbage collection. The point is, make sure you keep using your skills and testing yourself. It’s the only way you’ll make the Varsity team and stay off the bench.</p><h3>It’s not whether you get knocked down, it’s whether you get back up</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*QOIVsqw1W9xdDtrdwyrumg.jpeg" /></figure><p>Hands up for everyone who was NOT 7+ feet tall and picked first for everything? Nearly all of you? OK, like me, you probably needed some coaching at some point in your life. There’s no shame in that! A great coach and trainer can sculpt nearly any lump of potatoes into a mountain (see… Easter Eggs). Great athletes learn from others who played their position in the past. The best developers work with mentors to hone their abilities, learn best practices, and understand that just about everything is iterative. The one truth is, the best athletes and developers are the hungriest ones that are never satisfied. They always want to better themselves and never stop learning.</p><p>You may be on the cutting edge of everything, but you still learned how to develop from someone who did it before you. And you learned a ton of stuff along the way. Maybe it was a professor in school or a guy sitting in the cube next to you. Or maybe you were just thrown into a classic ASP and SQL 6.5 application when the developer who knew it left. Developers often get a trial by fire, and the coaching and mentoring are what help you not get burned.</p><p>If you’re just starting out, find a good mentor. Someone who cares that you know how things should be done, and will work with you to make sure they are. If you’ve been in the game a while, help out the new recruits. You’ll be amazed at what they can accomplish, and inspired by their creativity.</p><h3>Her palms are sweaty</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*t6GJdcHStt1b_tioTpbzrg.jpeg" /></figure><p>Seconds left on the clock.</p><p>Impossible odds.</p><p>The roar of the crowd is deafening.</p><p>This is what every athlete dreams about. The pressure. The world on their shoulders. The chance for glory.</p><p>It’s showtime.</p><p>OK, maybe for developers the fanfare is a bit less exciting. But, I KNOW you’ve been pushed up against a deadline that seemed impossible to hit. You’ve had to work unspoken hours fixing a bug. Maybe you’ve spent the night in front of an Exchange 5.5 server that had to be rebuilt before the office came back in the in the morning. (Jet databases… shudder…..)</p><p>And you got it done.</p><p>That’s what developers do. We make the impossible possible. We make the improbable probable. We make the simple overly complicated by over architecting things.</p><p>We overcome hurdles on a daily basis. Our whole job is problem solving, and we’re damn good at it. It’s easy to score when there are no defenders in front you. True superstars leap, juke, and Ickey Shuffle their way to score, no matter the odds.</p><p>As a developer, you will be asked to “just make it work.” You may not know how, but you’ll find a way. When it’s crunch time, developers can do amazing things. Pressure can bring out true greatness in a person.</p><h3>I coulda’ been a contender!</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1000/1*xWkEq7AHIzuj6rKLpg7JPg.jpeg" /></figure><p>An athlete in their prime is a valuable commodity. When a superstar is looking to make a change, teams will fumble all over themselves, rushing for the chance to convince them to join their organization. They represent success, victory, and some sweet endorsement deals. And they can turn an entire organization around just by being on the field.</p><p>Developers are just as valuable. Skilled, talented programmers can build just about anything. And companies know it. Don’t believe me? Just go update your LinkedIn profile to say “interested” and watch the flood of recruitment emails pour in.</p><p>It’s easy for a developer to get carried away and dream of being the GOAT. But they’re not wrong. That aspiration is what drives innovation. It’s what fuels creativity. And it’s what strives developers to better themselves and always be improving.</p><p>So, should you test the waters of free agency? I have no idea. But, I can tell you that longevity is what wins championships. If you want to build a legacy, you have to put in the time to get there. You’ll always be offered more (ah, the early 2000’s were amazing like that), but knowing when to make a move will be critical to your success.</p><p>Always weigh your options. Do your research on any new organization. Make sure you can read their playbook and fit into their formations. And make sure they respect you for the awesome athlete you are. The game is long and you need to be able make it to the end on top.</p><p>Now get ready. It’s almost time for kickoff….</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=602f048771c" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/developers-deserve-endorsement-deals-too-602f048771c">Developers deserve endorsement deals, too</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Balancing Exposure in a Public Role]]></title>
            <link>https://medium.com/hackernoon/balancing-exposure-in-a-public-role-2d0bc977705a?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/2d0bc977705a</guid>
            <category><![CDATA[developer-relations]]></category>
            <category><![CDATA[social-media]]></category>
            <category><![CDATA[social-media-marketing]]></category>
            <category><![CDATA[evangelism]]></category>
            <category><![CDATA[community-engagement]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Fri, 27 Apr 2018 18:31:33 GMT</pubDate>
            <atom:updated>2018-04-28T16:06:19.183Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*zlPtOqVHiRRrXwM-HandYA.jpeg" /></figure><p>Over the past 10 years, I have done this a lot:</p><p><em>“Hi, my name is Bryan Soltis.”</em></p><p>[…some interesting presentation…]</p><p><em>“So, there you have it! I hope you enjoyed the presentation and feel free to reach out to me in all these different ways.”</em></p><p>[List of various social media accounts]</p><p>No matter the audience or topic, the format is relatively the same. Introduce myself, tell them about some awesome technology or concept, and then let them know how they can get in touch later.</p><p>You see, I’m a technical evangelist, and I LOVE presenting. It’s my favorite part of the job, actually. Well, that and wearing shorts every day. It’s a very public role, and one that puts me (and my contact information) in front of a lot of people on a regular basis. To better connect with others, you have to be accessible, and social media is one of the go to routes.</p><p>But, what if you don’t love social media? Seems counter intuitive, right? To be honest, I can’t say I’m the biggest fan. I’m a very social person, and I love talking and interacting with people. I don’t, however, necessarily love to chronicle every aspect of my life for anyone to view.</p><p><em>The two most shocking things I tell people I meet is that I’m a grandfather and I don’t have Facebook.</em></p><p>Before I get too deep into it, I should let you know I have had several social media accounts over the years. It’s hard not to be a part of the 2 Billion on Facebook, and I was no different. I’ve also had Twitter, LinkedIn, MySpace, and a few others. I used them all for years and regularly learned what Kevin was eating for dinner and how many deadlifts Mark did in CrossFit. (….so many CrossFit updates….). I found that, over time, I had less interest in the personal aspect of social media and exposure.</p><p>So, my career is about connecting with everyone. I want people to want to talk/listen to me and understand who I am as a person. My personal stance is to be a bit more reserved. So, how do I balance these conflicting ideologies?</p><p><em>Compartmentalizing and boundaries.</em></p><h3><strong>Dividing your focus</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*U_Caldp8pPk-6EbvtKEiHA.jpeg" /><figcaption>Pizza is acceptable on any social media platform</figcaption></figure><p>From the beginning, I separated my contacts and content between professional and personal. Specifically, I deemed LinkedIn as my main professional channel, and FaceBook for my friends and family. Twitter hovered somewhere in between, with a mixture of both types of contacts and posts, but leaning more towards professional. I guarded my contact lists closely, striving to keep the types segregated as much as possible. For the most part, I was successful for a few years.</p><p>As time went on, I found myself changing my outlook some. My career as an evangelist required a social media presence, so I knew that was never going away. I was comfortable with that and enjoyed using the platforms. On the personal side, though, things were changing. I found myself hesitant to give all my personal information freely to some platform, with nothing in return (unless you count an onslaught of “targeted” ads). Glaring security risks aside, I found that purely personal platforms didn’t interest or engage me, and decided to let that piece go.</p><p>The ability to separate the two channels from the beginning made this a much easier process than it could have been. Up to that date, I had reserved my personal social media only for the ones closest to me. I was able to remove that, without losing the connections. I had a large professional network established, and keeping those accounts helped me keep those contacts.</p><h3><strong>Defining boundaries</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*fyiRAjdJTLdn4K1hWp-Yvw.png" /><figcaption>[INSERT TEAM NAME]’s home pitch</figcaption></figure><p>With so much of my role being on how effective I am at reaching a community, understanding the boundaries of social media was a critical component. I wanted people to know me and be open, without broadcasting my entire life. I wanted them to connect with me and understand my message, but I don’t need a ton of Happy Birthday posts every year.</p><p>Defining the limits of how I use social media meant deciding what information I was willing to post, and what I reserved for a chat with a friend on a bar stool. I wanted to show my personal side in my messages, but only to a certain point. It’s a hard chord to strike when you’re in a public role, but it’s possible to do and still be comfortable with your limits.</p><p>How did I decide between Professional and Personal? If we met at a conference, event, exchanged forum posts, worked together, or any other career-centric setting, the contact was Professional. Personal was pretty much everyone else: family, friends, that guy from that party that wore the same shirt as me. This meant I often didn’t accept friend invites from co-workers, as I wanted to try and keep a work/life balance as much as possible.</p><p>Making the distinction early on can help, as you will naturally use each channel for the intended purpose. This will help you decide where your limits are and fit the platforms to meet your needs.</p><h3><strong>Where to post</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*9HKjwoOVexnarocnVBzN2A.jpeg" /><figcaption>Probably one of the most boring neighborhoods for trick-or-treating</figcaption></figure><p>When it comes to my social media, I have classifications: <em>Acceptable</em>, <em>On the fence</em>, and <em>No thanks</em>. Now, these are just my opinions, and help me fit social media into the boundaries I defined. It’s in no way meant to be a knock on anyone else on those platforms, as I know I’m certainly in the minority with some of these.</p><p><strong>Acceptable <br></strong>These are platforms I use regularly and think they are essential to connecting with others on a professional (and sometimes personal) level. Mine are naturally technical-focused, but the overall theme is being reachable from my professional audience.</p><ul><li>Personal blog</li><li>Twitter</li><li>LinkedIn</li><li>GitHub</li><li>Stack Overflow</li><li>Company directory(?)</li><li>Work-related platforms</li><li>Speaker directories</li><li>Microsoft MVP directory</li></ul><p><strong>On the fence <br></strong>These platforms I’m not sure about. In some ways, I think they’re OK. They may provide a good medium for certain people, however, may expose too much for others. It really depends on their use and what the person is trying to get out of them. I use them, but sparingly and to fill a gap in communication, where needed.</p><ul><li>Disqus</li><li>Gaming platforms</li><li>Skype</li><li>Slack</li><li>Google+</li><li>ICQ(Yes, I still remember my #!)</li></ul><p><strong>No thanks<br></strong>These platforms are almost purely personal (in my opinion). I see them as avenues people express themselves and their thoughts, to anyone who will listen. I certainly know that businesses do use them to reach people, however, I see that as companies trying to capitalize on an already established audience, rather than a platform built specifically for it. I don’t use any of these, as they don’t fit into my boundaries for what I want to share.</p><ul><li>Facebook</li><li>Instagram</li><li>MySpace(?)</li><li>Anything that chronicles / exposes your personal life beyond your boundaries</li></ul><h3>In the end</h3><p>I’m at a point where I found a balance with social media. While I don’t want it to consume every aspect of my life, I’m comfortable (and enjoy) using it to connect with professionals and broadcast my message. That balance helps me share enough about myself with the world, while keeping the personal stuff closer to my chest.</p><p><strong>This means that if you find me on a social media account, feel free to hit me up! I’m there for a reason and would love to connect.</strong></p><p>When you are in a public role, you will always have this challenge. You’ll have to decide how much of yourself you want the world to know, and how much you reserve. It really boils down to how a person wants to be viewed by others, and the channels in which they broadcast that information. In the end, the decision will be unique for everyone.</p><p>Find your balance so you can achieve your goals, while getting the most out of each aspect.</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=2d0bc977705a" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/balancing-exposure-in-a-public-role-2d0bc977705a">Balancing Exposure in a Public Role</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Progressive Web App with a Headless CMS — Part 3]]></title>
            <link>https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/a6bb538084</guid>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[caching]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Wed, 25 Apr 2018 11:37:42 GMT</pubDate>
            <atom:updated>2018-04-26T14:49:12.961Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Exgo3UD4nuQqA2eCujfOoQ.jpeg" /></figure><p><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a><strong> |</strong><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6"><strong> Part 2</strong></a> | Part 3</p><p>Welcome to Part 3! If you’ve haven’t been following this series, I’ve been creating a Progressive Web App (PWA) using a Headless CMS. And the excitement has been unbearable! There’s been SUSPENSE! DRAMA! ACTION! ROMANCE? Yeah, we’ve seen a lot in Part 1 and Part 2, so it’s time to keep the franchise going with the next exciting installment. Grab the Milk Duds.</p><p>In the first 2 articles, I covered the basics of creating a PWA and how to integrate a Headless CMS into the mix. I gave an overview of the PWA architecture, detailed some important components, and showed you how to create a working example. Because PWAs are all about providing a dynamic experience, pulling and displaying content is a pretty big deal. How and when you pull that content is equally important, so I wanted to break down how to cache your content within your app. See? I told you this was going to get even more exhilarating.</p><h3>Why caching?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Ou0WCvYN67oOH82w7h52Wg.jpeg" /></figure><p>If you’ve ever built an application that uses a 3rd party service, you know that it doesn’t happen using magic. There are always API calls back and forth as the systems communicate. This may mean pulling data, validating information, or recording the flavor of latte you just ordered. The point is, that communication can quickly add up as users interact with your app. Learning how to make those calls wisely will help your app run better, and keep corporations from knowing your every move.</p><p>Caching is used all over the place to reduce calls and improve speed. It comes at a cost, however, in that the data you cache must still be valid when you display it. For a lucky few of you, that means you potentially could cache every aspect of your app and get amazing load times. For the rest of us, it’s going to take some planning to determine what makes the most sense. And because there are so many ways to do caching, the selection process can be a daunting one, especially when you find that you will use different techniques depending on the data.</p><p>What is the best solution for your app is entirely up to you. Just keep in mind how big a role caching can (should) play within your PWA to help it run as smooth as possible. It’s all about giving the user a great experience and providing the most relevant content.</p><h3>Caching solutions</h3><p>When it comes to caching, you can leverage a number of existing libraries, or roll your own. If you really like working with lower-level components (or are into Crossfit), knock yourself out and make a sweet new solution (while flipping a tire or something) for your app. If you’re like me, then you may be more inclined to leverage an existing library to do the heavy lifting. Just do your homework and find the solution that fits your needs the best.</p><p>The <strong>Google Offline Cookbook</strong> is a great resource for learning about caching in PWAs. I strongly recommend you check it out to see process workflows, scenarios, and deep dives into how data can move through your application.</p><p><a href="https://developers.google.com/web/fundamentals/instant-and-offline/offline-cookbook/"><strong>Read more about the Google Offline Cookbook</strong></a></p><p>For our Pack and Go demo, we opted for <strong>Workbox</strong>. Workbox is a JS library that provides offline support for PWAs and other applications. Through precaching, Workbox allows you to load aspects of your code quickly from memory, while defining what areas are to be retrieved from external sources and when. What’s even better, it does so with a minimal amount of code and configuration, making implementation a breeze. So, win/win, right?</p><p><a href="https://developers.google.com/web/tools/workbox/"><strong>Read more about Workbox</strong></a></p><h3>Caching strategies</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1014/0*ImTEATVn6oNzMlVL.png" /><figcaption>NetworkFirst process (from the Google Offline Cookbook)</figcaption></figure><p>Those multiple caching methods? Yeah, there’s about a billion of them, depending on your platform, libraries, components, and favorite color. Regardless of type you choose, the main thing to keep in mind with PWAs is the “type” of caching. Here’s a brief overview of the most common options:</p><p><strong>CacheFirst</strong><br>Fetch from the cache. If not available, fetch from the network and update the cache.</p><p><strong>CacheOnly</strong><br>Fetch only from the cache and never from the network.</p><p><strong>NetworkFirst</strong><br>Fetch from the network. If that fails, then fetch from the cache.</p><p><strong>NetworkOnly</strong><br>Fetch only from the network and never from the cache.</p><p><strong>StaleWhileRevalidate</strong><br>Fetch from both. Return from cache if available. If not, return from network and update cache, if successful.</p><p><a href="https://developers.google.com/web/tools/workbox/reference-docs/latest/workbox.strategies"><strong>Read more about Caching Methods</strong></a></p><p>You’ll use some (if not all) at various points of your development, depending on how you structure your data and application. Be sure to read up on each option to understand exactly how the requests will be handled so that your app performs how you want it to.</p><p>In our demo, we had two distinct types of content.</p><p>1. The AppShell (images, styles, headers, etc.)</p><p>2. The points of interest content from Kentico Cloud</p><p>Because our “main” files would rarely change, we opted for the <strong>CacheFirst </strong>option. This would load our <strong>AppShell</strong> and supporting files from cache (after the first load) for a quick display of the interface. Seeing how these files would rarely be modified, this made the most sense and gave us great load times.</p><p>For our POI content, we would be loading these using the <strong>Kentico Cloud API</strong>. Because this information would change often, it made sense that this content would need to be more dynamic. To accommodate this requirement, we went with the <strong>NetworkFirst</strong> strategy. This option allowed the app to always load the most up to date information from our Kentico Cloud project. If the network was down for any reason, we would fall back to the cached version.</p><h3>Service worker</h3><p>Whatever caching option you choose, your journey is certainly going to start with your service worker. Being the <a href="http://marvel.com/universe/Heimdall#axzz5CxRSzyKT"><strong>Heimdal</strong></a> of communication, your service worker will be where you register your caching and determine when it will be invoked. Because your service worker is the proxy between the app and the interwebs, it can intercept every request. It will have access to the cache repository you implement, and make all the components work together. And keep the Frost Giants off the Rainbow Bridge and in their own neighborhood.</p><h3>Caching Pack and Go</h3><p>Now that you have an understanding of caching with PWAs, let me tell you how we implemented it in our Pack and Go sample app. If you have been following the series, you may remember that we had a lot of code in our <strong>service-worker.js</strong> file for defining what files to cache immediately, and when to cache the calls to the Kentico Cloud API. <strong>Workbox</strong> takes care of all that code by wrapping things up in a pre-built library. This makes configuration super simple and clean, while providing the same functionality.</p><p>First, we added the workbox plugin to our <strong>package.json</strong> file.</p><pre>“devDependencies”: {<br>   …<br>   “workbox-webpack-plugin”: “³.0.1”<br>},</pre><p>Next, we registered Workbox within our Node app. In our <strong>webpack.config.js</strong> file, we added a new <strong>const</strong> and reference to the <strong>workbox plugin</strong>. This includes code to cache files that match a set of extensions. This replaces the <strong>AppShell</strong> files definition that used to be in the service worker file in the previous version of the app. <strong>Workbox</strong> also handles versioning of the <strong>AppShell</strong> files.</p><pre>const workboxPlugin = require(‘workbox-webpack-plugin’);</pre><pre>new workboxPlugin.InjectManifest({<br>   swSrc: ‘./src/public/service-worker.js’,<br>   globDirectory: ‘./src/public/’,<br>   globPatterns: [‘**/*.{html,js,css,svg,png,ico,woff,woff2,ttf}’],<br>});</pre><p>In our <strong>serviceworker.js</strong> file, we defined how we would cache calls to the Kentico Cloud API. We registered the specific route to the API, and selected the <strong>networkFirst</strong> option. This code replaces the <strong>addEventListener</strong> code from the previous version of the app. This is a lot simpler, as the registration of the listener is handled by <strong>Workbox</strong>, by default.</p><pre>if (workbox) {<br>   console.log(`Yay! Workbox is loaded 🎉`);<br>   workbox.routing.registerRoute(<br>      /https:\/\/deliver\.kenticocloud\.com\/66ab95de-6599–0018-f141–3c9dc08fe797\/items/,<br>      workbox.strategies.networkFirst()<br>   );<br>   workbox.precaching.precacheAndRoute(self.__precacheManifest || []);<br>} else {<br>   console.log(`Boo! Workbox didn’t load 😬`);<br>}</pre><h3>Testing</h3><p>With <strong>Workbox</strong> registered and configured, you should be ready to test your PWA. For our demo, we launched the site locally and confirmed the site loaded correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*z_0AUbluvUPSgNY8Hun9IA.png" /></figure><p>Viewing the <strong>Chrome Developer Tools</strong>, we could see that <strong>Workbox</strong> was being registered and properly caching the responses.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*Apge6BIUfrtdRetFNv_7QA.png" /></figure><p>We then deployed the site to an Azure App Service and tested it there.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*mr4T-IYRPwbFPpnEa4J68A.png" /></figure><p>If you want to see the live demo, <a href="https://bryansdemopwa1.azurewebsites.net/">check out my site</a>.</p><p>If you want to see the full code, check out the <strong>Kentico Cloud Pack and Go GitHub project</strong>. Be sure to use the <strong>v2-caching</strong> branch for what we covered today. We are continuing to update the project with new features, which we will cover in future articles.</p><p><a href="https://github.com/Kentico/cloud-sample-pwa-app/tree/v2-caching"><strong>View the Kentico Cloud Pack and Go GitHub project</strong></a></p><h3>Wrapping up</h3><p>Building an app that performs great in every situation is a big challenge. You must consider the user’s environment, connection, preferences, and a host of other factors. By leveraging caching in your PWAs, you can ensure your content is loaded quickly and correctly. This will increase user satisfaction, and reduce calls between your systems.</p><p>I also showed you a lot of great capabilities of Kentico Cloud. By using this Headless CMS, you can centralize your content, and leverage a technology-agnostic API to deliver it wherever you need. This helps you build applications the way YOU want to build them, in any language, while still getting a great content management experience for your editors.</p><p><a href="https://kenticocloud.com/"><strong>Learn more about Kentico Cloud</strong></a></p><p>This article wraps up my series on Creating a Progressive Web App with a Headless CMS. I hope you learned a lot about this new and exciting development technique. With it, you can build an amazing user experience for your audience, regardless of their platform.</p><p>For our Pack and Go PWA, we have big plans coming! Look for future blogs on transitioning to Angular, adding searching, and other leveraging device capabilities with your apps. See you next time!</p><p><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a><strong> |</strong><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6"><strong> Part 2</strong></a> | Part 3</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=a6bb538084" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084">Creating a Progressive Web App with a Headless CMS — Part 3</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Progressive Web App with a Headless CMS — Part 2]]></title>
            <link>https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/88ffee198ff6</guid>
            <category><![CDATA[headless-cms]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Wed, 04 Apr 2018 12:12:54 GMT</pubDate>
            <atom:updated>2018-04-26T14:48:46.604Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*omtqPm7skI8ZSHs3ZCxfxg.jpeg" /></figure><p><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a><strong> | </strong>Part 2 | <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084"><strong>Part 3</strong></a></p><p>Hey, welcome back! In <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a> of this series, I introduced you to the Progressive Web App (PWA). I covered what they are, how they function, and how a headless CMS can really add some awesome functionality. In <strong>Part 2</strong>, I’m going to dive into building a PWA and adding some cool features. That means creating the base app, adding the magic, and testing.</p><p>So, let’s get to the good stuff!</p><h3><strong>Recap</strong></h3><p>In <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a>, I mentioned a few services that we’re going to talk about a lot in this series.</p><p><a href="https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/"><strong>Google PWA Tutorial</strong></a><strong><br></strong>This is the “base” app we started with for our demo. It’s a great tutorial and provides a nice foundation for a PWA.</p><p><a href="https://kenticocloud.com/"><strong>Kentico Cloud</strong></a><strong><br></strong>This is the cloud-based CMS we used to power our application. It’s a scalable, flexible CMS with tons of SDKs and sample projects to help you get going quickly.</p><h3>Creating the base app</h3><p>OK, let’s get to creating your app. You can start from scratch, or use one of the many demos available to jumpstart your development. Regardless of the path you take, your app will contain a few key components.</p><p><strong>Application Shell (App Shell)</strong><br> The Application Shell is the base UI for the app. This is what you will load initially to give the user a consistent experience, regardless of their connection and device. This component is often stored in the browser cache the first time the app is loaded, as it will not change very often. You should also include any controls, buttons, or images in the App Shell to help those get loaded quickly, too.</p><p><strong>Service Worker</strong><br> Possibly the most important component, your Service Worker is what will power you PWA with fresh content. When people use a PWA, they will be expecting a rich, responsive experience. Service Workers are how you make that happen. These components are responsible for handling asynchronous events and executing code to update the UI. You have full control over the life-cycle of the script and state management.</p><p><strong>Manifest</strong><br> To have an app-like experience, your PWA needs to tell the browser how to behave. In your manifest file, you’ll define the basics of your application, along with the URL and icons to load. You can even set the orientation, full screen mode, and other environment variables to ensure your content loads exactly how you want.</p><p><strong>The Real Code</strong><br> After you define your AppShell, service worker, and manifest, you need to add the functionality. What I mean by this is the code that fetches your data, updates your layout, and any other features you want to include. It may be a standalone JaveScript file, or a bundle of them. I’m also grouping any external libraries into this mix, in case you are planning on adding some sweet cursor trails to your design.</p><h3>Making the App Shell</h3><p>For our demo, we started with a basic layout of a header, title, and a list of POIs. By using a standard top bar, the PWA would have a familiar and consistent look in the browser and on mobile devices. This basically made up our App Shell, so we kept it as simple as possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*DT9uYLpF35V71L17Knx7pQ.png" /><figcaption>This is the extent of my design skills.</figcaption></figure><p>Also included in the App Shell is the basic layout for our POIs. For this, we use a template to display the elements. Not very exciting, but that’s what 1st versions of an app are for!</p><pre>&lt;main class=”main”&gt;<br> &lt;div class=”card cardTemplate” hidden&gt;<br> &lt;h2 class=”title”&gt;&lt;/h2&gt;<br> &lt;div class=”content”&gt;&lt;/div&gt;<br> &lt;a class=”map-link” target=”_blank” hidden&gt;Open the map&lt;/a&gt;<br> &lt;/div&gt;<br>&lt;/main&gt;</pre><p>We will use this template when we write out POIs to the app after the content is fetched.</p><h3>Adding a Service Worker</h3><p>The next piece to add is the Service Worker. file. You will want to set up your triggers, define your cached information, and configure how the app will function. This can have big impact on how the app behaves, and what makes it more like a native app to mobile users. You and your Service Worker are probably going to spend a lot of time together, so bring it a house warming gift as an ice breaker.</p><p>In our demo, we created a new script to hold the service worker logic. Building off the sample, we added our cache information, list of files we wanted to store, and our event listeners. With this worker, we can capture events as the user interacts with the app, and control how the functionality processes based on the request and/or environment.</p><pre>var dataCacheName = &#39;packAndGoData-v1&#39;;<br> var cacheName = &#39;packAndGoApp-v1&#39;;</pre><pre>var filesToCache = [<br>   &#39;/&#39;,<br>   &#39;/index.html&#39;,<br>   &#39;/main.js&#39;,<br>   &#39;/manifest.json&#39;,<br>   &#39;/styles/fonts/RobotoMedium.eot&#39;,<br>   &#39;/styles/fonts/RobotoMedium.svg&#39;,<br>   &#39;/styles/fonts/RobotoMedium.ttf&#39;,<br>   &#39;/styles/fonts/RobotoMedium.woff&#39;,<br>   &#39;/styles/fonts/RobotoMedium.woff2&#39;,<br>   &#39;/styles/style.css&#39;,<br>   &#39;/assets/images/icon_refresh.svg&#39;|<br> ];</pre><pre>self.addEventListener(&#39;install&#39;, function (e) {<br>   console.log(&#39;[ServiceWorker] Install&#39;);<br>   e.waitUntil(<br>     caches.open(cacheName).then(function (cache) {<br>       console.log(&#39;[ServiceWorker] Caching app shell&#39;);<br>       return cache.addAll(filesToCache);<br>     })<br>   );<br> });</pre><pre>self.addEventListener(&#39;activate&#39;, function (e) {<br>   console.log(&#39;[ServiceWorker] Activate&#39;);<br>   e.waitUntil(<br>     caches.keys().then(function (keyList) {<br>       return Promise.all(keyList.map(function (key) {<br>         if (key !== cacheName &amp;&amp; key !== dataCacheName) {<br>           console.log(&#39;[ServiceWorker] Removing old cache&#39;, key);<br>           return caches.delete(key);<br>         }<br>       }));<br>     })<br>   );<br> <br>   /*<br>    * Fixes a corner case in which the app wasn&#39;t returning the latest data.|<br>    * You can reproduce the corner case by commenting out the line below and<br>    * then doing the following steps: 1) load app for first time so that the<br>    * initial New York City data is shown 2) press the refresh button on the<br>    * app 3) go offline 4) reload the app. You expect to see the newer NYC<br>    * data, but you actually see the initial data. This happens because the<br>    * service worker is not yet activated. The code below essentially lets<br>    * you activate the service worker faster.<br>    */<br>   return self.clients.claim();<br> });</pre><pre>self.addEventListener(&#39;fetch&#39;, function (e) {<br>   console.log(&#39;[Service Worker] Fetch&#39;, e.request.url);<br>   var dataUrl = &#39;https://deliver.kenticocloud.com/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/items&#39;;<br>   if (e.request.url.indexOf(dataUrl) &gt; -1) {<br>     /*<br>      * When the request URL contains dataUrl, the app is asking for fresh<br>      * weather data. In this case, the service worker always goes to the<br>      * network and then caches the response. This is called the &quot;Cache then<br>      * network&quot; strategy:<br>      * <a href="https://jakearchibald.com/2014/offline-cookbook/#cache-then-network">https://jakearchibald.com/2014/offline-cookbook/#cache-then-network</a><br>      */<br>     e.respondWith(<br>       caches.open(dataCacheName).then(function (cache) {<br>         return fetch(e.request).then(function (response) {<br>           cache.put(e.request.url, response.clone());<br>           return response;<br>         })<br>       })<br>     );<br>   } else {<br>     /*<br>      * The app is asking for app shell files. In this scenario the app uses the<br>      * &quot;Cache, falling back to the network&quot; offline strategy:<br>      * <a href="https://jakearchibald.com/2014/offline-cookbook/#cache-falling-back-to-network">https://jakearchibald.com/2014/offline-cookbook/#cache-falling-back-to-network</a><br>      */<br>     e.respondWith(<br>       caches.match(e.request).then(function (response) {<br>         return response || fetch(e.request)<br>       })<br>     );<br>   }<br> });</pre><h3>Integrating Kentico Cloud</h3><p>With the foundation for the app set, you are ready to add the good stuff. If you are going the cloud-based CMS route, this is where you will want to leverage any APIs and SDKs they have available. These will help you quickly integrate the platform into your PWA, ensuring seamless communication between the systems. Chances are, they have several SDK flavors available, so pick one that matches your architecture.</p><p>For our PWA, we selected a <a href="https://github.com/Enngage/KenticoCloudDeliveryTypeScriptSDK"><strong>JavaScript SDK for Kentico Cloud</strong></a>. Because our app would be JavaSscript-centric, this SDK offered the best solution to quickly incorporate into our architecture. By executing a few <strong>npm</strong> commands, we had our SDK installed within our app and ready for programming. This resulted in some new package files for creating our CMS client and retrieving content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*-OcqDdR3mwlAZOsNGFGmrA.png" /></figure><p>You can learn more about the <a href="https://github.com/Enngage/KenticoCloudDeliveryTypeScriptSDK"><strong>Kentico Cloud JavaScript SDK</strong></a>.</p><h3>Adding the content</h3><p>OK, so you’ve just spent all this time learning the architecture, defining your content, and creating your functionality. Now it’s time to make it work! This is where your “ Real Code” comes into play. You will need to connect your app to your CMS, fetch some content, and wire up your service worker to handle the requests.</p><p>For our app, we created a few scripts to hold our functionality. First, we created a <strong>client.js</strong> file to define our CMS client. This file leveraged the JavaScript SDK we integrated into the site, making the client creation a breeze. Because we used Kentico Cloud for the app, this meant defining our project id and creating a new <strong>DeliveryClient</strong> for accessing our content.</p><pre>import { DeliveryClient, DeliveryClientConfig } from &#39;kentico-cloud-delivery-typescript-sdk&#39;;<br> const projectId = &#39;XXXXXXXXXXXXXXXXXXXXXXXXXXXX;<br> const previewApiKey = &quot;&quot;;</pre><pre>const isPreview = () =&gt; {<br>     return previewApiKey !== &quot;&quot;;<br> }</pre><pre>const client = new DeliveryClient(<br>     new DeliveryClientConfig(projectId, [],<br>         {<br>             enablePreviewMode: isPreview(),<br>             previewApiKey: previewApiKey<br>         }<br>     )<br> )</pre><pre>module.exports = {<br>     projectId,<br>     client<br> }</pre><p>Next, we added an <strong>app.js </strong>file for the main functionality. Following the Google PWA Tutorial, we coded how the POI cards would be updated and when.</p><p>Because PWAs leverage cache heavily, we added functionality to check if the POI data had already been retrieved. If so, the app would load that content. Otherwise, we used our Kentico Cloud Delivery client to retrieve the information from our project.</p><pre>const getPointsOfInterest = () =&gt; {</pre><pre>const url = &#39;https://deliver.kenticocloud.com/XXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXXX/items?system.type=point_of_interest&#39;;<br>     if (&#39;caches&#39; in window) {<br>         /*<br>          * Check if the service worker has already cached this data about the Point of interests<br>          * data. If the service worker has the data, then display the cached<br>          * data while the app fetches the latest data.<br>          */<br>         caches.match(url).then(response =&gt;<br>             response &amp;&amp; response<br>                 .json()<br>                 .then(json =&gt; {<br>                     const typedResponse = new BaseResponse(json, response);<br>                     responseMapService<br>                         .mapMultipleResponse(typedResponse, client.config)<br>                         .items.forEach(pointOfInterest =&gt;<br>                             updatePointOfInterestCard(pointOfInterest))<br>                 })<br>         );<br>     }</pre><pre>client.items()<br>         .type(&#39;point_of_interest&#39;)<br>         .get()<br>         .toPromise()<br>         .then(response =&gt;<br>             response.items.forEach(pointOfInterest =&gt; {<br>                 updatePointOfInterestCard(pointOfInterest);<br>             }))<br> }</pre><p>In both cases, we call the <strong>updatePointOfInterestCard</strong> function to update our layout with the content.</p><p>Next, we created our <strong>updatePointOfInterestCard</strong> function to interact with our page elements. We check to make sure the card exists, creating it if needed. Then, we find each element and update the value with the retrieved data. Because we are using an SDK, we leverage some pre-built functions and patterns to help set our content easily.</p><pre>const updatePointOfInterestCard = (data) =&gt; {<br>    const key = data.system.id;<br>    const title = data.title.value;<br>    const content = data.description.value<br>    const latitude = data.latitude__decimal_degrees_ &amp;&amp; data.latitude__decimal_degrees_.value;<br>    const longitude = data.longitude__decimal_degrees_ &amp;&amp; data.longitude__decimal_degrees_.value;</pre><pre>let card = visibleCards[key];</pre><pre>if (!card) {<br>         card = cardTemplate.cloneNode(true);<br>         card.classList.remove(&#39;cardTemplate&#39;);<br>         card.removeAttribute(&#39;hidden&#39;);<br>         container.appendChild(card);<br>         visibleCards[key] = card;<br>     }</pre><pre>card.querySelector(&#39;.title&#39;).textContent = title;<br>     card.querySelector(&#39;.content&#39;).innerHTML = content;</pre><pre>if (latitude &amp;&amp; longitude) {<br>         card.querySelector(&#39;.map-link&#39;).setAttribute(&#39;href&#39;,<br> `http://maps.google.com/?ie=UTF8&amp;hq=&amp;ll=${latitude},${longitude}&amp;z=16`)<br>         card.querySelector(&#39;.map-link&#39;).removeAttribute(&#39;hidden&#39;);<br>     }</pre><pre>if (isLoading) {<br>         loader.setAttribute(&#39;hidden&#39;, true);<br>         isLoading = false;<br>     }<br> };</pre><h3>Configuring the manifest</h3><p>OK, you have your awesome app ready to go. You have your layout, service worker, and functionality all integrated, but you need to get it looking good on all devices. This is where your manifest file comes into play. In this file, you’ll define the experience the user will see, what options will be available to them, and how the app will look on their device.</p><p>In our PWA, we set some basics in our manifest for the title and colors. For the display, we selected <strong>standalone.</strong> This causes the page look like a native app, removing the address bar. Lastly, we defined our icons. Because PWAs can be pinned to user’s home screen, it’s important to include all the sizes that may be used.</p><pre>{<br>   &quot;name&quot;: &quot;Travel app&quot;,<br>   &quot;short_name&quot;: &quot;travelapp&quot;,<br>   &quot;theme_color&quot;: &quot;#1564bf&quot;,<br>   &quot;background_color&quot;: &quot;#e1e2e1&quot;,<br>   &quot;display&quot;: &quot;standalone&quot;,<br>   &quot;Scope&quot;: &quot;/&quot;,<br>   &quot;start_url&quot;: &quot;/&quot;,<br>   &quot;icons&quot;: [<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-36x36.png&quot;,<br>       &quot;sizes&quot;: &quot;36x36&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;0.75&quot;<br>     },<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-48x48.png&quot;,</pre><pre>&quot;sizes&quot;: &quot;48x48&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;1.0&quot;<br>     },<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-72x72.png&quot;,<br>       &quot;sizes&quot;: &quot;72x72&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;1.5&quot;<br>     },<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-96x96.png&quot;,<br>       &quot;sizes&quot;: &quot;96x96&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;2.0&quot;<br>     },<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-144x144.png&quot;,<br>       &quot;sizes&quot;: &quot;144x144&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;3.0&quot;<br>     },<br>     {<br>       &quot;src&quot;: &quot;\/assets\/images\/icons\/android-icon-192x192.png&quot;,<br>       &quot;sizes&quot;: &quot;192x192&quot;,<br>       &quot;type&quot;: &quot;image\/png&quot;,<br>       &quot;density&quot;: &quot;4.0&quot;<br>     }<br>   ],<br>   &quot;splash_pages&quot;: null<br> }</pre><h3>Testing the app</h3><p>At this point, you should be able to test your app. You will want to view it on your computer and your mobile device. You should see a consistent, clean look across the environments. On your phone, it should look very similar to a native app, and enable you to interact with the home screen and any other functionality you added.</p><p>For our demo, I opened the app on my computer and checked the layout.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*PUyf2yc4wTi4hYejv-v_Gg.png" /></figure><p>I then used the Developer Tools to simulate a mobile device. This was to test that the responsive layout properly resized the content.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*w8jolR_U7zFDfuPa6EL8ZA.png" /></figure><p>Next, I deployed the app to an Azure App Service to access the site externally. I opened the app on a mobile device to confirm it displayed properly.</p><p><strong>Tip</strong><br>I had to run the <strong>npm run build-prod</strong> command to create the <strong>dist </strong>folder for the deployment.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*dF0_P3fx2S_doLQ6zJ2eqQ.png" /></figure><p>Because of the <strong>manifest.json</strong> settings, I was able to add the app to the home screen and confirm the icon displayed correctly.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/720/1*99aw6_X0bYJ4ID0ac6aefg.png" /></figure><p>If you want to see the live demo, check out <a href="https://bryansdemopwa1.azurewebsites.net/"><strong>my site</strong></a>. I’ll continue to update this deployment with new features as the blog series continues.</p><h3>Next time</h3><p>Whew, that was a lot of information to type! If you’ve been following along, you’re no doubt as tired as I am and due for a break. In this blog, I covered setting up my base application, adding my service workers and layouts, and caching files and data at various points. After ensuring all my code was in place, I fired up the app and tested it on a variety of devices.</p><p>In future blogs, I will be covering more advanced topics like push notifications, images, and native app features. I’ll keep building on the demo mentioned here, so I hope you enjoy the journey. Until next time, friends!</p><p>If you want to keep track of our PWA demo app, check out our <a href="https://github.com/Kentico/cloud-sample-pwa-app/tree/v1-introduction"><strong>Pack and Go GitHub project</strong></a><strong>.</strong></p><p><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b"><strong>Part 1</strong></a><strong> | </strong>Part 2 | <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084"><strong>Part 3</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=88ffee198ff6" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6">Creating a Progressive Web App with a Headless CMS — Part 2</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Creating a Progressive Web App with a Headless CMS — Part 1]]></title>
            <link>https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/85ede9dba59b</guid>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[pwa]]></category>
            <category><![CDATA[progressive-web-app]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[headless-cms]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Wed, 28 Mar 2018 13:52:35 GMT</pubDate>
            <atom:updated>2018-04-26T14:48:15.449Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*EY8OdQVTZdU05gid39r78Q.jpeg" /></figure><p>Part 1 | <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6"><strong>Part 2</strong></a><strong> | </strong><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084"><strong>Part 3</strong></a></p><p>Think of all the developers you have met.</p><p>Now, limit the list to the ones that like programming for every platform / browser / display.</p><p>Next, trim it down to ones that love to maintain app codebases for multiple ecosystems.</p><p>I’m guessing you’re down to a pretty short list of people at this point.</p><p>The fact of the matter is that it’s a tough job to make something look (and perform) great for every user on every device, without wanting to table-flip a few desks along the way. And it’s not a new problem. Ever since there was the great browser war of the early 2000’s, developers have been fighting every pixel of their design to make sure things loaded properly. Add to that the rise of mobile platforms, and the fight became comically one-sided. A futile war to wage, but one every programmer has been enlisted to join.</p><p>Enter <strong>Progressive Web Apps</strong> (or PWAs “as they are known around my condo”). The brainchild of some very smart Google developers back in 2015, PWAs are designed to deliver an app-like experience to every user, regardless of their platform. Through responsive design and background processes, PWAs allow you to load your UI quickly, then populate your content asynchronously for a seamless, secure experience. And they can do it all without an install on the device.</p><p>With PWAs so focused on loading content smoothly, powering them with a solid content delivery platform is essential. The answer? A headless CMS. These scalable, API-driven services allow you to manage your data in a sleek UI, while cranking out beautifully-curated content to your apps. It’s a win/win for everyone!</p><p>Not convinced? Let me show you how in this first article of a multi-part series.</p><h3>What is a PWA? (Asking for a friend…)</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*sj1d_DnMV3VYh4-2_Zwo9Q.jpeg" /><figcaption>Those are actually phones I’ve collected over the past 10 years.</figcaption></figure><p>A Progressive Web App (PWA) is a streamlined web application that delivers responsive content in a native-app experience. Designed to look great in a browser or on a phone, PWAs are all about giving the user the best experience possible. Built on top of web technologies and libraries, these applications can be quickly coded using standard HTML and JavaScript skills, allowing current web developers to code them easily. By taking advantage of some modern browser capabilities, mobile users can receive background updates, push notifications, and a slew of other device capabilities. No network? No problem! PWAs can use cached data to ensure fast loading, even when you’re in your underground bunker eating canned peaches with no reception. In short, PWAs are about combining the best of web and mobile, into a single, optimized experience.</p><p><a href="https://developers.google.com/web/progressive-web-apps/"><strong>Read more about Progressive Web Apps</strong></a></p><h3>How can a Headless CMS help?</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*lBZqZnbtFGeBskd_4IJMYQ.png" /></figure><p>While PWAs are certainly the star of the show, they’d still be working smoky Las Vegas lounges if wasn’t for some great content. The guy-behind-guy, content delivery is key to making sure the app runs smoothly. This means being able to update information quickly, deliver it lightning-fast, and ensure developers have a robust platform to work with. Headless CMSs are perfect for the job by using all the fantastical aspects of the cloud, coupled with powerful, technology-agnostic APIs.</p><p>With these CMSs, developers are free to code their applications any way they need, and always know their content will be ready to display. Because PWAs are based on working with or without connectivity, tLastly, CMSs offer scalability and the freedom to code in whatever language it says on your business card.</p><p>In our demo, we chose to use Kentico Cloud for our headless CMS. This platform provides a scalable and flexible solution for delivering content to any device or channel.</p><p><a href="https://kenticocloud.com/"><strong>Read more about Kentico Cloud</strong></a></p><h3>Architecting the app</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*loK6XFRHyeufHIpmhLHngw.png" /></figure><p>Having a good plan isn’t just smart, it’s essential. If the first guy to ever make a pizza started with the sauce on the bottom, think of the struggles we’d have to deal with as a civilization. For PWAs, this means knowing what you are going to build, and how you’re going to leverage the technology. You need to decide what parts of the UI you’re going to load first, how you’re going to load your content, and when and where you’re caching information. Because PWAs should give mobile users an app-tastic joyride, you need to think about how you will implement push notifications, updates, and other phone-centric experiences.</p><p>To begin, break down your application into logical sections. From a design standpoint, identify your header and footer areas. These are what you’re going to load first. Think about how you’re going to use your service worker(s) to fetch your content and when. If you’re going down the headless CMS path, check out what SDKs your vendor has. These will greatly simplify your development and let you focus more on your UI.</p><p>For our demo, we started with a travel app, named Pack and Go. The app is designed to tell you all sorts of interesting information about places around you. For the design, we went with a simple header with a refresh button, matching many mobile apps already on your phone. The content would be the points of interests (POI) information, including the name, description, pictures, and coordinates.</p><p>Here’s a basic outline of the app functionality.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/525/1*VNL7U8W9s4u2sGbBTTRSPg.png" /></figure><p>As a base, we used the Google PWA tutorial. It provided a simple interface and functionality, perfect for us to start building our new app.</p><p><a href="https://developers.google.com/web/fundamentals/codelabs/your-first-pwapp/"><strong>Google PWA Tutorial</strong></a></p><h3>Creating the content</h3><p>With the app functionality figured out, you want to start thinking about the content. You may already have yours in an existing site, database, or just floating around in your head. Your next step is to get it into your CMS. Don’t worry, they should have a content management API to help you script the process. But you won’t want to just drop it into the new system. Because headless content management systems are all about omni-channel delivery, you’ll need to spend some time mapping out your content models and structure. You may have some content that is perfect for the web, while other information that is better suited for smart phones and wearables. Mapping your data correctly will be key to getting the most out of the platform.</p><p>For our site, we started with a simple structure for our POIs. A few text and number fields, along with some assets were all that was needed to launch our initial PWA. In later blogs, we’ll build on this model to power our app.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*i4wN-7FsrRM0fRJ-rzu9LA.png" /><figcaption>POI Content Model</figcaption></figure><p>After creating the content model, we added several locations around the Boston area (with my family being from Pittsburgh, not my first choice of sample content). CMS’s allow you to manage content easily, so we leveraged the workflow capabilities to publish some of the POIs, while we continued to work on others.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*VJVuycvVkmZEHXW1YCKcvw.png" /><figcaption>Lots of interesting Boston POIs in content Inventory</figcaption></figure><h3>Next time</h3><p>Well, we’re over 1,000 words at this point and still haven’t shown any code! I’m going to wrap up Part 1 here to get ready for <strong>Part 2</strong>. In the next article, I’ll be diving deep into the code and show you how to integrate your headless CMS, code your PWA to load data, and ensure everything runs smoothly on your devices. See you next time!</p><p>Part 1 | <a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-2-88ffee198ff6"><strong>Part 2</strong></a><strong> | </strong><a href="https://hackernoon.com/creating-a-progressive-web-app-with-a-headless-cms-part-3-a6bb538084"><strong>Part 3</strong></a></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=85ede9dba59b" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/creating-a-progressive-web-app-with-a-headless-cms-part-1-85ede9dba59b">Creating a Progressive Web App with a Headless CMS — Part 1</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[What You Should Expect from Your CMS Vendor When It Comes to GDPR]]></title>
            <link>https://medium.com/hackernoon/what-you-should-expect-from-your-cms-vendor-when-it-comes-to-gdpr-6f1bebe8f3d7?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/6f1bebe8f3d7</guid>
            <category><![CDATA[prepared-for-gdpr]]></category>
            <category><![CDATA[tips]]></category>
            <category><![CDATA[regulation]]></category>
            <category><![CDATA[cms]]></category>
            <category><![CDATA[gdpr]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Mon, 12 Mar 2018 13:58:07 GMT</pubDate>
            <atom:updated>2018-03-12T15:50:45.143Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*74Wkkp3IUZM2bF0R0CXfzg.jpeg" /></figure><p>If you’re running a website, then you certainly have heard of General Data Protection Regulation. GDPR is becoming one of the hottest topics around, as companies try to figure out how to get their applications compliant and avoid paying their lawyer’s power bills for the next few years. CIOs are getting grilled left and right, and developers are being tasked with getting the company’s assets up to date. With many enterprises using a Content Management System(CMS) for their sites, a lot of questions are coming up as to what needs to be done and by whom. In this article, I’ll let you know what you need to look for from your CMS vendor to get your sites on the up and up, and keep your legal fees down.</p><p>GDPR is a big deal. And it’s certainly being discussed around conference rooms and water coolers throughout Europe and the rest of the world. Many companies are beginning to make the necessary changes to their systems to adhere to new laws. Others are, well, still in the “deer in the headlights” phase.</p><p>Regardless of which camp you are in, you need to know what to expect from your CMS vendor. As your trusted platform for your business, your CMS is at the core of your GDPR compliance journey. Are they prepared for the new laws? Are they giving you the tools you need? Let’s take a look at what you should expect from your CMS platform when it comes to the new regulations.</p><h3>Prepared for GDPR</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*sRge8_Qbs_-nnU8TrwC4JQ.png" /></figure><p>First and foremost, your CMS vendor should be well-versed in the ways of GDPR. They should have a deep understanding of the new regulations, the impact it has on user’s data, and what their responsibilities are for compliance. While most of the onus is on the implementation partner, vendors should still be aware of the challenges their customers (You) will face.</p><p>Because of the far-reaching aspects of the regulations, vendors need to know exactly how and where data is being stored within their systems. This means reviewing every bit of code within the platform, and documenting what is being stored and where. CMS vendors should be following the regulations closely, tracking any deadlines and dates. This information will be essential for their customers looking to shore up their sites security and get compliant.</p><p><strong>The bottom line</strong></p><p>Your CMS vendor should have updated documentation on GDPR, and time invested in researching and understanding the new regulations. They should fully understand how the new laws affect them as a software provider, as well as businesses who use their software.</p><h3>Access to data</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*J4UJ38vRVdhD-e7aVk4jYA.png" /></figure><p>Once a CMS vendor identifies the data, they need to make sure their partners can get to it. Every company that implements a site with a CMS will need to be able to provide their users with access to their personal data, a full list of the information, and the ability export it to a number of formats. Getting to that data should be easy and straightforward, reducing the roadblocks a company will have in trying to adhere to the news rules. Prebuilt modules and utilities to get this data is a huge bonus, as anyone using the platform will need to comply.</p><p><strong>The bottom line</strong></p><p>Look for a CMS vendor that has easily viewable, open data repositories to help you become GDPR compliant. Ideally, they’ll have some pre-made utilities to help you view all your client’s data quickly, and the ability export them, if needed. Because much of the GDPR laws center around the user’s ability to control their information, expect your CMS vendor to provide the ability o get consents, adhere to data requests, and forget a user, if needed.</p><h3>Customized solutions</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*M3i6HZ10Pgynxac_SAu87w.png" /></figure><p>Every business is different. The data you collect and store about your users can be as varied as a fingerprint, so a custom GDPR solution is always a possibility. If you’re leveraging a CMS, you will likely need to store specific information about your users, in a very unique way. While you don’t want to give up all the sweet data you collect on your users, GDPR can drastically alter how and when that data is stored. As you define your individual GDPR needs, you need to ensure your CMS is up to the task.</p><p>Nearly every CMS offers an Application Programming Interface (API) to develop with. When it comes to your user’s data, be sure your platform has GDPR-ready interfaces to help you create your solutions. This means the ability to log data quickly, but still ensure what you’re storing is compliant. A flexible and scalable API is key here, and will ease the burden of getting your sites up to code.</p><p><strong>The bottom line</strong></p><p>You CMS should be easily extendable with a robust API. The interface should be updated to help you continue to store data, while ensuring you adhere to the new rules. As stated before, the data should be easily accessible and enable you to implement whatever customizations needed for you to follow the laws, but keep your business productive.</p><h3>A committed partner</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/624/1*MCfCHTAxwguxW1O0QKN83A.png" /></figure><p>There’s no magic switch to make your sites GDPR compliant. Because the new regulations are so exhaustive, it’s going to take plenty of time and planning to understand exactly what you’re going to need to do and when. And like with most jobs, many hands make for quick work. Having a trusted partner on your journey can lighten load, and make sure that nothing gets overlooked. Because your CMS vendor built the platform, they will be the most knowledgeable when it comes to what you’ll need to do to get things in order.</p><p><strong>The bottom line</strong></p><p>You made an investment to use a CMS. Make sure your CMS vendor has made an investment in you and your success. They need to be upfront with information and guidance. They should be knowledgeable about the new rules and regulations and provide detailed documentation. And above all, they need to be a good partner and ready to help you stay a satisfied and happy customer.</p><h3>Moving forward</h3><p>People invest a lot of time and money into choosing a CMS for their applications. Features and functionality aside, what’s most important is how well your organization can use the tool to achieve their goals. When it comes to GDPR, this is especially important as you will need every advantage you can get. In this article, I shared some key things to expect from your CMS vendor to help prepare you. It’s certainly not the end of the list, but a good starting point if you’re beginning your regulation compliance adventure. In the end, I hope your CMS is a great partner and you’re able to update set your sites up for success and a harmonious, GDPR-compliant future. Good luck!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=6f1bebe8f3d7" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/what-you-should-expect-from-your-cms-vendor-when-it-comes-to-gdpr-6f1bebe8f3d7">What You Should Expect from Your CMS Vendor When It Comes to GDPR</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Help! My Azure Site Performance Sucks! — Part 3]]></title>
            <link>https://medium.com/@bryan_soltis/help-my-azure-site-performance-sucks-part-3-744dc54297f3?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/744dc54297f3</guid>
            <category><![CDATA[tips-and-tricks]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[azure-websites]]></category>
            <category><![CDATA[azure]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Thu, 01 Feb 2018 15:39:56 GMT</pubDate>
            <atom:updated>2018-02-01T22:02:48.502Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*IoedLiDZKnaKlbw3ZwxrbQ.jpeg" /></figure><p>Oh, snap!</p><p>I bet you weren’t expecting another post in this series.</p><p><strong>Note</strong><br>You can check out <a href="https://hackernoon.com/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0"><strong>Part 1</strong></a> and <a href="https://blog.usejournal.com/help-my-azure-site-performance-sucks-part-2-df28f40b3778"><strong>Part 2</strong></a> of the series here.</p><p>Well, before you get too excited, just know that this one is really about an infographic. You see, when I was creating Part 2 of this series, I wanted to make it a bit more exciting with some images. I created several smaller graphics, each detailing the steps to take to fix your site performance issues. In doing so, I inadvertently came up with an nice infographic to put all the pieces together.</p><h3>Ooh, an infographic!</h3><p>For the image, I combined the <strong>Quick Fix</strong> and <strong>Longterm Solution</strong> sections for each area, along with a handy chart to show you the potential impact.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*taiXxcFwP_hLn1-t4w-6IQ.png" /></figure><p>When working with Azure, certain things you do may result in some drastic improvements when it comes to performance, while others will have less. In all, you will want to do everything you can to ensure your site is running as smoothly as possible.</p><p>So there it is. Exciting, right? I’m not much of a designer, but I still wanted to put something together to help you get answers quickly. I’m sure you are going to rush over to Kinko’s (is that still a thing?) and print up copies to plaster all over your walls.</p><h3>Wrapping Up</h3><p>This article wraps up this series. I hope you’ve learned a lot about Azure and how to get your App Services running smoothly. If you can’t tell, I kind of like talking about Azure and to develop on the platform. Feel free to hit me up with your questions and comments. Good luck, friends!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=744dc54297f3" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Help, My Azure Site Performance Sucks! — Part 2]]></title>
            <link>https://medium.com/@bryan_soltis/help-my-azure-site-performance-sucks-part-2-df28f40b3778?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/df28f40b3778</guid>
            <category><![CDATA[tips-and-tricks]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[web-development]]></category>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[performance]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Wed, 17 Jan 2018 20:14:29 GMT</pubDate>
            <atom:updated>2018-02-02T15:48:04.244Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*myKDRrtEMdJjdkdPnwAktg.png" /></figure><p><strong>Note</strong><br>You can check out <a href="https://hackernoon.com/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0"><strong>Part 1</strong></a><strong> </strong>and <a href="https://medium.com/@bryan_soltis/help-my-azure-site-performance-sucks-part-3-744dc54297f3"><strong>Part 3</strong></a><strong> </strong>of the series here.</p><p>Hello and welcome to Part 2 of my “Help, My Azure Site Performance Sucks!” series. In <a href="https://hackernoon.com/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0">Part 1</a>, I gave you a glimpse into how I go about diagnosing issues when someone reports a problem with their cloud-hosted sites. I really wanted to let you know how I tackle diagnosing an issue and the areas I look into first. In this next article, I want to give you more concrete examples of exactly how you can go about fixing your performance woes.</p><p>Performance slowdowns are rarely change-this-one-thing-and-everything-is-awesome scenarios. More often than not, you’re going to need to look at several areas of your environment and Sherlock Holmes your way to a solution. Because there are so many factors in play, small problems get compounded into big ones and start affecting other systems. If <a href="https://hackernoon.com/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0">Part 1</a> taught you anything, I hope it’s how to step back and evaluate each piece before you go all Hulk-Mania on your IT guys.</p><p>When performance issues arise, they never tiptoe into your organization and whisper that something’s wrong. It’s more like a freight train barreling through the front door. With bees. And the bees have lasers instead of eyes. You get the idea. The impact is immediate and horrible and everyone needs them fixed NOW! As with most things, there are steps you can take right away, and others that will help fix the issue in the long term.</p><p>To help with these two timelines, I’ve broken the topics down into distinct areas, with some steps to take in each case. I’ve included suggestions you can use to ease the pain, and long-term solutions to prevent them coming back. So, let’s get to the tips!</p><h3>The Database Dilemma</h3><p>As I said before, the database is almost always the issue. Whether it’s bad design or configuration, data-driven sites always seem to fall victim to slow performance when hosting in Azure. The good thing is that problems are usually easy to find and Band-Aid. The bad thing is, you may need to consult a DBA to get your site performing at 100%.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*9cPBul87eWiY20xReTRjBg.png" /><figcaption>Database — Do this now!</figcaption></figure><p>If you see that your DTUs are spiking and want immediate results, simply scale your database to the next tier. It’s a great way to see instant performance improvements. Just be sure to take a seat when the next Azure bill comes in if you scale up to the P2/3 range. This should be considered a temporary fix while you get to the bottom of what is really causing your performance issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*O7HxqzMzsNmmT3VAzl6Jjw.png" /><figcaption>Database — Do this to fix the issue.</figcaption></figure><p>With detailed knowledge of where your database is having problems, hit up your neighborhood DBA to see what indexes make sense for your application. They love talking about those things and it can have a huge impact on improving your performance and reducing latency. By tuning your database for your exact needs, you’ll get much more efficient processing and a lot fewer DTU spikes. You can even use the Recommendations from the Azure portal to help identify which indexes are good to keep around.</p><h3>App Service Specs</h3><p>If your database isn’t the cause of your troubles, take a look at your web server. Is it maxing out its memory or CPU? Are your processes taking forever to complete? Maybe your site monitoring software is blowing up your pager (you still have one, right?) every night. If so, you may need to check out your App Service plan to see the details. Here’s what you can do to help fix your performance issues.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Ry9Ezd9xhEDXyRWHQkIUCQ.png" /><figcaption>Web — Do this now!</figcaption></figure><p>Scaling up your app service plan will allocate more resources to your site, addressing the issue in the short term. Azure has a lot of great tools in the <strong>App Service Advisor</strong>,<strong> </strong>which can provide guidance on where your service is having trouble. It’s a great place to start and should be one of the first things you do. If you’re using Application Insights, check out the <strong>Slowest Requests </strong>report to find out which areas of the site are performing the worst. This information can help you in fixing the bigger issue if your web server is running out of steam.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*Qe6dAtQQt5YCgaUDAkPelQ.png" /><figcaption>Web — Do this to fix the issue.</figcaption></figure><p>In the long term, you want to ensure your app service will perform under any load. This means scaling up your number of servers (manually or automatically), and making sure you understand what’s happening with your resources. Set up <strong>Alerts </strong>in your Azure portal to get notifications for when you run out of resources. If you’re using multiple servers and sessions, you should be using <a href="https://azure.microsoft.com/en-us/services/cache/"><strong>Azure REDIS Cache</strong></a>, so be sure to scale that up with the service plan, if needed. The main thing here is to <strong>monitor your activity</strong>! It’s the only way you’ll know how the Website Express is running, and it will give you a glimpse into when it comes off the rails.</p><h3>Serving Media</h3><p>If you are still having problems with page loading, it may be due to how you are working with media within your site. There’s about a billion different ways to reference an image, and understanding how to leverage Azure to the fullest will be key for your scenario. You can certainly kill your performance by doing things the wrong way, so solid coding and know-how will go a long way.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*9_hY0FaPKBvaVIUxJ5_hyA.png" /><figcaption>Media — Do this now!</figcaption></figure><p>For quick results, you should focus on good coding techniques and practices. This means reducing the payload you send to the client and limiting the number of calls. Make sure your images are web sized and leverage CDN-hosted external scripts, if needed. While your marketing may LOVE the idea of loading 100+ 20GB images for your product gallery, those AOL users still in your network won’t think the same way. You need to be sure you’re catering to your audience and their connection speeds, where possible.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*MmURuRcAn5qAOI6dMLt5ow.png" /><figcaption>Media — Do this to fix the issue.</figcaption></figure><p>If you can, move all your images to Azure Storage, and update your paths to use the full CDN URL. You’ll cut down on the work your web server has to do with serving images, and replicate your content around the globe for super speedy delivery. And don’t forgot to resize your images for mobile devices and small screens! If you’re using a platform for your site like a CMS, this may already be built into the functionality for you.</p><p>For your JS and CSS, do whatever you can to reduce their size and the amount of calls. Many browsers limit the number of requests you can make from a single domain, so the fewer in your code, the better. If you‘re using the CDN, be sure you understand <a href="https://docs.microsoft.com/en-us/azure/cdn/cdn-manage-expiration-of-blob-content">Time-To-Live (TTLs)</a> settings so that your content is cached correctly. If you have frequently changing scripts, you will want to make sure your updates are propagated correctly.</p><h3>Better Code</h3><p>If you’ve ruled out the database and the app service, there’s a good chance the problem lies within your code. While the other areas are pretty cut and dry on how to approach them, custom functionality is a bit tougher to diagnose. Hopefully, you have access to your repository and can dig in and check out what’s going on.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*ANX8G1I_Xwt9Udy3JGXYLg.png" /><figcaption>Code — Do this now!</figcaption></figure><p>These suggestions are really about doing the basics: resolving errors, eliminating variables, and tracking the diagnostics. As with any application, nothing can replace good design and logic, so be sure your site has both. Get an experienced developer to review each piece of custom functionality. If something’s not being used, disable it! There’s no sense in executing a cleanup task when no one uses that section of the site. And if you’re getting errors, you’re making the system do extra work every time it happens. Resolve those ASAP!</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*mCgqhNBjnlnuDX9b5OS31Q.png" /><figcaption>Code — Do this to fix the issue.</figcaption></figure><p>To fix code in the long run, you really need to make sure everything is up to date. If you’re using a platform for your application, make sure it’s on the current version and patched. Ensure that you’re calling the database efficiently, pooling requests when you can. And <strong>TEST YOUR CODE</strong>! Azure gives you <strong>Deployment Slots</strong>, the<strong> Performance Test</strong> utility, and <strong>Diagnostic Logs</strong> to help you ensure your code is running great before it’s ever deployed to Production. Knowing about an issue ahead of time can save a lot of tough conversations and stress ball abuse.</p><h3>Other Stuff</h3><p>When it comes to Azure, certain things are exactly the same as any other hosting (file systems, memory, etc.), but some areas have a completely different way in which they work. Things like session management, caching, and infrastructure can have a very different look to them when it comes to cloud. If your code is closely tied to these types of substructures, they can certainly cause a lot of havoc when it comes to assembling the Voltron-esque collection of systems that make up your site.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/600/1*eXTI8jWY5Y6V1bhUx4cNZw.png" /><figcaption>Other stuff — Do this to fix the issue.</figcaption></figure><p>Azure has a lot of secondary systems that can offload your heavy lifting. From <a href="https://azure.microsoft.com/en-us/services/functions/"><strong>Azure Functions</strong></a> to <a href="https://azure.microsoft.com/en-us/services/logic-apps/"><strong>Logic Apps</strong></a>, the server-less architecture is a great way to improve your site performance while reducing your resource consumption. If you did your <strong>Performance &amp; Load Tests</strong>, you should know which areas of your site are causing your slowdown. Automate integrations where you can, and get the cloud working for you!</p><h3>Architecting for the Future</h3><p>When all’s said and done and you’ve made every improvement you can, you may still find yourself with not-so-stellar site performance. If this is the case, you really need to consider the fact that your application may just need horsepower. If you’ve rolled out your database in an S-0 to save some cash, you’re going to quickly find that no amount of code changes or reconfiguration is going to give you what you need to run smoothly. You need to make sure your application and database have all the resources they need to do the job.</p><p><strong>I always recommend at least an S1 App Service Plan for a production site.</strong></p><p>Your mileage may vary. However, I have found that starting with the Standard tier and working your way up is a good method when spec’ing out your web server. Depending on your storage and memory needs, Premium may be a better bet, so be sure to monitor your site carefully.</p><p><strong>I would always start with an S2 or P1 Azure Database and expect to scale up</strong>.</p><p>Modern systems have so much read/write activity, the lower tiers (Basic / Standard 0/1) just don’t have enough DTUs allocated to keep up with the demand. By starting with S2+, you should be better suited for a “standard” application. Again, the Premium tier may be the best bet, depending on your backup and performance needs.</p><p><strong>Use Azure Storage with the CDN</strong>.</p><p>It’s such a simple solution to storing content that it would be foolish not to use it. With data centers around the world, your content will be cached and delivered faster than a DOS attack on a SQL Server 6.5 instance (As SOON as you brought it online!). Be sure you understand and implement TTLs for your modified files, especially your JavaScript and CSS.</p><p><strong>With all architectures, it is important to be flexible.</strong></p><p>Your initial configuration may be great for your launch, however, after that well-timed Super Bowl airs, your traffic may go through the roof. Be prepared to adjust your environment as needed. With auto-scaling, your app service can add new servers when it needs them, then scale back down when the hordes move on to the next Internet fad. It’s a great way to control your costs, and keep a little bit of your hair from being pulled out.</p><h3>Moving Forward</h3><p>Hopefully, this article gave you some concrete ideas on how to help your Azure sites perform better. Unfortunately, there’s not a Hogwarts’s spell that fixes the problem, but there are several things you can do to set yourself up for success with the right solution from the start. The key is to always be monitoring because performance never stays the same. Azure gives you a ton of tools to track your activity, so be sure to use them! Good luck, friends!</p><p>Have some other ideas to improve performance? Why not share them in the comments!</p><p><strong>This story is published in </strong><a href="http://blog.usejournal.com/"><strong>Noteworthy</strong></a><strong>, where 10,000+ readers come every day to learn about the people &amp; ideas shaping the products we love.</strong></p><p><a href="http://blog.usejournal.com/"><strong>Follow our publication</strong></a><strong> to see more product &amp; design stories featured by the </strong><a href="https://usejournal.com/?/utm_source=usejournal.com&amp;utm_medium=blog&amp;utm_campaign=guest_post&amp;utm_content=bryan_soltis"><strong>Journal</strong></a><strong> team.</strong></p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=df28f40b3778" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Help! My Azure Site Performance Sucks! — Part 1]]></title>
            <link>https://medium.com/hackernoon/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0?source=rss-7b17752b4823------2</link>
            <guid isPermaLink="false">https://medium.com/p/5a3a1b048ac0</guid>
            <category><![CDATA[azure]]></category>
            <category><![CDATA[performance]]></category>
            <category><![CDATA[azure-app-service]]></category>
            <category><![CDATA[azure-database]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <dc:creator><![CDATA[Bryan Soltis]]></dc:creator>
            <pubDate>Thu, 21 Dec 2017 21:43:19 GMT</pubDate>
            <atom:updated>2018-02-02T15:47:08.172Z</atom:updated>
            <content:encoded><![CDATA[<figure><img alt="" src="https://cdn-images-1.medium.com/max/960/1*60Ig0PMfhS2QwYKnfQlvUg.jpeg" /></figure><p><strong>Note</strong><br>You can check out <a href="https://blog.usejournal.com/help-my-azure-site-performance-sucks-part-2-df28f40b3778"><strong>Part 2</strong></a> and <a href="https://medium.com/@bryan_soltis/help-my-azure-site-performance-sucks-part-3-744dc54297f3"><strong>Part 3</strong></a><strong> </strong>of the series here.</p><p>Let me guess. You’ve seen the light when it comes to the cloud and migrated your application to Microsoft Azure. Your site is hosted on an app service big enough to run a BitCoin mega-mine, and your database is a technological spectacle of SQL SaaS goodness. You get everyone in the company together to toss you on their shoulders and marvel at your new cloud-powered creation, and its performance…well… sucks. Before you go rolling your site back to the 486DX in the supply closet, let me give you some tips in this two-part blog series on how to get it running smoothly in Microsoft’s cloud.</p><p>I’ve been working with Azure a long time. In technology-terms, I suppose I’m a great-grandfather when it comes to cloud computing. If not that, at least a distant relative that shows up at family dinners and steals stamps. Either way, since 2008, I’ve created applications for it, written articles about it, given bootcamps for it, and waved the Azure banner on every street corner I could. I love the platform and am constantly amazed at how much you can achieve with it. As an Azure MVP, I let everyone know how great working with the cloud can be at every conference, event, code camp, wedding, and parent-teacher meeting I attend. Yeah, I kind of like working with Azure.</p><p>But to be honest, when running in the cloud, things don’t always go smoothly. I’ve seen applications that can be lightning fast in one environment crawl to 14.4K speeds when deployed to Azure. I’ve had the most seasoned software engineers question everything about the platform, and question how it can be so great with such bad latency and performance. They sit baffled at their deployments, with no obvious reason for their painfully slow sites.</p><p>I totally get it! The cloud gets touted as this wunderkind of technology that will solve your problems!</p><p>But what gives with the craptastic speeds?!? I’ve worked with a lot of clients and developers over the years to help them answer that question when it comes to their Azure applications. Let me illuminate the possibilities…</p><h3><strong>Read the manual</strong></h3><p>One of the biggest reasons for bad Azure performance comes down to education. This is especially true of developers just getting started with the cloud and not fully understanding what the platform is. Azure isn’t one thing. It’s 100s of things (and growing!). It’s infrastructure, connectivity, functionality, scalability, and flexibility, all rolled up into a five-letter name that no one can seem to agree on how to pronounce. Because of its vast capabilities, fully grasping all the individual pieces can be a daunting task, especially if you’re new to the game.</p><p>Every time I begin to diagnose someone’s Azure woes, I first start by ascertaining what they know about the cloud. Do they get why cloud computing even exists? Do they understand Cloud Services vs App Services? Did they lift-and-shift their app to the cloud, or was it architected there from the beginning? Did they have any Azure expertise on-hand for the process, or did they wing it? These are all important factors when it comes to why a particular architecture or configuration was chosen, and can set the stage for some seriously long application loading time if not done correctly.</p><h3><strong>Remove the variables</strong></h3><p>As any developer who has tried to hunt down that phantom bug that only Linda in accounting can produce, you need to take a pragmatic approach when it comes to determining why your Azure site isn’t performing. Rule out as much of the equation as possible. If you have 100 variables in your environment, you’ll spend most of your time hunting and pecking your way to insanity. Save yourself some headache (and therapy) and eliminate as much of the riffraff as possible.</p><p>If you have multiple apps on the same server, isolate them to their own instances. Are your application database and storage in different data centers? Set up your own Three’s Company episode and get all your resources in the same region. Does the issue only happen to authenticated users or a specific area of the site? Try to identify the common denominators to help isolate the issue.</p><p>Knowing what NOT to look at can be one of the best steps you take toward getting your performance issues resolved.</p><h3><strong>What’s causing the problem?</strong></h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*8kR6p8k3ZeLTbVQObPaFoA.jpeg" /><figcaption>I combined decks to make it more exciting!</figcaption></figure><p>OK, so you know your team is skilled in ways of Azure-ology, and you’ve removed as many variables as you can. Now, you need to start trying to identify where the problem is. If you’re lucky, it’s a single factor in the environment that causes the problem. If that’s the case, stop what you’re doing and go buy a lottery ticket or something.</p><p>Chances are, you’ll have several components that are causing you grief. You just have to figure out which ones. And you will need to prepare yourself to change more than one thing. In many cases, it’s several aspects of the deployment that contribute to the slowdown.</p><p><strong>App Service</strong></p><p>Determining if the web server (App service) is the root of your problems tends to be a pretty simple process. In the Azure portal, you can check out the server performance and see if you’re getting spikes in your CPU and memory. If you find your app is causing your server to max out on a regular basis, you want to start thinking about scaling up or out. One of the best parts of Azure is the ability to scale your web environment quickly, automatically if needed. Check out your App Service plan settings and adjust until you get the performance you’re looking for.</p><p>This is one of the simplest things you can do to address performance, but only if your problems are web server related. To be honest, I rarely see the app service as the cause of the problem. More often than not, it’s a data and/or architecture related issue. If the server looks like an EKG for the Tin Man (no heart beats, i.e., no spikes), it’s time to keep searching.</p><p><strong>Database</strong></p><p>A lot of developers will start with hosting their database in SQL Database (or Azure SQL…or SQL Azure…or SQL Database for Azure. I’ve seen more than a few name changes.). And for good reason! It’s an extremely scalable SQL environment that you can get for a few dollars a month (depending on your needs). Your data is automatically replicated on the backend for DR and you can easily deploy your database via SSMS and connect your website in seconds. What’s not to love??</p><p>Well, there’s a mythical creature called a <a href="https://docs.microsoft.com/en-us/azure/sql-database/sql-database-what-is-a-dtu">DTU (Database Throughput Unit)</a> that has eluded developers for years. DTUs are not a single measurement, but rather a collection of variables that Microsoft uses to calculate the resources your database is consuming. These are CPU, memory, and read-write rates. (trust me, after nine years, I still get a little confused). Microsoft uses DTUs to figure what kind of resources your database is consuming, to make sure everyone on the platform is getting what they pay for.</p><p>When it comes to bad performing Azure sites, DTU spikes are usually at the top of the discussion. Whether it’s long running queries, poorly-performing indexes, or just bad code that causes way too many calls, an overworked SQL Database can slow down any application. If you find your SQL Database is beaten down and struggling, check out the Support &amp; Troubleshooting section of the Azure portal for help. Use those tools to figure out which queries are taking up the most time, and when your DTUs are spiking.</p><p><strong>DTU issues are probably the most common culprit I’ve seen in the past 9 years.</strong></p><h3>Serving images</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*2eFkmqsTay7jGZgzNSvyUA.jpeg" /><figcaption>Just hold that position for another 32 minutes.</figcaption></figure><p>Going back to the first point about education, handling images is where I’ve most often seen developers not using Azure to its potential. When it comes to media, developers should rethink the “deploy-with-site” model and explore the unique capabilities that Azure can offer. Because Azure storage is so flexible (and easy to configure), not using it for images in an application is a huge mistake that could be costing your site a lot of precious performance. The Azure CDN functionality gets included with Storage, so serving your site media from a global network of data centers (instead of where your site is deployed) can drastically speed up load times throughout your site.</p><p>In addition, offloading your images to the CDN means less calls to your main URL to load content, which means a lot better parallel request management.</p><h3>Maybe it’s the code</h3><figure><img alt="" src="https://cdn-images-1.medium.com/max/842/1*6_bjXQCTGkbHS9Dw1R79LQ.jpeg" /><figcaption>Aww, man! I got the Gray Screen of Death!</figcaption></figure><p>No amount of memory, processors, or servers can fix bad code. When all the architecture areas have been addressed and a site is still slow, I always ask about the custom functionality. This is where things can get tricky, and take a lot of time.</p><p>If you’re using a 3rd party platform for your site, chances are that company has put a lot time into making sure the “vanilla” version of the product will run in any environment. With that in mind, your custom code may be the villain. Make sure your code base is up to date with the latest fixes, and then start digging into your functionality.</p><p>You will want to make sure you are accessing your data as efficiently as possible. Are you leveraging caching and vendor APIs to store data in memory? Are you pulling back only the data you need, reducing the overall payload? Are you trying to divide by zero or some other wormhole-producing action in your custom functionality?</p><p>You need to dig through every piece of your code and make sure it’s as optimal as possible. Unfortunately, reworking code is never an easy task and one you’re going to have to pack a lunch for, especially if the intern in the cubicle next you who wrote the entire contact management module.</p><p>Diligence is key here, so don’t cut corners! Be sure to check out anything with a database connection, memory access, or functionality that relies on external systems. Learn how to leverage Azure caching and storage to improve speed and latency. You may find you need to update several areas of your site. Azure is a big mountain to climb, so take it one step at a time.</p><h3><strong>Time to think things over</strong></h3><p>OK, so your mind may be a bit like a Game of Thrones family tree right now. You’re probably already processing all the possible areas you may have to update, configure, and rework within your site. I’m going to wrap this blog up here to give you time to process things. In my next article, I’m going to give my recommendations on how you should architect your Azure applications to minimize performance issues in the future. It will also be packed with more tips on steps to take to identify issues, implement stop-gap solutions, and build better Azure sites. Until next time, friends.</p><h3><strong>UPDATE!</strong></h3><p>Want to get some real tips and tricks? Check out <a href="https://medium.com/@bryan_soltis/help-my-azure-site-performance-sucks-part-2-df28f40b3778"><strong>Part 2</strong></a> of the series!</p><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=5a3a1b048ac0" width="1" height="1" alt=""><hr><p><a href="https://medium.com/hackernoon/help-my-azure-site-performance-sucks-part-1-5a3a1b048ac0">Help! My Azure Site Performance Sucks! — Part 1</a> was originally published in <a href="https://medium.com/hackernoon">HackerNoon.com</a> on Medium, where people are continuing the conversation by highlighting and responding to this story.</p>]]></content:encoded>
        </item>
    </channel>
</rss>