6 ms·

Our number is closer to 1,700 now, but yes this means 1,700 distinct applications. Each application has many instances, some have thousands of instances.

by mranney 10y ago

jrochkind1 10y ago
that sounds nightmarish
- dastbe 10y ago
  Why? I'm assuming their highish engineer/service ratio is because their services do less individually. Anecdotally, I've worked on services that ran tens of thousands of instances across the world. You build the tools to manage them and it works very well.
  - softawre 10y ago
    It's not the number of instances that he's talking about, it's the number of images. Microservices can go to far. I'm very thankful for this video.
    - dastbe 10y ago
      The # of services vs # of engineers isn't really bad though; you just need the tools to make the commonalities between services easy.
  - Scarblac 10y ago
    > Why? People talk about interpreted languages being slow sometimes, now your program is divided over 1700 separate servers and instead of keeping variables in memory you have to serialize and send them over the network all the time.
  - deleted 10y ago
    [deleted]
niccaluim 10y ago
Good god, what on earth for?
mtrpcic 10y ago
Could you give some information as to what the breakdown of functionality is for those services? I can't fathom 1700 different and unique pieces of functionality that would need to be their own services.
- lnanek2 10y ago
  I work at a microservice company. An example microservice is our geoservice which simply takes a lat/lon and tells you what service region the user is in (e.g. New York, San Francisco, etc..). You can see how dozens of these services might be needed when handling a single request coming in from the front end or mobile apps. The service may eventually gain another related function or two as we work on tearing down our monolith (internally referred to as the tumor because we do anything to keep it from growing...).
  - taeric 10y ago
    This just sounds crazy to me. How often do the services that are responsible for a given region change?
  - Scarblac 10y ago
    Why would you make that a separate service when e.g. one query on a PostGIS table can do that?
    - user5994461 10y ago
      One query on a table is the exact same thing as a HTTP GET call on a service.
      - taeric 10y ago
        Strictly this is not necessarily relevant. You can easily roll that table hit into another db hit you were already making. Can't do that with services.
      - Scarblac 10y ago
user5994461 10y ago
>>> Our number is closer to 1,700 now, but yes this means 1,700 distinct applications. Each application has many instances, some have thousands of instances. Time to forbid adding more stuff and start cleaning. (12) [...] perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. https://tools.ietf.org/html/rfc1925 https://tools.ietf.org/html/rfc1925
- brown9-2 10y ago
  This type of comment presumes that there is a right number of services for a company to run. What number is that?
BinaryIdiot 10y ago
Whoa. That's is an insanely large amount of applications. I'm assuming that's essentially one function per microservice which is one of the huge do-not-do of microservices as it's just a complete waste of time, resources, etc. I would love to hear a breakdown. This sounds like a nightmare to maintain and test.

Our number is closer to 1,700 now, but yes this means 1,700 distinct applications. Each application has many instances, some have thousands of instances.

by mranney 10y ago

Our number is closer to 1,700 now, but yes this means 1,700 distinct applications. Each application has many instances, some have thousands of instances.

jrochkind1 10y ago

that sounds nightmarish

dastbe 10y ago
Why? I'm assuming their highish engineer/service ratio is because their services do less individually. Anecdotally, I've worked on services that ran tens of thousands of instances across the world. You build the tools to manage them and it works very well.
- softawre 10y ago
  It's not the number of instances that he's talking about, it's the number of images. Microservices can go to far. I'm very thankful for this video.
  - dastbe 10y ago
    The # of services vs # of engineers isn't really bad though; you just need the tools to make the commonalities between services easy.
- Scarblac 10y ago
  > Why? People talk about interpreted languages being slow sometimes, now your program is divided over 1700 separate servers and instead of keeping variables in memory you have to serialize and send them over the network all the time.
- deleted 10y ago
  [deleted]

niccaluim 10y ago

Good god, what on earth for?

mtrpcic 10y ago

Could you give some information as to what the breakdown of functionality is for those services? I can't fathom 1700 different and unique pieces of functionality that would need to be their own services.

lnanek2 10y ago
I work at a microservice company. An example microservice is our geoservice which simply takes a lat/lon and tells you what service region the user is in (e.g. New York, San Francisco, etc..). You can see how dozens of these services might be needed when handling a single request coming in from the front end or mobile apps. The service may eventually gain another related function or two as we work on tearing down our monolith (internally referred to as the tumor because we do anything to keep it from growing...).
- taeric 10y ago
  This just sounds crazy to me. How often do the services that are responsible for a given region change?
- Scarblac 10y ago
  Why would you make that a separate service when e.g. one query on a PostGIS table can do that?
  - user5994461 10y ago
    One query on a table is the exact same thing as a HTTP GET call on a service.
    - taeric 10y ago
      Strictly this is not necessarily relevant. You can easily roll that table hit into another db hit you were already making. Can't do that with services.
    - Scarblac 10y ago

user5994461 10y ago

>>> Our number is closer to 1,700 now, but yes this means 1,700 distinct applications. Each application has many instances, some have thousands of instances. Time to forbid adding more stuff and start cleaning. (12) [...] perfection has been reached not when there is nothing left to add, but when there is nothing left to take away. https://tools.ietf.org/html/rfc1925 https://tools.ietf.org/html/rfc1925

brown9-2 10y ago
This type of comment presumes that there is a right number of services for a company to run. What number is that?

BinaryIdiot 10y ago

Whoa. That's is an insanely large amount of applications. I'm assuming that's essentially one function per microservice which is one of the huge do-not-do of microservices as it's just a complete waste of time, resources, etc. I would love to hear a breakdown. This sounds like a nightmare to maintain and test.