Thoughts on Software
As Developers, we build API’s regardless if we intentionally designed them or not – it could be some form of abstraction for data persistence, how you invoke talking to another service that you have internally within your organisation etc.
If we were trying to intentionally try to design a good API, first, we should probably understand what makes a good API – or probably a better start, what is an API anyway?
Continuing from the previous part, where we’ve written and tested our parser using Antlr 4 – let’s now generate a C# parser, and hook it up to search an elasticsearch index.
For some products, having your own language that your customers can use to be productive, or make your product that much more powerful, is a Domain Specific Language. Think Atlassian’s Jira Query Language, Github’s filter feature etc.
So – after quite some time working with distributed systems, I want to share the decisions made throughout as you build an event-based distributed system.
I want to share some of the things that I’ve noticed, and my thoughts in general in these different approaches – what they look like, pros and cons etc.