5, 10 or 20 seats+ for your team - learn more
You’re a software developer for Greengrocer, a chain of supermarkets that’s losing productivity (and its customer base) thanks to a monolithic web app that can’t keep up with demand. In this series of liveProjects, you’ll design and develop three REST APIs that integrate with legacy modules while increasing scalability and addressing typical supermarket challenges. You’ll deploy your APIs to the cloud and prepare them to be accessed by Greengrocer’s UI and other software services.
As you work, you’ll implement key API design patterns, including the naming of APIs, defining of resources and their scope, and custom method definitions to ensure your APIs are scalable, fast, fail-safe, and developer- and client-friendly. These liveProjects offer explicit instruction on modern API design patterns and high-level implementation that enables you to adopt, create, deploy, and test in a short time.
I really liked the use case which walks you through the thought process involved in designing a good REST API and the importance of documenting the same.
You’re a software developer for Greengrocer, a chain of supermarkets that’s revamping its monolithic software to better handle its growing customer base. Using a design-first approach and the OpenAPI Specification, your task is to design a product catalog API to help employees track inventory. You’ll write API definitions through YAML description files and generate code and documentation for the API. When you’re done, you’ll have firsthand experience with OpenAPI Specification, YAML syntax, and schema definitions, and you’ll have improved the developer experience with good documentation.
Greengrocer’s monolithic web app is suffering growing pains. As a software developer for this chain of mid-sized supermarkets, your task is to design a supplier API to help define various resources, resource types, and resource relationships. Using an API design-first approach, you’ll design the microservice API’s resource layout, establish data type definitions for the API in YAML, then add CRUD (create, read, update and delete) as well as partial read and update functionalities for price details.
Greengrocer has built a new supplier API as part of its endeavor to handle growing market demand. Your task, as a software developer on its IT team, is to enhance this microservices API—and the administrator experience—by designing and developing custom methods that address exceptional side effects, implementing long-running jobs, and clearly defining the interactions between them.
Greengrocer, a chain of mid-sized supermarkets, has been revamping its software to keep up with market demand. As a software developer on the IT team, your task is to enhance the newly built supplier API by implementing business logic using three API design patterns: the singleton sub-resource pattern to facilitate independent and asynchronous operations, the cross-reference pattern to decouple the supplier location API from the supplier API, and the association resources pattern to maintain relationships with various resources.
Greengrocer, a chain of mid-sized supermarkets, has been upgrading its web app to keep employees—and its growing customer base—happy. As a software developer on their IT team, your task is to design a ledger API that will serve as a background REST service and help analyze data. Using advanced API design patterns, you’ll implement functionality for anonymous writes, applying filters, and API authentication and authorization with JWT.
These liveProjects are for learners who want to gain practical experience with RESTful API, microservices, design principles, and API design patterns. To begin these liveProjects you’ll need to be familiar with the following:TOOLS
In this liveProject series, you’ll learn to design and develop top-notch REST APIs that can integrate with legacy modules while increasing scalability.
geekle is based on a wordle clone.