3 ms·

This is probably harsh but the description of their api gateway sounds like the description of corba from the late 90s… probably if you are just getting started

by taf2 5y ago

This is probably harsh but the description of their api gateway sounds like the description of corba from the late 90s… probably if you are just getting started and need something simple but powerful go with openresty… IMO it gives you all the benefits and it’s super fast/lightweight … you can get advanced with cookie sharing / signing or just do simple logging to statsd… it’s really good if you are starting out to get operational experience running nginx / statsd etc… IMO

dtauzell 5y ago
The people defining CORBA faced many of e same issues we face with micro services today.
- TeMPOraL 5y ago
  After working with Distributed COM, I'd go as far as to say that people building DCOM software were doing microservices, way before that term was known or popular - microservices at much finer granularity (per object), and all the bells&whistles people make startups off today - like load balancing, service discovery, strong auth, etc. - were already built into the platform and properly integrated. Alas, it was ahead of its time; the legacy of C makes it hard to work with.
  - barrkel 5y ago
    Eh, but stateful and synchronous and chatty. I don't think DCOM has too many good ideas, beyond what it shares with CORBA - mostly, an IDL. It's good to have an IDL if you're going to be serious about heterogeneous implementations.
plank_time 5y ago
CORBA never scaled to the level that Uber needs to. Pre-pandemic, you’re talking hundreds of thousands to millions of requests per second globally. Also you never saw a CORBA project with thousands of engineers checking in code multiple times a day. All these are factors too. People on HN always think “all it’s doing is matching a rider with a driver, why is it so complicated? I can write it in a weekend!” Sure, but it won’t scale.
- Aeolun 5y ago
  I doubt they have millions of driver to rider matching requests per second. A lot of people use Uber, but they don’t need a ride every second.
  - plank_time 5y ago
    At peak I can see it being low single digit millions per second. A single client will do more than 1 rps, there’s a lot going on per client.
fosk 5y ago
For anybody looking at OpenResty, it’s also worthwhile to a look at Kong, which is the largest openresty-based application and already provides the right abstractions in place for API management: https://github.com/Kong/kong https://github.com/Kong/kong

by taf2 5y ago

dtauzell 5y ago

The people defining CORBA faced many of e same issues we face with micro services today.

TeMPOraL 5y ago
After working with Distributed COM, I'd go as far as to say that people building DCOM software were doing microservices, way before that term was known or popular - microservices at much finer granularity (per object), and all the bells&whistles people make startups off today - like load balancing, service discovery, strong auth, etc. - were already built into the platform and properly integrated. Alas, it was ahead of its time; the legacy of C makes it hard to work with.
- barrkel 5y ago
  Eh, but stateful and synchronous and chatty. I don't think DCOM has too many good ideas, beyond what it shares with CORBA - mostly, an IDL. It's good to have an IDL if you're going to be serious about heterogeneous implementations.

plank_time 5y ago

CORBA never scaled to the level that Uber needs to. Pre-pandemic, you’re talking hundreds of thousands to millions of requests per second globally. Also you never saw a CORBA project with thousands of engineers checking in code multiple times a day. All these are factors too. People on HN always think “all it’s doing is matching a rider with a driver, why is it so complicated? I can write it in a weekend!” Sure, but it won’t scale.

Aeolun 5y ago
I doubt they have millions of driver to rider matching requests per second. A lot of people use Uber, but they don’t need a ride every second.
- plank_time 5y ago
  At peak I can see it being low single digit millions per second. A single client will do more than 1 rps, there’s a lot going on per client.

fosk 5y ago

For anybody looking at OpenResty, it’s also worthwhile to a look at Kong, which is the largest openresty-based application and already provides the right abstractions in place for API management: https://github.com/Kong/kong https://github.com/Kong/kong