network
json-api
network | json-api | |
---|---|---|
3 | 59 | |
20 | 7,327 | |
- | 0.3% | |
4.6 | 5.2 | |
11 days ago | 7 days ago | |
Go | CSS | |
Apache License 2.0 | Creative Commons Zero v1.0 Universal |
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.
network
-
Ask HN: Why isn't JSON-RPC more widely adopted?
So funny you say this. I think it's the insight of many developers including my own. I hacked together a framework that did this before the existence of GRPC. Now I'm trying to formalise it as a protocol. https://github.com/micro/network/blob/main/PROTOCOL.md
-
More Instant Messaging Interoperability
Alright, let me throw my hat into this ring with a totally unfinished idea. I started working on a design for something called the Micro Communication Protocol (MUCP) [1]. It's a header based protocol that's transport agnostic and focuses on service-to-service communication. An early prototype existed in Micro [2] but I'm primarily focused on redesigning the protocol before re-implementing it. Micro was geared towards API first services but I'm looking to expand the scope and try to build a UI layer on top. Most of the protocols focused very much on communication between people but I think if you focus on service-to-service communication more broadly it opens up the avenue to all sorts of multiplayer collaboration.
- [1] https://github.com/micro/network/blob/main/PROTOCOL.md
-
Real World Micro Services
Yea like you're part of this club that has exclusive access to something, you contribute to it, deliver value, see it grow and then it's gone when you leave. It exists within a silo and for the better part of a decade that's really irked me but I haven't quite figured out how to solve for that problem beyond doing it in a shared open source repo and a shared platform. I think I the issue is it's bigger than any one person and you have to find a way to sell thousands of people on the idea. My starting point was code and now I wonder could I have approached this differently? Is there another path in which this would actually succeed? I'm still trying to figure it out and it's driving me crazy. Next I'll be writing a protocol no joke https://github.com/micro/network
json-api
-
Hatchify: The Fastest Way to Build JSON: APIs
In addition to saving you time on boilerplate, the API provided by Hatchify fully implements the JSON: API specification, which stipulates solid standards to define the peculiarities of CRUD REST APIs. Get back all the time spent bike-shedding how to implement standard API features like filtering, pagination, including related data, etc. JSON: API offers consistent practices for frontend and backend developers to agree on how resources are fetched and returned. Since Hatchify provides the core of your API for you, you can count on it’s standardized functionality to give your API a consistent start.
- SQL as API
-
Show HN: Sunnybox – An Email API for Effortless IMAP Integration
-JSON:API format responses (https://jsonapi.org) for better standardization.
Built using Ruby on Rails, Sunnybox is designed to offer a powerful yet easy-to-use solution for developers managing email systems.
I'd really appreciate your feedback on:
- The API's user-friendliness and efficiency.
-
What if an SQL Statement Returned a Database?
https://github.com/json-api/json-api/issues/795
There is an atomic operations extension:
-
A View on Functional Software Architecture
JSON:API to format each message
-
Custom Fields: Give Your Customers the Fields They Need
As we’re building a RESTful API that’s formatted by the JSON:API specification and store our data in a MySQL8 relational database, a few things were pretty straightforward – we need a new model and we’ll name it Custom Field (naming wasn’t an issue here 🥲).
-
How to (and how not to) design REST APIs
I found json api spec[1] recently. This kind of is better standard for REST APIs. It is bit rough to handle client side but once you get the hang of it, it is breeze to use
[1] https://jsonapi.org/
-
Building a Secure RESTful API Using NestJS and Prisma With Minimum Code
That's it! Now we have a complete set of RESTful CRUD APIs at "/api/zen" that conforms to the JSON:API specification, and the access policies fully protect the APIs. The API provides rich filtering and relation-fetching capabilities. The following are some examples; you can find more details here.
-
JSON Schema Store
Does this have any relation to https://jsonapi.org/ ?
-
An Introduction to APIs
Basic REST and JSON RPC are very simple to start with, but have common problems when application gets bigger. How do you represent relations, pagination, filtering etc? My go-to specification for structuring JSON documents is https://jsonapi.org/ It covers most basic needs of a standard API.
What are some alternatives?
services - Real World Micro Services
NSwag - The Swagger/OpenAPI toolchain for .NET, ASP.NET Core and TypeScript.
sydent - Sydent: Reference Matrix Identity Server
api-guidelines - Microsoft REST API Guidelines
Spectrum 2 - Spectrum 2 IM transports
laravel-json-api - JSON API (jsonapi.org) package for Laravel applications.
biboumi - IRC gateway for XMPP
apollo - 🚀 Apollo/GraphQL integration for VueJS
server
grpcurl - Like cURL, but for gRPC: Command-line tool for interacting with gRPC servers
grpc-swift - The Swift language implementation of gRPC.
zenstack - Typescript toolkit on top of Prisma ORM, offering flexible and declarative Access Control Policy(Authorization/Permission) for RBAC/ABAC/PBAC/ReBAC with auto-generated type-safe APIs and frontend hooks.