Search Results for "openssh-server"

...Since GraphQL has a type system, the server defines a schema that the client can query using the introspection API. This provides the client with a set of possibilities. After the client got this information and decided which parts of the data it needs, it is able to describe its data requirements in form of a GraphQL query. An important aspect of GraphQL is that it’s completely backend agnostic.

...Schemas are type safe and derived at compile time. No need to manually define a schema for every type in your API. Let the compiler do the boring work. Out-of-the-box support for major HTTP server libraries, effect types, Json libraries and more.

...Each endpoint can contain a number of input and output parameters. Compile-time guarantees, develop-time completions, read-time information. Separate the shape of the endpoint (the "what"), from the server logic (the "how"). Generate documentation from endpoint descriptions. Leverage the metadata to report rich metrics and tracing information. Re-use common endpoint definitions, as well as individual inputs/outputs. Library, not a framework, integrates with your stack. Is your company already using tapir? We're continually expanding the "adopters" section in the documentation; the more the merrier! ...

...Monitor your backend applications, fix performance issues, and get alerted when problems happen. All without being a monitoring expert. Everybody starts monitoring with logs because they are there by default. Just connect to your server and start tailing. But logs have a hard time showing you the overall response times for your application, or whether certain calls to the database are happening in sequence or parallel (among a million other things).

...Whether you like it or not, JDBC is a stable standard interface. Since most of RDBMS supports JDBC interface, we can access RDBMS in the same way. We believe that ScalikeJDBC basically works with any other RDBMS (Oracle, SQL Server and so on). If you can access some datastore via JDBC interface, that means you can access them via ScalikeJDBC too. Recently, Amazon Redshift and Facebook Presto support JDBC interface. You can access them via ScalikeJDBC! Of course, you can use c3p0 (or others) instead of commons-dbcp though ConnectionPool implementation for that isn’t provided by default.

...It compares implementations built with frameworks and runtimes such as Spray, Netty, Undertow, Jetty, Vert.x, Grizzly, Node.js, Go, and Go-fasthttp. The project focuses on large-scale long-lived WebSocket connections and documents tests reaching more than one million active connections. It includes simple server prototypes that can act as scaffolds for chat, message pushing, notification, or real-time delivery systems. The repository also provides deployment and tuning guidance for servers, clients, memory settings, file descriptor limits, and multiple test IPs. It is useful for engineers evaluating WebSocket stack behavior under extreme connection pressure.

...The core philosophy behind Spray is that it should act as a “library” for integration and HTTP layers, not as a full application framework—it gives you the building blocks to handle HTTP and REST but doesn’t impose heavy structure. It includes modules for low-level HTTP I/O, routing, client and server APIs, HTTP model (requests/responses), (un)marshalling, servlet adapters, and testing utilities. Its routing DSL offers expressive combinators for defining HTTP endpoints, and its testkit allows route logic to be tested in isolation (even without spinning up actors). It was popular in earlier Scala/Akka stacks but has since been superseded by Akka HTTP as the maintained successor.