I agree, but the comments here are generally pretty reasonable. There are problems on both ends of the spectrum. Landing in a sensible middle area is pretty important.
It's pronounced Diane. I do data architecture, operations, and backend development. In my spare time I maintain Massive.js, a data mapper for Node.js and PostgreSQL.
It's really about context more than anything. Monoliths are easier to maintain when they encapsulate less complexity than is worth the microservice effort overhead. Asynchronous web UIs can be unacceptably slow for some purposes. Breaking out a planet-scale distributed datastore when you have a few hundred megabytes of data tops is stupid. Framing an issue as a case of extreme, flawed, and diametrically opposed perspectives dueling around a sensible center tends to be overly simplistic.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
I agree, but the comments here are generally pretty reasonable. There are problems on both ends of the spectrum. Landing in a sensible middle area is pretty important.
Yes, and it's not easy.
I for one would say serverless is the future and blockchains are a fad.
But maybe it's the other way around?
I think these things are becoming important, but we are in fairly painful early days in both.
I don’t think there’s anything wrong with hanging back and catching on once some of the dust has settled.
It's really about context more than anything. Monoliths are easier to maintain when they encapsulate less complexity than is worth the microservice effort overhead. Asynchronous web UIs can be unacceptably slow for some purposes. Breaking out a planet-scale distributed datastore when you have a few hundred megabytes of data tops is stupid. Framing an issue as a case of extreme, flawed, and diametrically opposed perspectives dueling around a sensible center tends to be overly simplistic.