As an web developer, I can’t have blind spots in my understanding of applications and their execution environments. I need to know how things work in the front end (UI), the back end, the data store, the OS, any virtualization layers, the hardware, the network, and the data center.
I Believe in Lifelong Learning
Learning can no longer be divided into a place and time to acquire knowledge (school) and a place and time to apply the knowledge acquired (the workplace). Instead, learning can be seen as something that takes place on an ongoing basis from our daily interactions with others and with the world around us.
As of August 2019, a new proposal optional chaining reached stage 3 and is going to be a nice improvement. Optional chaining changes the way properties are accessed from deep objects structures. JavaScript language has added few exciting features over the past few years, like the spread operator, default argument values, and arrow functions and now new feature is optional chaining. Optional chaining allows developers to reference object properties which may or may not exist without trigger an error.
In almost every app that I build clients wants some sort of Authorization and Authentication in their applications so today I will present you one solution that is fast to build and it is great for today’s modern apps that are build with React (or maybe Angular, Vue, Ionic etc…). When you are working alone or in a small team you don’t have time or funds to reinvent the wheel. There are many great solutions for AuthR and AuthZ which are developed and heavily tested with many clients and developers so it’s good practice to use them in your next project instead of developing new custom solution.
Before start you need 2-3 things installed and configured. These are Visual Studio 2017 (on your machine), AWS Toolkit for Visual Studio (if you work on windows machine) and AWS account . If you have Mac like I do you can’t take advantages of AWS Toolkit for Visual Studio but instead you must do some things from CLI. In article below I will show you example with CLI ( create, deploy and publish .NET Core to AWS)
I think that serverless is very big thing in web development today and here I will try to explain how to build simple Node.js AWS Lambda function with basic CRUD capabilities on DynamoDB ( Amazon DynamoDB is a fully managed NoSQL database ) table and S3 bucket for file uploads. If you wanna learn DynamoDB visit this great guide on DynamoDB.
First, we need to log in to our AWS Console and select DynamoDB from the list of services. Next we need to create new DynamoDB table. Table name will be “myposts” and Primary key will be userId (also here we will set our Sort key … in our example let’s call it postId )
Today’s article is about how to start creating Fullstack Web Project. For this example I choose JAVA for backend part, to be more clear I develop Spring Boot Rest Api for backend and for client frontend, app is built with React (with redux for state management and some styling with Bootstrap 4). Complete code is available on my Github repo
Traefik is a modern HTTP reverse proxy and load balancer for microservices. Traefik serves as a router for all your microservices applications, routing all client requests to correct microservices destination. In this tutorial, I will show you how to install and configure Traefik modern reverse proxy as a Docker container on Ubuntu 18.04 with Digitalocean. So in my example you need to have installed Digitalocean droplet with Docker and Docker-compose on Ubuntu 18.04. Easiest way to do this to choose One-click apps when you create Droplet on Digitalocean, then click on Docker 18.06.1~ce~3 on 18.04 and finish creating of your new Droplet. In creation it is essential to create SSH key to improve security so we can easily ssh to our droplet through terminal. How to do this is very well described on this link: https://www.digitalocean.com/docs/droplets/how-to/add-ssh-keys/
Hello again in my new demonstration series. Today I will show you advanced calendar component which I build and use in one of my previous projects and of course here I will show you simplified version with core functionalities and not full one. Why is that? Because full working calendar component is included in one of my bigger project and has other dependencies and also frontend part of this application is connected with server-side part. This raw componet that I will show you here was my starting point in developing final component. Full source code for this calendar is available on my Github.