oatpp

2025-12-10 0 567

 

Oat++

Oat++ is a modern Web Framework for C++.
It\’s fully loaded and contains all the necessary components for effective production-level development.
It\’s also light and has a small memory footprint.

News

  • ️ Attention! Oat++ main repo is bumping its version to 1.4.0. While 1.4.0 is IN DEVELOPMENT use 1.3.0-latest tag.
  • Follow the changelog for news and features in version 1.4.0.
  • Consider supporting Oat++ via the GitHub sponsors page.

New ORM integrations:

  • oatpp-mysql by @Atarasin
  • oatpp-mariadb by @lilltiger

Start

  • Get Started
  • Build For Unix/Linux
  • Build For Windows
  • Examples

Support the Project

Maintaining and developing this project requires significant time and resources. If you enjoy using it and want to support its continued development, please consider supporting us through GitHub Sponsors.

Become a Sponsor on GitHub

Every contribution, big or small, helps us keep improving and maintaining the project.
Thank you for your support!

About

  • Website
  • Supported Platforms
  • Latest Benchmarks: 5 Million WebSockets
  • Contributing to Oat++

Quick Overview

Shortcuts:

  • Oat++ High Level Overview – Get a quick overview of Oat++ features.
  • Example Project – A complete example of a \”CRUD\” service (UserService) built with Oat++. REST + Swagger-UI + SQLite.

Build Powerful API And Document It With Swagger-UI

See ApiController for more details.

