Certificate Associate in Web Development – RESTful Web Services
The name Representational state transfer (REST) was coined by Roy Fielding from the University of California. It is a very simplified and lightweight web service compared to SOAP. Performance, scalability, simplicity, portability, and modifiability are the main principles behind the REST design.
The REST API allows different systems to communicate and send/receive data in a very simple way. Each and every REST API call has a relation between an HTTP verb and the URL. The resources in the database in an application can be mapped with an API endpoint in the REST.
When you are using a mobile app on your phone, your phone might be secretly talking to many cloud services to retrieve, update, or delete your data. REST services have a huge impact on our daily lives.
REST is a stateless, cacheable, and simple architecture that is not a protocol but a pattern.
This course will walk you through the foundation of Representational State Transfer (REST) and will explain how REST couples with the HTTP protocol. You will look into key principles that have to be considered while turning any HTTP application into a RESTful service-enabled application. You will also look at the differences between describing RESTful and classic Simple Object Access Protocol (SOAP)-based web services.
Let’s look at the key principles around the HTTP and URI standards, sticking to which will make your HTTP application a RESTful service-enabled application:
- Everything is a resource
- Each resource is identifiable by a unique identifier (URI)
- Resources are manipulated via standard HTTP methods
- Resources can have multiple representations
- Communicate with resources in a stateless manner
Upon completion of the course, participants should be able to:
- Demonstrate knowledge of fundamentals of REST architecture and verbs
- Handling Routing for REST Services, describes how to add routing to our API
- Simplifying RESTful Services with Popular Frameworks, presents quick prototyping API with frameworks
- Working with database (PostgreSQL), JSON, explains the benefits of PostgreSQL and a JSON store for creating APIs.
- Building a REST API Client and Unit Testing, presents techniques for building client software and API testing with unit tests
- Deploying Our REST Services, shows how we can deploy services built on Nginx and monitor them
- Handling Authentication for Our REST Services, discusses securing our API with basic authentication and JSON Web Tokens (JWT)
Who should attend
This course will help beginners, programmers, application developers and software engineers pick the right strategy for developing cross-platform web applications that run on a variety of desktop computers as well as mobile devices. The primary audience is developers who need to learn how to develop web applications using the HTML5 stack.
Foundational certificate in Programming
Mix of Instructor-led, case study driven and hands-on for select phases
H/w, S/w Reqd
24 Hours (2 days Instructor led + 8 hours online learning)
- Course Name: Certificate Associate in Web Development – RESTful Web Services
- Location: Melbourne
- Duration: 2 days classroom + 8 hours online
- Exam Time: 60 minutes
- Course Price: Call for price
- Minimum requirements: Foundational Certificate in Programming
|#||Topic||Method of Delivery|
Chapter 1 – Introduction to Web Services
The different Web Services available
Representational State Transfer (REST) architecture in detail
Introduction to Single Page Applications (SPA) with REST
Setting up a project and running a development server
Building our first service
Chapter 2 – Handling Routing for REST Services
Building a basic web server
Creating a basic router
Understanding httprouter, a router package
Introducing URL shortening service design
Chapter 3 – Working with PostgreSQL, JSON
Introduction to the PostgreSQL database
Installing PostgreSQL and creating users and databases
Learning about database driver
Implementing a URL shortening service with PostgreSQL and a Base62 algorithm
Exploring the JSON store in PostgreSQL
Chapter 4 – Building a REST API Client
What is a client software?
Basics for writing a command-line tool
Introducing requests, a Python request-like library
Inspecting GitHub REST API
Creating an API client
|Online Self paced|
- Certificate Title: Certificate Associate in Web Development – RESTful Web Services
- Certificate Awarding Body: ITPACS
Information Technology Professional Accreditations and Certifications Society (ITPACS) is a non-profit organization focused on improving technology skills for the future. ITPACS offers associate level, professional level and leader certifications across 6 domains including data science, web development, mobile development, cyber security, IoT and blockchain. Applicants have to go through a exam eligibility process demonstrating their experience.
The Associate certification is catered to individuals with less than 1 year working experience in the field. This is ideal for newcomers starting out in the profession or those seeking to make an entry into the profession. Applicants are required to have completed the application process prior to taking the exam.
- Exam Format: Closed-book format.
Questions: 30 multiple choice questions, coding exercises
Passing Score: 65%
Exam Duration: 60 minutes
- Exam needs to be taken within 12 months from the exam voucher issue date
Web Developers build web applications. A web application is one that helps an organization run its business online. Most web applications are built in a three-tier architecture that consists of three important layers: data, logic, and presentation. In web applications, the application structure usually breaks down to database, server, and client, while in modern web development; it can also be broken into database, server logic, client logic, and client UI.
Dynamic web pages are known as pages that are created as soon as a call is sent to the server. So data can be built interactively into the sites. They are particularly helpful when you need to react to user inputs. Forms can be evaluated immediately and the content of the next page can be shown. The application possibilities are nearly unlimited. Whether and to which extent databases are used depends on the goal. Dynamic web pages actually do not need a database.
A popular paradigm for implementing this model is the Model-View-Controller (MVC) architectural pattern. In the MVC paradigm, the logic, data, and visualization are separated into three types of object, each handling its own tasks. The View handles the visual part, taking care of user interaction. The Controller responds to system and user events, commanding the Model and View to change appropriately. The Model handles data manipulation, responding to requests for information or changing its state according to the Controller’s instructions.