Search Results for "evolution-x"

Finatra builds on TwitterServer and uses Finagle, therefore it is highly recommended that you familiarize yourself with those frameworks before getting started. The version of Finatra documented here is version 2.x. Version 2.x is a complete rewrite over v1.x and as such many things are different. Finatra at its core is agnostic to the type of service or application being created. It can be used to build anything based on TwitterUtil: c.t.app.App. For servers, Finatra builds on top of the features of TwitterServer (and Finagle) by allowing you to easily define a Server and controllers (a Service-like abstraction) which define and handle endpoints of the Server. ...

...Graphcool separates the business logic from stateful storage components, allowing the stateful parts (database, subscription engine) to scale independently and giving flexibility in how you compose your system. Users could deploy Graphcool either locally (e.g. via Docker) or on a managed cloud offering. The framework also provided features like schema evolution, migrations, data loaders for performance, and built-in tooling to manage endpoints and deployments.

...Operationally, it’s engineered for high traffic spikes—breaking news or live sports—through aggressive caching strategies, feature switches, and robust fault isolation between services. The project reflects a long-running evolution from a monolith toward a service-oriented architecture, with portions moved to separate rendering services and modern front-end stacks while this repo remains the glue for core routes and legacy paths.