ENDPOINT_INFO(getUserById) {
  info->summary = \"Get one User by userId\";

  info->addResponse<Object<UserDto>>(Status::CODE_200, \"application/json\");
  info->addResponse<Object<StatusDto>>(Status::CODE_404, \"application/json\");
  info->addResponse<Object<StatusDto>>(Status::CODE_500, \"application/json\");

  info->pathParams[\"userId\"].description = \"User Identifier\";
}
ENDPOINT(\"GET\", \"users/{userId}\", getUserById,
         PATH(Int32, userId))
{
  return createDtoResponse(Status::CODE_200, m_userService.getUserById(userId));
}

Access Databases And Keep Your Data Consistent

See Oat++ ORM for more details.

QUERY(createUser,
      \"INSERT INTO users (username, email, role) VALUES (:username, :email, :role);\",
      PARAM(oatpp::String, username), 
      PARAM(oatpp::String, email), 
      PARAM(oatpp::Enum<UserRoles>::AsString, role))

Join Our Community

  • Gitter – Talk to Oat++ developers and to other Oat++ users.
  • Twitter – Follow Oat++ on Twitter.
  • Reddit – Follow Oat++ subreddit.
  • StackOverflow (new) – Post a Question.

Examples

REST-API

  • REST Service – A complete example of a \”CRUD\” service (UserService) built with Oat++. REST + Swagger-UI + SQLite.
  • REST Client – Example project of how-to use Retrofit-like client wrapper (ApiClient) and how it works.

WebSocket

  • Can Chat – Feature-complete rooms-based chat for tens of thousands of users. Client plus Server.
  • WebSocket – Collection of oatpp WebSocket examples.
  • YUV Websocket Stream – Example project how-to create a YUV image stream from a V4L device (i.E. Webcam) using websockets.

Databases

  • SQLite – A complete example of a \”CRUD\” service. REST + Swagger-UI + SQLite.
  • PostgreSQL – Example of a production-grade entity service storing information in PostgreSQL. With Swagger-UI and configuration profiles.
  • MongoDB – Example project how to work with MongoDB using oatpp-mongo mondule. The project is a web-service with basic CRUD and Swagger-UI.

IoT

  • Example-IoT-Hue – Example project how-to create a Philips Hue compatible REST-API that is discovered and controllable by Hue compatible Smart-Home devices like Amazon Alexa or Google Echo.

Streaming

  • HTTP Live Streaming Server – Example project on how to build an HLS-streaming server using Oat++ asynchronous API.
  • YUV Websocket Stream – Example project how-to create a YUV image stream from a V4L device (i.E. Webcam) using websockets.

TLS

  • TLS With Libressl – Example project how-to setup secure connection and serve via HTTPS.

Microservices

  • Consul Integration – Example project on how to use oatpp::consul::Client. Consul integration.
  • Microservices – Example project on how to build microservices with Oat++,
    and example on how to consolidate those microservices using monolithization technique.

Asynchronous API

  • Async Service – Example project on how to use asynchronous API to handle a large number of simultaneous connections.

Frequently Asked Questions

Q: \”Oat++\” name?

  • \”Oat\” is something light, organic, and green. It can be easily cooked and consumed with no effort.
  • \”++\” gives a hint that it is \”something\” for C++.

Q: What is the main area of Oat++ application?

Oat++ is used for many different purposes, from building REST APIs that run on embedded devices to
building microservices and highly-loaded cloud applications.

But the majority of use cases appears to be in IoT and Robotics.

Q: How portable is Oat++?

Theoretically, Oat++ can be easily ported everywhere where you have threads and network stack.
With an additional comparably small effort, it can be ported almost everywhere depending on how
much you strip it and what would be the final binary size.

See supported platforms for additional info.

Q: What is the size of a minimal Oat++ application?

About 1Mb, depending on C/C++ std-lib and oatpp version.

Q: Which Oat++ API to choose, Simple or Async?

Always choose Simple API wherever possible. Simple API is more developed and makes the code cleaner.

Async API is designed for small, specific tasks that run at high concurrency levels ex.:

  • Serving file downloads to a large number of concurrent users (1K users and more).
  • Streaming to a large number of clients (1K or more).
  • Websocket Chat servers.

For all other purposes use simple API.

下载源码

通过命令行克隆项目:

git clone https://github.com/oatpp/oatpp.git

收藏 (0) 打赏

感谢您的支持,我会继续努力的!

打开微信/支付宝扫一扫,即可进行扫码打赏哦,分享从这里开始,精彩与您同在
点赞 (0)

申明:本文由第三方发布,内容仅代表作者观点,与本网站无关。对本文以及其中全部或者部分内容的真实性、完整性、及时性本站不作任何保证或承诺,请读者仅作参考,并请自行核实相关内容。本网发布或转载文章出于传递更多信息之目的,并不意味着赞同其观点或证实其描述,也不代表本网对其真实性负责。

左子网 编程相关 oatpp https://www.zuozi.net/33563.html

webxcel
上一篇: webxcel
Cemu
下一篇: Cemu
常见问题
  • 1、自动:拍下后,点击(下载)链接即可下载;2、手动:拍下后,联系卖家发放即可或者联系官方找开发者发货。
查看详情
  • 1、源码默认交易周期:手动发货商品为1-3天,并且用户付款金额将会进入平台担保直到交易完成或者3-7天即可发放,如遇纠纷无限期延长收款金额直至纠纷解决或者退款!;
查看详情
  • 1、描述:源码描述(含标题)与实际源码不一致的(例:货不对板); 2、演示:有演示站时,与实际源码小于95%一致的(但描述中有”不保证完全一样、有变化的可能性”类似显著声明的除外); 3、发货:不发货可无理由退款; 4、安装:免费提供安装服务的源码但卖家不履行的; 5、收费:价格虚标,额外收取其他费用的(但描述中有显著声明或双方交易前有商定的除外); 6、其他:如质量方面的硬性常规问题BUG等。 注:经核实符合上述任一,均支持退款,但卖家予以积极解决问题则除外。
查看详情
  • 1、左子会对双方交易的过程及交易商品的快照进行永久存档,以确保交易的真实、有效、安全! 2、左子无法对如“永久包更新”、“永久技术支持”等类似交易之后的商家承诺做担保,请买家自行鉴别; 3、在源码同时有网站演示与图片演示,且站演与图演不一致时,默认按图演作为纠纷评判依据(特别声明或有商定除外); 4、在没有”无任何正当退款依据”的前提下,商品写有”一旦售出,概不支持退款”等类似的声明,视为无效声明; 5、在未拍下前,双方在QQ上所商定的交易内容,亦可成为纠纷评判依据(商定与描述冲突时,商定为准); 6、因聊天记录可作为纠纷评判依据,故双方联系时,只与对方在左子上所留的QQ、手机号沟通,以防对方不承认自我承诺。 7、虽然交易产生纠纷的几率很小,但一定要保留如聊天记录、手机短信等这样的重要信息,以防产生纠纷时便于左子介入快速处理。
查看详情

相关文章

猜你喜欢
发表评论
暂无评论
官方客服团队

为您解决烦忧 - 24小时在线 专业服务