Remove Azure Remove Meeting Remove Microservices Remove SOA
article thumbnail

Architecture options to run a workflow engine

Bernd Rucker

These are valid questions which recently we get asked a lot, especially in the context of microservices , modern SOA initiatives or domain-driven design. If you share one engine you always meet in the data store. In Microservices architectures (or similar) this ownership is typically given to teams building the service.

article thumbnail

Egnyte Architecture: Lessons learned in building and scaling a multi petabyte content platform

High Scalability

SOA architecture based on REST APIs. Python used to power client-side code, certain microservices, migration scripts, internal scripts. Tens of petabytes of data stored in our servers and other object stores such as GCS, S3 and Azure Blobstore. How does your system evolve to meet new scaling challenges? Cloud Platform.

Insiders

Sign Up for our Newsletter

This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

article thumbnail

Crew management in airlines: planning and scheduling with Sabre, Jeppesen, and others

Altexsoft

Overall, crew planning must meet tons of complex rules and requirements dictated by aviation legislation, contractual conditions, and personal expectations. The need for limits on flight and duty time was recognized as far back as in 1944, and since then crew-scheduling practices had to meet strict flight time limitations (FTL).

article thumbnail

Airline Reservation Systems and Passenger Service Systems: Navitaire, Amadeus Altea, SabreSonic and more

Altexsoft

On the one hand, legacy systems continue to meet the basic industry requirements: they process high volumes of transactions, proving to be super-fast, reliable, and relatively secure. Currently, providers of PSSs are switching from monolithic to service-based design — either service-oriented architecture (SOA) or microservices.