Open Source Zone with with Mockoon

Key Concepts:

• API Mocking: Simulating API behavior for development and testing.
• Open Source: Software with publicly accessible source code.
• Desktop Application: Software that runs locally on a computer.
• Cloud Version: Software hosted and accessed over the internet.
• Stateful Mocking: Preserving data between API calls to simulate workflows.
• Continuous Integration (CI): Automating testing and integration of code changes.
• Mono Repository: A single repository containing multiple projects.
• CLI (Command Line Interface): A text-based interface for interacting with software.
• GitHub Actions: Automating workflows directly in GitHub repositories.

1. Introduction and Overview

• Andrea, from the Open Source Zone live at We Are Developers Congress in Berlin, introduces Mun K, the founder of the open-source API mocking tool, Mokun.
• Mokun is one of five open-source projects featured in the Open Source Zone.
• Mun K previously participated in the GitHub Accelerator program.

2. Mun K's Background and the Genesis of Mokun

• Mun K is a full-stack web developer and former intellectual property lawyer.
• He transitioned to development in 2015 and created Mokun in 2017.
• Mokun originated from the need for an API mocking tool at a bank in Luxembourg where cloud usage was restricted due to regulations.
• The initial version was a desktop offline tool, but now there's also a cloud version.

3. What is Mokun?

• Mokun is an API mocking tool designed to simulate APIs for development and testing purposes.
• The logo is inspired by raccoon eyes.
• It addresses the problem of front-end teams needing to work when back-end APIs are not yet available or accessible.

4. Use Cases and Applications

• Typical Use Case: Front-end development when back-end APIs are not ready.
• Advanced Use Case: Simulating vendor or third-party APIs that are only available in production environments.
• Enterprises in automotive and retail industries use Mokun to replicate vendor APIs for testing in CI environments.
• Mokun prevents developers from being at a standstill when back-end APIs are not ready for testing.

5. Mokun Demo (Cloud Version)

• The demo showcases the cloud version of Mokun.
• The goal is to create mock APIs quickly and easily.
• A demo API with a single endpoint ("we are developer dash conference") is shown.
• Creating an endpoint is designed to be quick and easy, appealing to developers, testers, and designers.
• A contest scenario created with Mokun is presented, where users can win a free cloud solo account.
• The contest involves an email registration endpoint with multiple responses, including a 200 success response validated against a JSON schema.
• Mokun generates a temporary API key and stores it, demonstrating stateful mocking.
• The system simulates signup/login workflows and feature flags.
• A callback is triggered to email the team, and the API key is deleted to prevent multiple entries.
• The demo highlights the balance between no-code and code elements in Mokun.

6. Mokun Architecture and Deployment

• Mokun was initially a completely offline, privacy-friendly desktop application.
• The cloud version was added later, with careful separation from the desktop version.
• Users are not forced to use the cloud version and can continue using the desktop application locally.
• The desktop application and CLI are identical to the pre-cloud release versions.

7. Open Source Aspects and Contribution

• The Mokun repository contains the desktop application, CLI, and packages for deploying to cloud functions (e.g., Amazon Lambda, Azure).
• The desktop application is available in various formats (Windows app, Winget, Brew, AppImage, DEB, RPM).
• The typical workflow involves designing the mock API in the desktop application and deploying it using the CLI in a GitHub Action.
• Contributions are encouraged, especially from users who understand and like the app.
• Contributing involves writing tests and ensuring UI consistency.
• The project aims to onboard and support contributors, including code explanation calls.

8. Future Plans and Sustainability

• The next step is to secure Mokun's future through sponsorships and cloud subscriptions.
• Enterprise support is offered for the open-source, self-hosted version, including bug fixes, setup assistance, and debugging.
• The goal is to onboard more team members and eventually contributors.

9. Call to Action

• Connect with Mun K on LinkedIn.
• Visit the Mokun website and GitHub repository.
• Leave a star on the GitHub repository.
• Use Mokun for reliable API mocking in development cycles.

10. Conclusion

• Mokun has evolved significantly since Mun K's participation in the GitHub Accelerator.
• The tool offers both offline and cloud-based API mocking solutions, catering to various user needs and preferences.
• The project emphasizes community involvement and sustainable development.