Is there a Database-driven development (?) Well, if people like Robert Martin, Eric Evans and many others here on LinkedIn and elsewhere - can spend career in software development advocacy promoting literal database ignorance, anyone is free to do opposite advocacy. Who knows, you may even start a movement. Lord knows I've been doing my part. And it's not even database driven, it's basically using SQL first as I explained in this article: https://lnkd.in/d63FrdMa And it's not even SQL first, it's the PostgreSQL flavor of the SQL. Other platforms doesn't seem want to be anything other then dumb database. They don't even understand a boolean types. PostgreSQL is different. And it's it's not even PostgreSQL SQL first driven or whatever, I just think that should be default, and there many situations when something is better to do on a client. It's just that SQL should be default. But then again I recognize there's a serious skill gap in this industry. It's basically, the right tool for a job driven development. https://lnkd.in/dYjV_hxz
Almost all software is just a presentation layer or capture layer for a database. So yes, it's much easier if you spend more effort on the database. Work out what stored procs input and output you need and take the tables on later. Don't use postgres unless you are cheap. Go with Mssql, where they actually respect the tech.
Use Oracle Database, instead. It will give you the capability to publish stored procedure or table directly via rest.
I am not sure how it is related but where the data is fetch, and how it is processed etc. once again, pragmatism matters.
Vedran B. Heh... man, do I agree with what you wrote about supposedly "modern software" and the sucking noises it frequently makes, especially if a relational database is involved. I've run into my fair share of folks that say things like "SQL stands for Scarcely Qualifies as a Language". I LOVE it when they say that because it means that they're one of two types... someone who can be trained or someone who cannot. It doesn't take long to determine which type they are. The cool part is, especially with the ones that don't want to be trained is that keeps "the field" pretty narrow... which is good for the wallet, as well. Anyway... hang in there. As you already know, being able to work some magic that blows the doors off of a lot of front-end code is fun and profitable. Don't "spread the word". 😊
I feel like a lot of developers that seek this "modern software architecture" now were exactly the ones doing some kind of "database driven development" before. But for some reason they feel like this is not the right way to develop software. I think the first step for this new movement would be to have a genuine interest in understanding what problems are these developers trying to solve. I may be wrong but I feel like you guys spend too much time dumping on DDD/CA coaches, while you could spend more time explaining why your approach is actually better. I feel you guys have a point and I would love to hear more about that.
I can look at this from a well known perspective: Design First Development (instead of Code First approach). So, instead of building your model using UML entity diagrams, you will use SQL for tables and procedures. Once you have your "model", there are plenty of scaffolding tools that will expose your model as an App/API.
I think similar (ish) "Persistence First/-Driven"… I think that is a good frame. Often we need to develop "concurrent persistence"; and, by-design, an excellent machine for concurrent persistence, is a Database; so, database/SQL-Driven can be a good selection…
Junior DBA and Full-Stack Developer
5moFor the millionth time: name calling won't be tolerated and you will be deleted and blocked. Have a nice day.